GFI ESM GFI ESM

Event ID: Event Source:

Event ID 10010 Source DCOM

Event ID10010
SourceDCOM
TypeError
DescriptionThe server {<GUID of the component>} did not register with DCOM within the required timeout.
English, please! This information is only available to subscribers. An example of English, please!
Concepts to understand What is a GUID?
What is DCOM?
How does a COM server register with DCOM?
What is a server?
Comments Adrian Grigorof (Last update 3/12/2009):
As per Microsoft: "This happens when the server was launched but there was no reply from the server. The application may be configured incorrectly and you should check that the application is configured properly". The server here is the server application vs. the client application (and they may reside on the same computer). Obviously this explanation is not too useful.

There are several causes for this error and they depend on what component is reported (you can lookup the GUID in the registry). A good troubleshooting approach is searching the newsgroups for the GUID string.

See below for some of the known problems that cause this event.
- This behavior may be caused by installing Citrix Metaframe 1.8 for Microsoft Windows 2000 and using the drive remapping feature during the Metaframe installation. Download the latest Citrix Metaframe Service Pack. See M263900
- In a Windows Terminal Server session, the debug manager cannot be initialized properly in the Interactive User's context and generates the 10010 event. See M194396.
- If using IIS 4.0 and event IDs 36 and 7011 occur as well then this occurs because the changes made to the application, directory, virtual directory, or site are interrupted while they are being written to the metabase, which corrupted the metabase. See M238665
- In NT 4.0 this event can also occur if Internet Explorer 4.0 is installed (without any Service Pack). See M177510

GUID: F3A614DC-ABE0-11D2-A441-00C04F795683 - This GUID seems to belong to MSN Messenger with Messenger Plus! 2.02.23. From a newsgroup post: "After a fair amount of analysis, I was able to determine that the DCOM errors occur when more than one instance of Messenger (msmsgs.exe) exists; when more than one
Messenger instance exists. To fix this, I wrote a script that verifies the number of msmsg.exe instances. If more than one instance is found, all instances are terminated and a new instance is launched."

GUID: BA126AD1-2166-11D1-B1D0-00805FC1270E = "Network Connection Manager Class". A newsgroup post suggests that this may be caused by a corrupted driver or a RAM-problem. Check if you're using the latest drivers for the hardware components."

GUID: E0B8F398-BB08-4298-87F0-34502693902E - See M823661.

GUID: DC0C2640-1415-4644-875C-6F4D769839BA - This GUID belongs to Apple iTunes and this event was recorded when iTunes was started by clicking on the hyperlink inside an email message from Apple (that connected to the iTunes Store). There was no problems with iTunes but this event was recorded (most probably iTunes re-registered this component).

GUID: 73E709EA-5D93-4B2E-BBB0-99B7938DA9E4 - Belongs to the "Microsoft WMI Provider Subsystem Host" (C:\WINDOWS\system32\wbem\wmiprvse.exe).  - One user reported this a being recorded when a custom VBS script was run against some computers. The script attempted to use the WMI to retrieve certain information about the computer. From a Microsoft blog, this appear to be recorded occasionally by computers where this type of scripts are used, particularly when the computers that are under heavy CPU load. Because of the load, a delay longer than 120 seconds for the COM object to register is causing DCOM to consider this operation as failed and record an error message. The same script may run fine when the computer is not very busy. See the "Adi Oltean Blog" in the links section.

Milli (Last update 5/5/2009):
In my case the problem (SID {0006F020-0000-0000-C000-000000000046} ) occurred because we have installed Office 2000 and I upgraded only Outlook to version 2003 on all workstations.  Each time a user tried to send a document via mail directly in the other office programs (e. g. Excel: File -> Send to -> Mail (Attachment)) he got a message saying "Cannot start Microsoft Outlook. A program eerror occured. Quit Outlook and Mircrosoft Windows and then start again". This was caused by a wrong value in the registry which refers to the old Outlook 2000.ex. To fix it, simply change the value in the key :HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{0006F020-0000-0000-C000-000000000046}\LocalServer32  to C:\PROGRA~1\MICROS~1\Office\ to C:\PROGRA~1\MICROS~1\Office11\.

