Monday, September 25, 2006

Error 2732

We've had a couple of people run into this error. (Windows Installer error 2732) It usually pops up right as their installer starts. The error means "Directory Manager not initialized" which is described as "the directory manager is responsible for determining the target and source paths. It is initialized during the costing actions (CostInitialize action, FileCost action, and CostFinalize action). A standard action or custom action made a call to a function requiring the directory manager before the initialization of the directory manager. This action should be sequenced after the costing actions." (ref here)

In this latest version of the merge module the files' destinations were changed from "C:\program files\common files\plantronics\plantronics device" to "[CommonFilesFolder]\plantronics\plantronics device". On your typical Windows installation on your typical English language machine these would be indistinguishable. However, the new path is using a variable. That variable must be resolved, and the directory manager needs to be initialized to resolve it.

I would recommend checking your installation sequence and making sure that the CostInitialize action, the FileCost action, and the CostFinalize action are being called, and being called early. Just about any installation is probably already calling these, but it may be calling them too late for the merge module.

0 Comments:

Post a Comment

<< Home