mhatkinson
Posts: 32
Joined: Tue Apr 08, 2008 5:36 pm

Error 2732 - Directory Manager not initialized

I'm getting an error when I include an merge module in my project. The error is: 2732 - Directory Manager not initialized.

It looks AI is running the merge modules before the CostInitialize/CostFinalize actions and the MSM needs to "use" the directory manager. Is there any way to sequence the MSM's so that they run after the directory manager has been initialized?

Thanks,
Mark
mhatkinson
Posts: 32
Joined: Tue Apr 08, 2008 5:36 pm

Re: Error 2732 - Directory Manager not initialized

OK, so in the merge module I'm trying to include, they have an action that, apparently, requires the directory manager to be initialized. But the action sequence value is 525 and the CostInitialize/Finalize stuff happens in this sequence (as far as I know):
CostInitialize 800
FileCost 900
CostFinalize 1000

The folks that made the msm suggested changing the sequence value of their action from 525 to 850 and claimed they've had success with that before.
So, in Orca, I make the change (the only change) and save the .msm.
Now, when I build the .msi with the msm included in Advanced Installer 7.5.2, I get this error
Exception - Reason: Error calling Msi API: 161 Method: MsiRecordSetStream Table: MergeMod. Build finished because an
error was encountered.

It looks like the problem is really on the end of the people that made the msm I'm trying to include, but if you have any suggestions, it would be appreciated.

thanks,
Mark
GabrielBarbu
Posts: 2146
Joined: Thu Jul 09, 2009 11:24 am
Contact: Website

Re: Error 2732 - Directory Manager not initialized

Hello,

You can try the following:
- add the msm (unmodified)
- do the proper modifications from Advanced Installer's Table Editor instead of doing them from Orca
- rebuild

Let us know if this helped.

Best regards,
Gabriel
Gabriel Barbu
Advanced Installer Team
http://www.advancedinstaller.com/

Return to “Common Problems”