Mihai Andrei (Last update 11/8/2008):
- GUID: {D99E6E73-FC88-11D0-B498-00A0C90312F3} - See M959117.
- GUID: {4FB6BB00-3347-11D0-B40A-00AA005FF586} - See M912063 for a hotfix applicable to Microsoft Windows Server 2003.
- GUID: {F1673109-CF44-468D-9E23-FE4116F84CFA} - See M870655.

Microsoft article M909444 has some information about a situation in which this event occurs. Follow the link to the article for details.

John L (Last update 7/7/2008):
- GUID: {8BC3F05E-D86B-11D0-A075-00C04FB68820} and {BA126AE5-2166-11D1-B1D0-00805FC1270E} - From a newsgroup post: "It appears that some MS patch changed the permissions on the "HKEY_CLASSES_ROOT\CLSID" registry key. In order to resolve the problem, the following permissions were added: Authenticated users: Read access; Network Service: Full control".

Anonymous (Last update 4/26/2008):
- GUID: {F3A614DC-ABE0-11D2-A441-00C04F795683} and {FB7199AB-79BF-11D2-8D94-0000F875C541} - The problem disappeared after unchecking the "Contacts" checkbox in Outlook Express (View->Layout), and then restarting Outlook Express. The "Contacts" checkbox may be selected again later without problems.

Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here!

Dave White (Last update 10/7/2007):
- GUID: {FBA44040-BD27-4A09-ACC8-C08B7C723DCD} - In my case, the Google toolbar was the culprit. I removed it and the problem was solved.

Filip Zahradnik (Last update 7/18/2007):
I was getting numerous events for various GUIDs on startup and at random times after startup on a Windows XP machine. The wide variety of GUIDs pointed to a problem with DCOM rather than the individual GUIDs. I traced the problem back to dodgy registry permissions. Article M266118 on how to restore default NTFS permissions fixed the problem. The article refers to Windows 2000, but the solution worked well on Windows XP also.

Richard Durr II (Last update 3/19/2007):
- GUID: {5A5AA0AA-1DEB-4683-96B0-B43301E83971} - A newsgroup post suggests that this is related to the HPBPRO.EXE process which is the HP toolbox program. The way to solve this is to either remove the toolbox program or upgrade to version 1.048.0 or newer.

Brooklyn98 (Last update 2/26/2007):
- GUID: {D3FB54B3-B359-4FE4-AE66-49FFBF799088} - See the link to "Citrix Support Document ID: CTX112168".
- GUID: {14B0E00C-96F8-4A61-814B-3F2DD512E1BF} - See the link to "Citrix Support Document ID: CTX112168".

Dmitri Shnitko (Last update 11/24/2006):
- GUID: {4991D34B-80A1-4291-83B6-3328366B9097} - This event can occur when a large file is transferred from the Windows Update Server. A possible solution is to empty the contents of the "C:\Documents and Settings\All Users\Application Data\Microsoft\Network" folder.

Stan (Last update 6/15/2006):
- GUID: {ED081F25-6A77-4C89-B689-C6E15C582EC1} - In my case, this is related to Microsoft Active Sync, and only occures when the pda/phone is not in the cradle. It has never occured with the phone in the cradle, and can be duplicated by removing the phone. I am ignoring it.

David Adams (Last update 5/19/2006):
GUID: {0C0A3666-30C9-11D0-8F20-00805F2CD064} – this GUID refers to MDM.EXE or “Machine Debug Manager”. This runs when “Disable Script Debugging” is cleared (i.e. script debugging is enabled) in Internet Options -> Advanced. Also runs with ASP scripts.
Incorrect configuration causes slow IE load, this event in the event log and EventID 37 from source W3SVC.

