2K出错，传上日志，高手帮看看

anmin · 发表于 2004-10-18 12:06:15

事件类型: 错误 
事件来源: DCOM 
事件种类: 无 
事件 ID: 10010 
日期: 2004-10-18 
事件: 11:26:16 
用户: HAOSHUAI\attn 
计算机: ATTN 
描述: 
服务器 {9F92FFA3-40D1-475A-9323-A39C705DAB86} 没有在限定的时间内用 DCOM 注册。 那位高手能告诉我解决的方法，先谢谢了！

bad · 发表于 2004-10-19 16:12:13

这么多，你看是哪一个能解决你的问题： 
Adrian Grigorof (Last update 8/25/2003): 
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 Q263900 
- 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 Q194396. 
- 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 Q238665 
- In NT 4.0 this event can also occur if Internet Explorer 4.0 is installed (without any Service Pack). See Q177510 
 
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 Q823661. 
 
Ionut Marin (Last update 9/27/2004): 
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 Q327153 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 Q280719 for more information. 
 
- GUID: {D61A27C6-8F53-11D0-BFA0-00A024151983} - See Q825118 for a hotfix. 
- GUID: {FB7199AB-79BF-11D2-8D94-0000F875C541} - See Q325717. 
- GUID: {B6EC1632-E61D-11D2-85EA-0000F87A5571} - See Q247962. 
- GUID: {02D4B3F1-FD88-11D1-960D-00805FC79235} - See Q326306. 
- GUID: {3D14228D-FBE1-11D0-995D-00C04FD919C1} - See Q309051. 
- GUID: {A9E69610-B80D-11D0-B9B9-00A0C922E750} - See Q252638. 
- GUID: {8BC3F05E-D86B-11D0-A075-00C04FB68820} - See Q839880. 
- GUID: {590A29BA-CF7E-4034-82AB-CBBEF9BA844E} - See Q870694. 
- GUID: {601ac3dc-786a-4eb0-bf40-ee3521e70bfb} - See Q873375. 
- GUID: "Network Crawler" - See Q873375. 
- GUID: {27B04BDE-684A-415B-9F6E-187EDD0BD419} - See "Veritas Support Document ID: 270419". 
 
If you experience problems with Outlook Express running very slow, take a look at "Insideoe.tomsterdam.com"(see the link below). 
 
Also check Q312074, Q820461, and "Microsoft event 10010 from source DCOM" 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 Q826382 to see how to disable DCOM support in RPC over HTTP for Win2k3 servers. 
 
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 di ciccone 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. 
 
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.

		自动登录	找回密码
密码			会员注册

2K出错，传上日志，高手帮看看

re:这么多，你看是哪一个能解决你的问题：...

浏览过的版块