Windows Installer RRS feed

  • Question

  • Hi,

    Getting below error while starting Windows Installer Service in Windows Server 2003 SP2

    Could not start the Windows Installer Service on the Local Compuer

    Error 14007: The requested lookup key was not found in any active activation congtext.

    Monday, April 12, 2010 1:58 PM


All replies

  • Hello,

    this should help you:;en-us;555175&SD=tech

    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
    Monday, April 12, 2010 2:03 PM
  • Take a look at this article:


    Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX This posting is provided "AS IS" with no warranties, and confers no rights.
    Monday, April 12, 2010 3:15 PM
  • Getting this Application Event

    The description for Event ID ( 10005 ) in Source ( MsiInstaller ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Product: Configuration Manager Client -- Error 25100. Setup was unable to create the WMI namespace CCM
    The error code is 80040154, (NULL), (NULL), (NULL), (NULL), , .


    Tuesday, April 13, 2010 3:56 AM
  • Hi,


    Please check the Default Domain Policy to see if there is any Windows Installer related policy is setup. Here are the detailed steps:


    1. Change the start type of the Windows Installer service in Default Domain Policy, from Automatic to Manual mode.


    a) Open GPMC.msc

    b) Go to the Default Domain Policy

    c) Click on Edit

    d) Got to Computer Configuration\Windows Settings\Security Settings\System\Services\Windows Installer and change the startup up type to Manual


    2. Do a gpupdate /force on the DC.

    3. Reboot.

    4. Check if the startup type of the Installer Service is set to Manual

    5. Run msiexec /regserver

    6. Test to start the Windows Installer service again.

    Tuesday, April 13, 2010 8:10 AM
  • Hi,

    We are not implemented any kind of group policy related to windows installer. Till yesterday it was working fine suddenly we got this probelm.





    Tuesday, April 13, 2010 8:23 AM
  • Hi,

    As it is not caused by group policy, please refer following steps to re-register dll files of WMI and CCM Client:

    Open CMD, type in the following commands one by one:

    cd %windir%\System32\WBEM
    for /f %s in ('dir /b /s *.dll') do regsvr32 /s %s
    for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s

    The Above command will re-register all the WMI dll files in the windows registry.

    Then run the following commands:

    cd %windir%\System32\ccm
    for /f %s in ('dir /b /s *.dll') do regsvr32 /s %s
    for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s

    Reboot to see the result.

    If there is any error occurs, or any new event log occurs, please write down and post here.

    Tuesday, April 13, 2010 9:15 AM
  • Hi Shaon,

    After executing this for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s i got amy erros as mentioned below:


    C:\WINDOWS\system32\wbem>mofcomp dnsetw.mof
    Microsoft (R) 32-bit MOF Compiler Version 5.2.3790.3959
    Copyright (c) Microsoft Corp. 1997-2001. All rights reserved.
    Parsing MOF file: dnsetw.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 10 -
    Error Number: 0x80080005, Facility: Windows
    Description: Server execution failed
    Compiler returned error 0x80080005

    Like this so many for every .mof.but i didn't get any errors in event log


    Can i go ahead with below commands or not

    cd %windir%\System32\ccm
    for /f %s in ('dir /b /s *.dll') do regsvr32 /s %s
    for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s


    What can i do now?




    Thursday, April 15, 2010 5:33 PM
  • Hi,

    I believe WMI isn't working on your machine.

    Could you please run procmon trace while connecting to WMI locally on the box, and then look for Access Denied Results in the trace?

    Once you add up the required permission to the entry, I am sure you'll be able to get MSI fixed.


    ~Cheers Visit my Blog@
    • Proposed as answer by HelpforSure Thursday, April 15, 2010 9:47 PM
    Thursday, April 15, 2010 9:47 PM
  • Hi,

    Actually what are common reasons for why WMI is not work? or file got corrupt or services not work?

    Friday, April 16, 2010 9:00 AM
  • Common reason including file corrupt/missing, related registry missing/changed, no permission on registry etc. This article is provided by Santhosh:

    How to resolve Common "Windows Installer" Problems

    You can have a test to install Windows Installer 4.5:


    Monday, April 19, 2010 2:01 AM
  • It wotks....


    I have tried msiexec /regserver, msiexec /unregserver  this 2 commands in local system & it is starts working.....


    Tuesday, May 10, 2011 7:24 AM
  • open CMD


    C:\msiexec /unregserver


    C:\msiexec /regserver

    Now start your Windows Installer service, it will start...



    Tuesday, May 10, 2011 7:26 AM