Fix1: As stated by “Anonymous (Last update 5/3/2005)”, delete this DCOM application (I do not know the implications of this deletion).
Fix2: Check the “Disable Script Debugging” checkbox in Internet Options -> Advanced.
Fix3: Enter Component Services (Windows XP) or use DCOMCNFG.EXE (Win2K) to configure the properties for “Machine Debug Manager”. Remove and then replace IWAM_<server> and IUSR_<server> accounts in the “Use custom access permissions” and “Use custom launch permissions” sections on the “Security” tab. Ensure “Allow Access” & “Allow Launch” permissions are set for these accounts.

Note: Possibly a side issue but the above got me so far. I still had script errors when running ASP scripts.
Fix: Re-register the scripting engine with the following command:
"regsvr32 c:\winnt\system32\scrrun.dll".

Anonymous (Last update 12/22/2005):
GUID: {BAA8FB92-D1E7-4181-B0EE-94DA3329F7C0} - This event was caused by Microsoft Handwriting recognition being installed. It happened on shutdown on Windows XP. Since I have no devices that recognize handwriting, I simply removed it through settings on the language toolbar. I followed the following procedure taken from Microsoft TechNet website for DCOM errors.

To determine the program vendor:
1. Using Regedit, navigate to the following registry value
HKCR\CLSID\CLSID value\localserver32.
The CLSID value is the information displayed in the message.
2. In the right pane, double-click Default. The Edit String dialog box is displayed. Leave this dialog box open.
3. Click Start, and then click My Computer.
4. Using the information displayed in the Value data box of the Edit String dialog box, navigate to the program.
5. Right-click the program name, and then click Properties. The Properties dialog box for the program is displayed.
6. To determine who the vendor is for this program, refer to the Version tab.

Ionut Marin (Last update 8/16/2005):
As per Microsoft: "The Component Object Model (COM) infrastructure tried to start the named server; however, the server did not reply within the required timeout period. There might be a deadlock, or the program might not have responded to the server initialization code within the timeout period of two minutes". See MSW2KDB for more details.

If the component GUID is: 3D14228D-FBE1-11D0-995D-00C04FD919C1, the event appears according to Microsoft when you try to browse Active Server Pages (ASP) pages. See M327153 to fix this problem.

GUID: 520CCA63-51A5-11D3-9144-00104BA11C5E. From a newsgroup post: "I think my DCOM problem was caused by a combination of Windows Messenger and Outlook Express. I removed Windows Messenger and I have not seen the DCOM error".
The event can also occur when you complete a drive remapping during a Citrix MetaFrame 1.8 installation on a Microsoft Windows 2000 Terminal Server computer. See M280719 for more information.

- GUID: {D61A27C6-8F53-11D0-BFA0-00A024151983} - See M825118 for a hotfix.
- GUID: {FB7199AB-79BF-11D2-8D94-0000F875C541} - See M325717.
- GUID: {B6EC1632-E61D-11D2-85EA-0000F87A5571} - See M247962.
- GUID: {02D4B3F1-FD88-11D1-960D-00805FC79235} - See M326306.
- GUID: {3D14228D-FBE1-11D0-995D-00C04FD919C1} - See M309051.
- GUID: {A9E69610-B80D-11D0-B9B9-00A0C922E750} - See M252638.
- GUID: {8BC3F05E-D86B-11D0-A075-00C04FB68820} - See M839880.
- GUID: {590A29BA-CF7E-4034-82AB-CBBEF9BA844E} - See M870694.
- GUID: {601ac3dc-786a-4eb0-bf40-ee3521e70bfb} - See M873375.
- GUID: "Network Crawler" - See M873375.
- GUID: {27B04BDE-684A-415B-9F6E-187EDD0BD419} - See "Veritas Support Document ID: 270419".
- GUID: {3D14228D-FBE1-11D0-995D-00C04FD919C1} - See the link to "Citrix Support Document ID: CTX104956".
- GUID: {200691B9-C444-4089-8C61-247621196B15} - See M891330.
- GUID: {A9E69610-B80D-11D0-B9B9-00A0C922E750} - See M903072.

