Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 1001 Source: MsiInstaller

Detection of product '<product GUID>', feature '<feature name>' failed during request for component '<component GUID>'.
- Component GUID: {9E0B2BE1-DEDA-11D1-A17E-00A0C90AB50F} - A newsgroup post suggests that Method 2 from ME265194 solves the problem.
- Component GUID: {8E46FEFA-D973-6294-B305-E968CEDFFCB9} - See ME911682.
- Component GUID: {79ED246A-69C7-4CEF-85A2-57EC3886BC31} - See "Citrix Support Document ID: CTX103585".

See ME912159 and ME915431 for hotfixes applicable to Microsoft Office SharePoint Portal Server 2003.
If this error is generated with a user who has minimal rights, he may be missing some HKCU keys. To fix see “Windows Administration - Problems of Privilege: Find and Fix LUA Bugs”.
- Component GUID: {876580E3-2E52-4F48-A7B8-298B9D795970} - We received this error after applying the "Citrix Hotfix Rollup Pack PSE400W2K3R01" to our Windows 2003 servers running PSE4. Published applications would not run in a published desktop. When selected they would attempt to install. After uninstalling the Citrix hotfix, the problem went away. I reinstalled the hotfix and the problem reappeared.

See "Citrix Support Document ID: CTX108764" for more details on this issue.
If this happened to you after you upgraded Windows Installer to version 2.0, then ME319624 might be able to fix your problem.

If this issue occurs when you try to install Windows SharePoint Services, see ME833183 for information on how to fix this problem.

See ME314852 to find out how to enable Windows Installer logging in Windows XP.
ME290301 provides a description of the Windows Installer CleanUp utility. Additional information on this event can be found in the Frequently Asked Questions about Windows Installer.

From a newsgroup post: "We just deployed Office XP SP3 to the whole company. I had two machines that every time the users try to open any Office product, or IE it tried to go thru the install again. Only common denominator that I found is that they both had Project 2003 installed as well. In order to get rid of the problem I had to remove Project 2003 and Office, then reinstall Office, and after this reinstall Project again". Look at ME290139 for more information.

- Component GUID: {96220418-71CF-4334-B0B4-D6D11A3DD30E} - See "BlackBerry Support Article Number: KB-04393".
- Component GUID: {C763CD13-6E1E-4166-8C78-D274B266E9B6} - From a newsgroup post: "The component "{C763CD13-6E1E-4166-8C78-D274B266E9B6}" has a keypath with file "CookDoc.dll". Let us try the following to fix this issue:

1. Search for the file "CookDoc.dll" on your system. By default, it should be in the following folder: “C:\Program Files\Common Files\Microsoft Shared\MSDN”.
2. Open a command line interface (by running "cmd.exe") and issue the
following command: RegSvr32 "C:\Program Files\Common Files\Microsoft Shared\MSDN\CookDoc.dll".

Here we need to use the quotation marks to quote the full path towards the DLL.
3. Normally you should be able to see the prompt like the following: DllRegisterServer in c:\program files\Common Files\Microsoft Shared\MSDN\CookDoc.dll succeeded".

See "Citrix Support Document ID: CTX106101" for additional information on this event.
- Component GUID: BD12EB47-DBDF-11D3-BEEA-00A0CC272509 - On a server running Windows 2000 Server SP4 and Norton AntiVirus Corporate Edition 7.51, I tried to upgrade LiveUpdate to full version I had just successfully performed the same procedure on a similar server in the same domain. The upgrade process failed on this second server, and I had to create some missing registry keys and values using the first server as a guide. After rebooting, Windows Installer repeatedly prompted me for NAVCE.MSI on the NAVCE installation CD. The 1001/MsiInstaller warning in the Application event log coincided with each prompt. I searched the registry for component ID BD12EB47-DBDF-11D3-BEEA-00A0CC272509 and discovered that the server had a locally stored and renamed copy of NAVCE.MSI in C:\WINNT\Installer\. I created a folder {BD12EB47-DBDF-11D3-BEEA-00A0CC272509} within in, copied the local copy of NAVCE.MSI to that folder, renamed it as NAVCE.MSI, pointed Windows Installer to it and rebooted after installation. Windows Installer attempted installation again after I next opened NAVCE, but it found NAVCE.MSI in the folder that I created and finished without prompting me. All seems to be well now.

We received this error on W2K Professional workstations when logged on with a domain user. In our case, we were receiving this error whenever an Access file was opened by double-clicking an .mdb file. When opening Access first and then opening the database file (.mdb), everything worked without errors.
To fix the problem, I re-ran the setup program and installed all of the "Install on first use" features of Office. The error happens because domain users are not permitted to run the installer to add those "Install on first use" items, an option that I wish Microsoft would eliminate.
We found that this event is generated when MsiInstaller is trying to install a package but the installation is intrerrupted by the user (typically), the original installation kit is not present or by a problem with the software. For troubleshooting, enable the MsiInstaller verbose log file using the instructions from KB article ME223300.

From a newsgroup post: I've had similar errors. Turned out that I'd removed a shortcut from my Start Menu. Solution: reboot and have your Office CD in the installation drive as you boot into Windows. Whatever is missing should reinstall."
I have noticed that 1000, 1001, 1004 errors with Msinstaller are generated with a user who has minimal rights. If a regular user starts Excel these errors will be generated. When someone starts excel with Administrator right, nothing happens.
Hints: Check of everything is installed on the harddisk (office 2000), no cd-rom requirements or install when first started.
Here is a solution that worked for me:
- Reboot machine into safe mode with command prompt. (Win2K Server)
- On each hard disk, issue following command from drive's root: DEL *.tmp /S
- Clear any TEMP directories of their contents: C:\TEMP, C:\WINNT\TEMP, etc.  Clear an entire folder by adding /S to rmdir command.
- Reboot machine into normal operation mode and reinstall product. Ignore popup installer error message boxes (as reported previously "...Configuration file successfully created...") and finish the install.
- If reboot is requested, do so.
See ME274473: Windows Installer Runs Every Time Help Is Used on WTS.
Add two Reg entries under :
UserData (DWORD) = 1
UserData (DWORD) = 1

Feature: OUTLOOKNonBootFiles - If someone click on Outlook Today the Windows Installer popsup. And this error is logged in the eventlog. The problem is that there is an Registry entry missing :
UserData RegDword = 1
Feature ProductNonBootFiles - See ME298385.
I had the same error occur on my system. I used Office Update to install the Windows MSI Installer v2.0. After the system was restarted, the problem did not occur again.
In my case this error revealed that an important file was not installed from an MSI package assigned to machines. I used ORCA from the Windows Installer SDK to load the MSI and look up the component, which turned out to be a file that did not get installed for some reason. I am still investigating this and it appears to be vendor error in the MSI.

In the case of Office XP, which I also assigned to machines and not users, the warning appears when the office applications are first launched because the MSI notices that HKCU keys are missing. This is OK, because it creates them ("repairs") on the fly when users first launch the application.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.