Community Forums
Results 1 to 5 of 5

Thread: Directory Manager Not Initialized on showmsilog

  1. #1
    Join Date
    Jan 2009
    Johannesburg, South Africa

    Directory Manager Not Initialized on showmsilog

    I have an MSI where I have enabled logging using the option "Create MSI logs" under Product Properties.

    I have also added a LaunchCondition to test for an application, should the application be installed then the install must fail - Which it does displaying the message box.

    The installed the display the SetupCompleteError dialog box with the option to veiw the log.

    If you select to view the log and click Finish an error message is displayed saying "Directory Manager Not Initialized".

    This is a basic MSI project.

    How do I overcome this error (Other than turning of the option of logging)?

    Tested using Windows 2008 64 bit and a 32 bit msi.

    Doing action: SetupCompleteError
    Info 2898.For TahomaWhite8 textstyle, the system created a 'Tahoma' font, in 0 character set.
    Info 2898.For TahomaBold10 textstyle, the system created a 'Tahoma' font, in 0 character set.
    SetupCompleteError. Dialog created
    Note: 1: 2731 2: 0
    PROPERTY CHANGE: Adding ISSHOWMSILOG property. Its value is '1'.ShowMsiLog
    Note: 1: 2732 2: 0
    Directory Manager not initialized.
    Product: MyTestProcuct -- Error 2732.Directory Manager not initialized.



  2. #2
    jcarlos10 Guest
    I'm having the same issue. Does anybody know an solution to this?

    -Juan Carlos

  3. #3
    Join Date
    Apr 2002
    Same thing over here. Anyone have any ideas? This is with InstallShield 2011.
    Last edited by nitsev; 03-03-2011 at 09:57 AM. Reason: Added info on installahield 2011

  4. #4
    Join Date
    Mar 2002

    Error 2732 - Directory Manager not initialized.

    The CA that aborts the install may be sequenced before the CostFinalize action, which is when the Directory Manager is initialized. Any action that uses, modifies, tries to retrieve, etc. directory paths must follow the costing actions, in both sequences.
    Testing whether an application is installed, or resolving the path for the msi logfile may involve directories the Directory Manager doesn't know about yet.
    Look carefully at what happens up to the point where you display SetupCompleteError.
    Last edited by RobFlum; 05-16-2012 at 05:38 PM. Reason: signature wrong
    Rob Flum
    Elance freelancer

  5. #5
    Join Date
    Mar 2006
    Use your own Custom Action (CA) instead of built-in CA ShowMsiLog -

    1. Main CA (any name)
    a. Custom Actions – New EXE – Path in property value
    b. Executable Property: NOTEPADPATH
    c. Command Line: [MsiLogFileLocation]
    d. Return Processing: Asyncronous (No wait for completion)

    2. Supporting CA (any name)
    a. Custom Actions – New Set Property
    b. Property Name: NOTEPADPATH
    c. PropertyValue: [SystemFolder]notepad.exe
    d. Install UI Sequence: After AppSearch
    e. Install Exec Sequence: After AppSearch

    3. Rename built-in ShowMsiLog CA to exShowMsiLog and your Main CA (see above) to ShowMsiLog
    Last edited by Domnitch; 01-28-2014 at 04:58 AM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts