Enabling verbose logging for Windows installer may provide more information about the source of the problem. See ME314852
on how to enable Windows Installer logging in Windows XP.
- Product: Microsoft Shared Fax - See ME930216
- Product: Candle OMEGAMON XE - See "IBM Support Reference # 1204136".
- Product: Microsoft Content Management Server Sample Data - This can happen when you install the sample site on a different Web site as the Default Web Site. This is not officially supported. Also ensure that you did not rename the Default Web Site to another name. See the link to "MCMS Complete FAQ" to solve this problem.
- Product: McAfee GroupShield For Exchange - McAfee Solution ID kb38650 states that this is a permission issue. Go to the "McAfee Knowledge Search" page and search for the specified solution for details.
- Product: Symantec AntiVirus Client - See the link to "Symantec Knowledge Base Document ID: 2002091814020248" for details on this issue.
See the link to "Citrix Support Document ID: CTX103080
" for additional information on this event.
- Product: Sophos Small Business Anti-Virus - This event was posted in the event log when an error occurred while trying to update the client software (0x80041f09). We went into the registry under [HKLM\Software\Sophos] and changed the permissions of this level key to give the administrator (or installer) full rights. Running the update again allowed the software installation to complete successfully.
- Product: Microsoft Windows Update Auto Update - As per Microsoft: "The behavior occurs because the Automatic Update Client is already installed". See ME835399
for more details.
- Product: CustomMSI - See ME825075
- Product: BusinessApp (Application Proxy) - See ME317996
- Product: Symantec AntiVirus - See the link to "Symantec Support Document ID: 2004112515491748".
- Product: Microsoft Host Integration Server 2000 End-User Client - See ME899427
for a hotfix applicable to Microsoft Host Integration Server 2000.
- Product: McAfee GroupShield for Lotus Domino - Read "McAfee Support Solution ID NAI36669" and McAfee Support Solution ID kb44246. Go to the McAfee Knowledge Search page and search for these solutions to read them.
- Product: MetaFrame Presentation Server – Administration Snap-in - See "Citrix Support Document ID: CTX108839
- Product: Citrix MetaFrame Presentation Server for Windows - See "Citrix Support Document ID: CTX110279
" and "Citrix Support Document ID: CTX113596
- Product: COMTI Test Server - See ME329456
I was receiving this error when trying to update Office 2003, either when trying to install Office Patches and SPs, and also when trying to use Add/Remove Programs to try to repair Office. Microsoft`s article ME295823
resolved our problem.
The problem for me was that I could not run any MSI installation. After some research, it seems that the problem was residing in the registry. Going to HKLM\Software\Policies\Microsoft\Windows\Installer, "DisableMSI" was set to 2. Setting it to 0 resolved the issue.
A corrupt Group Policy Object can cause this. In my case, one faulty GPO caused this event to fire off for every application installed on the machine, every time a user logged in. The result was a logon that took way too long and an application event log full of 11708 errors. Removing the problematic GPO resolved the issue.
- Product: ActiveSync - If you have another email client installed, there are some chances that MAPI is broken. Run fixmapi.exe and try again. See ME228457
and the link to “Can not install Activesync 4.x“ for more details.
I was trying to deploy Office 2003 with a mst-template, but the install failed after about ten seconds. The event viewer wasn't very informative. I used the “/l*” logging option as suggested by contributor Steve Palmer. In the log it was mentioned that the mst-file was probably corrupt. I recreated the mst-template and saved it with a different name than the previous one, run the installer on the CLI and the installation succeeded.
In order to get more information about the failure of the installer bring up a cmd and type in:
msiexec.exe /i product.msi /l* c:\log file name.txt
It will go through the installer as normal but will create a log file that you can look at.
- Product: Windows Server 2003 Administration Tools Pack - See the link to "www.experts-exchange.com Q_21404770" for details on this issue.
Make sure that the SYSTEM account has access to the installation folder and files.
This event can also appear during the installation of the ISA firewall client. The ISA client is unable to install correctly, because in the registry 8.3 file name creation functionality has been disabled. See KB article ME294409
for more information.
Check that Everyone has full rights on the folder where the “*.msi” is executed.
This event ID can be generated for a number of different reasons, the ones we encountered are listed below:
1) Corrupt user profile
2) Improper permissions to component Services (Windows XP). Go to start run and type in "dcomcnfg" expand Component Services > Computer and go to properties on "My Computer" and modify permissions on "default COM Security" as needed.