Directory Manager not initialized. - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

cyberdavid
Posts: 2
Joined: Sat Aug 04, 2012 11:49 pm

Directory Manager not initialized.

Hello,
I am a beginner in both Advanced Installer and Visual Studio. I have finished coding in Voice Recognition and TTS. It is remaining to publish the package which using Advanced Installer and importing Visual Studio 2010 solution with merge module of MS voice engine MSM. After I compiled and setup the package, it was fine. After that, I also using merge module of the Third party TTS voice MSM file and compiled again. It was still fine. But once I setup the package under both my own machine and other machines, MSI Installer showed error that “Directory Manager not initialized.” As I googled, it’s belonging to MSI Error 2732 Directory Manager not initialized. Someone recommended in issues below.
1. May not have put a backslash (\) after a directory path in the set directory action or the custom action should be CostInitialize
2. Solving by Orca.exe
3. Solving by Custom Action in Advanced Installer
4. Solving by Dark.exe of WiX Installer to solve it.
5. It looks Advanced Installer is running the merge modules before the CostInitialize/CostFinalize actions and the MSM needs to "use" the directory manager.
6. The MSM merge module files requires the actual developer the right to use them (As this issue, the third party MSM informed me that their MSM files were released only for my cooperation for trial test. So, I filled the right name in Advanced Installer/ Product Details / Company name)
7. Etc.

All those above I am not familiar. Could someone help me to solve this in details? Here I show you below the log file after trying of setup package failed.
=== Logging started: 6/8/2555 7:26:41 ===
Action start 7:26:41: INSTALL.
Action start 7:26:41: AI_SET_INSTALL.
Action ended 7:26:41: AI_SET_INSTALL. Return value 1.
Action start 7:26:41: AI_ResolveLocalizedCredentials.
ConvertSidToStringSidW
ConvertSidToStringSidW
ConvertSidToStringSidW
ConvertSidToStringSidW
ConvertSidToStringSidW
ConvertSidToStringSidW
Action ended 7:26:42: AI_ResolveLocalizedCredentials. Return value 1.
Action start 7:26:42: AI_ResolveKnownFolders.
Action ended 7:26:42: AI_ResolveKnownFolders. Return value 1.
Action start 7:26:42: PrepareDlg.
Info 2898. For DlgFont8 textstyle, the system created a 'Tahoma' font, in 0 character set.
Info 2898. For VerdanaBold13 textstyle, the system created a 'Verdana' font, in 0 character set.
Info 2826. Control BottomLine on dialog PrepareDlg extends beyond the boundaries of the dialog to the right by 3 pixels.
Action ended 7:26:42: PrepareDlg. Return value 1.
Action start 7:26:42: AI_StartImageSlideshow.
Action ended 7:26:42: AI_StartImageSlideshow. Return value 1.
Action start 7:26:42: AI_BACKUP_AI_SETUPEXEPATH.
Action ended 7:26:42: AI_BACKUP_AI_SETUPEXEPATH. Return value 1.
Action start 7:26:42: AppSearch.
Action ended 7:26:42: AppSearch. Return value 1.
Action start 7:26:42: AI_RESTORE_AI_SETUPEXEPATH.
Action ended 7:26:42: AI_RESTORE_AI_SETUPEXEPATH. Return value 1.
Action start 7:26:42: FindRelatedProducts.
Action ended 7:26:42: FindRelatedProducts. Return value 1.
Action start 7:26:42: LaunchConditions.
Action ended 7:26:42: LaunchConditions. Return value 1.
Action start 7:26:42: setUserProfileNT.
Action ended 7:26:42: setUserProfileNT. Return value 1.
Action start 7:26:42: setAllUsersProfile2K.
Action ended 7:26:42: setAllUsersProfile2K. Return value 1.
Action start 7:26:42: ResolveSource.
Error 2732. Directory Manager not initialized.
MSI (c) (98:14) [07:26:44:083]: Product: Test 9 -- Error 2732. Directory Manager not initialized.

Action ended 7:26:44: ResolveSource. Return value 3.
Action start 7:26:44: FatalError.
Info 2826. Control BottomLine on dialog FatalError extends beyond the boundaries of the dialog to the right by 3 pixels.
Action start 7:26:45: AI_SHOW_LOG.
Action ended 7:26:45: AI_SHOW_LOG. Return value 1.
Action start 7:26:45: AI_StopImageSlideshow.
Action ended 7:26:45: AI_StopImageSlideshow. Return value 1.
Action ended 7:26:45: FatalError. Return value 2.

Thanks and Kind Regards,
David
cyberdavid
Posts: 2
Joined: Sat Aug 04, 2012 11:49 pm

Re: Directory Manager not initialized.

Let me update. My third party MSM distributor just told me that his MSM file released by InstallShield installer and it is not compatible with my EXE project which released by Advanced Installer. Why? It should be standardised under Microsoft's. Is there anyone help me? Have you integrate Install Shield MSM file with your Advanced Installer EXE project?

Thanks in advance.
cyberdavid
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Directory Manager not initialized.

Hi,
MSI Installer showed error that “Directory Manager not initialized.”
It looks like one of the merge modules is calling ResolveSource standard action before CostInitialize. I noticed that some custom actions were executed before ResolveSource, so perhaps one of them triggered it:
- setUserProfileNT
- setAllUsersProfile2K

This is a problem with one of the merge modules. To fix it, you can try moving these custom actions or ResolveSource action after CostInitialize in InstallUISequence and InstallExecuteSequence tables of the MSM. To modify a MSM you can use Orca.
My third party MSM distributor just told me that his MSM file released by InstallShield installer and it is not compatible with my EXE project which released by Advanced Installer.
That seems very unlikely. Advanced Installer supports merge modules created with any setup authoring tool. Perhaps the merge module needs to be configured somehow and this is why it doesn't work out of the box.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”