If you experience problems with Outlook Express running very slow, take a look at "Insideoe.tomsterdam.com"(see the link below).

If you are having problems installing McAfee NetShield, then see the link to “McAfee Support Solution ID: nai3134” for information on this problem.

If you are having problems installing the Microsoft Systems Management Server (SMS) 2003 Advanced Client on a computer that has Microsoft Internet Information Services (IIS) installed, then read 884870 for a workaround on this problem.

Also check M312074 and M820461 for more details.

If you do not need DCOM you can disable it in the following way:
1. Set the EnableDCOM Value Name, a string (REG_SZ) data type, at HKEY_LOCAL_MACHINE\Software\Microsoft\OLE to N.
2.Shutdown and restart your computer.
3.For Windows XP and Windows Server 2003, complete the following additional steps:
  A. Run Dcomcnfg.exe.
  B. Expand Component Services.
  C. Right-click Computer and press Properties. For a remote computer, right-click Computer, press New, press Computer, type the ComputerName, right-click the ComputerName and press Properties.
  D. Select the Default Properties tab.
  E. Clear the Enable Distributed COM on this Computer box.
  F. press Apply to disable DCOM.
  G. Press OK and exit Dcomcnfg.exe.
  H. Shutdown and restart your computer.

Also check M826382 to see how to disable DCOM support in RPC over HTTP for Win2k3 servers.

Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here!

Anonymous (Last update 5/3/2005):
- GUID: {0C0A3666-30C9-11D0-8F20-00805F2CD064} - This GUID belongs to MDM i.e. Machine Debug Manager. This problem caused a severe slowdown when starting Internet Explorer or Outlook XP. Contributor Stephan Grossberndt already posted his solution to this problem. An alternative solution is to go to "c:\winnt\system32\com\comexp.msc” -> Component Services -> Computer -> My Computer -> DCOM config -> select Machine Debug Manager -> delete.

Philip Patrick (Last update 3/10/2005):
- GUID: {A1F4E726-8CF1-11D1-BF92-0060081ED811} - The problem I have encountered was that the Windows Media Encoder did not start and this event was logged in the event log. To resolve this issue, I had to stop and disable the WIA (Windows Image Acquisition) service.

Wobert (Last update 2/2/2005):
We had this problem, every time a user logged on to the server, via terminal services. Originally, we got the EventID 10002 from source Dcom, but after using dcomconfg.exe to change permissions on the culprit (FameworkServices.exe, a McAfee service) to default on all 3 topics, the 10002 error disappeared, and the 10010 error appeared. To get rid of the 10010, all that was needed was a restart of the FrameworkService service.

Jason Smith (Last update 11/15/2004):
- GUID: {2C5DFFB3-472F-11CE-A030-00AA00339A98} - This error was occurring on a SQL 2000 cluster member running on Win2k. I searched the registry and I found that the GUID belonged to the License Logging Service. I also had many “llsmgr.exe” processes running. I terminated all running “llsmgr.exe” processes and stopped the License Logging Service. The DCOM errors stopped appearing. This does not affect the operation of any software on the servers. See MS article M824196 for more information.

Mark Penders (Last update 8/16/2004):
From a newsgroup post: "By searching the registry for the "server" number listed in the error log, I found it in the registry. Inside the associated registry entries, I found a reference to wiamgr.dll. A search on this revealed that this is the new "Windows Image Acquisition" system, which is supposed to replace TWAIN, and is new in XP. However, that was not much help, since it only confirmed what I suspected before, that I had a scanner related problem. In the end, to fix the problem, I searched my system for all “.dll” files starting with “wia”. I found that there were around 7 or so sitting in “c:\windows\system32”. I did a “regsvr32 wiamgr.dll” and repeated that for all the DLLs starting with “wia”, then I followed it up with a “SFC /SCANNOW” and after a reboot, everything was fixed".

Mark Powell (Last update 6/1/2004):
- GUID: {DFDCBFDA-632A-4DC1-93E4-55E7B50F6C64} - I have had many 10010 errors related to the NetIQ AppManager Agent. NetIQ Knowledge Base Article ID: NETIQKB26239 addresses this situation.

Ben Rothbauer (Last update 3/18/2004):
- GUID: {8BC3F05E-D86B-11D0-A075-00C04FB68820} - This GUID belongs to Windows Management Instrumentation Service. EventID 10010 was generated every 10 minutes. I restarted the service and the problem was solved.

Stephan Grossberndt (Last update 3/18/2004):
- GUID: {0C0A3666-30C9-11D0-8F20-00805F2CD064} - This GUID belongs to MDM i.e. Machine Debug Manager. This problem caused a severe slowdown when starting Internet Explorer or Outlook XP. I solved this by:
1. Disabling DCOM. Go to “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole” and set “EnableDCOM” to “N”. Another way to accomplish this is to run the following command “c:\winnt\system32\com\comexp.msc” -> Component Services -> Computer -> right click My Computer -> Options/Preferences -> Default Options/Preferences -> uncheck “Enable DCOM on this computer”.
2. Turning off Script Debugging in IE.
3. Reboot.

Lubrano Diciccone Christophe (Last update 3/2/2004):
- GUID: 6CE8FEE6-A771-11D3-9B08-0090275F67ED - Appears when you try to install Oracle 8 client on a server. See Known software issue with Oracle 8i* installation for more details.

Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here!

Fred Logan (Last update 12/2/2003):
- GUID: {9B9A80E0-A9C0-11D2-B5E1-006008187232} - This error occurred on a Dell 4600 running Windows 200 Server and operating as a DNS Server and Domain Controller. When searching thru my server's registry, the GUID (Global Unique Identifier) referenced "VxVmCmd Command line Server". This references Dell's Array Manager. The problem is a timing issue between DCOM and Array Manager. The event error will occur only once upon boot. According to Dell support, it will hopefully be corrected when Array Manager 3.5 arrives. In the meantime, Dell support had me to search the registry for the GUID {9B9A80E0-A9C0-11D2-B5E1- 06008187232}. It should occur only twice. Delete the key for each instance. Reboot and Event 10010 is no more.

Anonymous (Last update 11/14/2003):
I looked in the registry for the GUID listed in the error, and found it was related to the Dell OMCI errors I was getting - which is basically Dells intrusion detection system telling me every 30 minutes that my pc case had been opened at some time. I just needed to go into the BIOS and reset or disable this.

Wade Ramponi (Last update 9/6/2003):
This problem showed up after enabling page heap through gflags.exe. The problem occurred every 60 seconds. After disabling this and rebooting, the error was no more.

Fred (Last update 9/6/2003):
The component GUID {80EE4901-33A8-11D1-A213-0080C88593A5} belongs to the Diskeeper defragmentation program. Activating "Paging File Frag Guard" and "MFT Frag Guard" on all volumes makes this error disappear.

Joe Rodríguez (Last update 9/6/2003):
In my case the GUID was: 4FB6BB00-3347-11D0-B40A-00AA005FF586 which is related to dmadmin, the Logical Disk Manager Administrative Service. As I found out it seams that it has moved to "manual start". Resetting it to "automatic" solved the problem.

Gary Karasik (Last update 9/6/2003):
In some cases at least, this error is profile-related. On a workstation that has several different users, I noticed the error was regularly absent when one user logged in but regularly present when another user logged in. Simply deleting the problem user's profile and recreating it didn't fix the error. I rebooted that workstation but didn't log in. From a different workstation I deleted the profile of the problem user and renamed the problem workstation's Default User profile to Default User.BAK. I copied the profile of the "clean" user and renamed it Default User. I logged into the problem workstation (as the problem user recreated the profile), and the error went away.

Niendertal (Last update 8/25/2003):
If you have an event like 7024 after this error, then it may be better to fix that first before dealing with event ID 10010. As a rule of thumb, look for events that provide you more information about the applications that generates the error.

Llefkowicz (Last update 8/25/2003):
If the GUID points to the Background Intelligent Transfer Service (Do a search in the registry for the GUID), it could be that the Network folder in %systemroot%\Documents and Settings\All Users\Application Data\Microsoft is missing. Create the folder then restart the service (net start bits).

Anonymous (Last update 8/25/2003):
In my case this was caused by the Instant Messaging component of Outlook XP. So I disabled using Tools, Options, uncheck Instant Messaging Support.

Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here!

Jonathan Schwartz (Last update 7/23/2003):
GUID: {D61A27C6-8F53-11D0-BFA0-00A024151983} is a problem with Removable Storage. It means that some settings in DCOM for Removable Storage are not registered properly. I ran DCOMCNFG and the minute I ran it - it stated that it wanted to register two GUID's that were listed in DCOM but not the AppID section of the registry. When I said yes and rebooted, the error went away.

Captain Confuzed (Last update 6/16/2003):
If the component GUID is: FB7199AB-79BF-11D2-8D94-0000F875C541 this is because the MSN/.net Messenger service cannot start. Check the following registry key for the user trying to log on:
HKEY_CURRENT_USER\Software\Microsoft\MessengerService
Value: PrimaryService
Type: String
Data: ".NET Messenger Service" (without quotes). See M325717 for more information.

Bernardo van Hoof (Last update 6/16/2003):
On my machine, this error was reported by HPAiO Device, a component of the OfficeJet G85xi. This error occurs on fast machines with antivirus software running (I tested this with Sophos as well as Norton). A workaround (for Sophos) is to set all Sophos services to manual and, after the HP officeJet is loaded, start the services.

Simon Hogg (Last update 6/16/2003):
This error occured to me when GroupShield was automatically updating the virus definition files.  This msg came up every few seconds and users were blocked from accessing Exchange resources. This was resolved with a swift reboot to restart all the services.

Anthony Hessler (Last update 6/16/2003):
GUID AAB71939-CBFF-11D2-960F-000629F011E9. This error Identified an IBM subcomponent in the registry. But the real cause of the error was the Inetpub directory being moved from the default C:\ directory to D:\. When IIS was installed a new catalog was created in the Indexing Service labeled WEB. After the Inetpub directory move the catalog was still trying to index the directory in its original location. The fix is to go into Services and Applications under Computer Management. Locate the Indexing Service and delete the WEB entry under there. Then recreate the catalog by clicking on Indexing Service, select ACTION from the toolbar, choose NEW, CATALOG. Name it Web and point it to the new location for Inetpub. The DCOM entries will dissappear.

Jevgenij Martynenko (Last update 6/16/2003):
I had the same error in combination with the problem stated in the M326607 and M326460 ("Service-Specific Error code -2147944102" Error Message If You Try to Start the Background Intelligent Transfer Service (BITS) Service). Fixing the problem with BITS service fixes the problem with DCOM.

Anonymous (Last update 6/16/2003):
In my case this occured due to an HP Officejet printer, using driver version 2.43. Upgrading to new v 2.50 cured this.

As per Microsoft, if you receive this error in a Windows 2000 environment do the following to the users registry:
1. Start Registry Editor (Regedt32.exe).
2. Locate and then click the following key in the registry:
   HKEY_CURRENT_USER\Software\Microsoft
3. On the Edit menu, click Add Key, and then add the following registry value:
   Key name: MessengerService
4. Open the MessengerService Key:
5. On the Edit menu, click Add Value, and then add the following registry value:
   Value name: PrimaryService
   Data type: REG_SZ
   Value data: .NET Messenger Service
6. Quit Registry Editor.
Confirmed to work, however it would be required to do the same procedure for all present & future domain users (ok for admins)hopefully MS will have a permanent fix.

Mark Adams (Last update 4/28/2003):
The error occurred (on SBS2000) every 30 seconds. According to Microsoft the event occurs because those object classes are considered user globals by Dcom and Terminal Server. See M187146.

Cody Pack
I resolved this issue on a Windows 2000 Server serving Siebel Document Server. I found that the ID in my error message ({D45FD2FC-5C6E-11D1-9EC1-00C04FD7081F}) referenced the Microsoft Agent Server 2.0 which serves the Office Assistant. I knew to look in Dcom config, since the setup of Siebel Document required an edit of DCOM. Run dcomcnfg, double click Microsoft Agent Server 2.0, Edit "Use Custom Configuration Permissions" on the Security Tab, and add INTERACTIVE from the local machine with Full Control access. This made my errors go away.

Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here!

Jeff Reid
I found another cause of this error. My GUID happened to be E0B8F398-BB08-4298-87F0-34502693902E.  This is a MS Instant Message object. I got this error when I opened Office XP Pro on a Windows XP Pro machine. OLXP would hang about 1 minute before it would open to the Inbox. The 10010 was generated everytime. This was caused by disabling IM via local policies in an attempt to prevent IM from running. (I personally do not like IM and it is annoying for it to ALWAYS pop-up on its own with no way to uninstall it). When OLXP is launched, it looks for IM for your contacts. Other events seem to spawn IM to launch even after you close it. I re-enabled IM from the policies and the Dcom is gone and OLXP opens as normal. I found M290025 that addresses the OLXP/IM issue, but it doesn't reference the DCOM error. My issues was with OLXP with POP, not Exchange.

Don Curtiss
In my case, this event occurred when I restarted Windows 2000 Server after setting up a subweb with IIS 5.0 and deleting it from the wwwroot without using the Sharepoint Administrator Frontpage(2002) to delete the subweb. To fix the problemm, I re-created a subweb web with the identical name in Sharepoint Administration and deleted it with the Sharepoint Administrator. I was left with no folders in the wwwroot and no error message upon reboot.

Maciej Plewa
This event may appear after deactivation of Windows Messenger in Windows XP. For more information and the solution visit http://www.tweakxp.com/tweakxp/display.asp?id=108.

Michael Waites
if event IDs 4205 and 36 occur then the problem is that the identity for the com+ application or the Microsoft Transaction Server (MTS) package is configured for "Interactive user - the current logged on user". Because no user is currently logged on to the IIS console, the application cannot run. See M282073

Dennis Annfeldt
I encountered this when I tried to install Backup Exec Agent Accelerator when it already existed on the server.
LinksM177510, M187146, M194396, M238665, M247962, M252638, M263900, M266118, M280719, M282073, M290025, M309051, M312074, M325717, M326306, M326460, M326607, M327153, M820461, M823661, M824196, M825118, M826382, M839880, M870655, M870694, M873375, M884870, M891330, M903072, M909444, M912063, M959117, www.tweakxp.com, OE Performance, Known issues with Oracle 8i* install, NetIQ NETIQKB26239, Veritas Support Document ID: 270419, Citrix Support Document ID: CTX104956, Citrix Support Document ID: CTX112168, McAfee Support Solution ID: nai3134, EventID 37 from source W3SVC, MSW2KDB, Adi Oltean Blog
Search Google Web - Microsoft Support - Bing - EventID.Net Queue - More links...
Custom search The custom search information is available to subscribers only.
Feedback Send comments - Notify me when updated
 Print version