MonitorWare Knowledge Base

Anonymous wrote:^^^^ That was actually a changed one i got after starting in safe mode.
The usual one is;

The server {9F92FFA3-40D1-475A-9323-A39C705DAB86} did not register with DCOM within the required timeout.

Help???

therget wrote:Hi all,

I found a Microsoft Knowledge Base Article concerning the DCOM 10010 Error :

Microsoft Knowledge Base wrote:...

SYMPTOMS

Distributed Component Object Model (DCOM) client programs that run inside Terminal Server sessions other than the console cannot create objects of classes implemented inside DCOM servers running as Terminal Server services.

You may also receive occurrences of event ID 10010 from DCOM in the Event Viewer with the following description:

The server <clsid> did not register with DCOM within the required timeout.
...

CAUSE

...


RESOLUTION

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To explicitly register a DCOM class as a system global, use the following steps:


1. If it does not exist, create the following registry key:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\CLSID

2. Create a subkey with {CLSID} as its name, where the CLSID is the class identifier of the DCOM class that is to be a system global. For example, a subkey would be:

{41116C00-8B90-101B-96CD-00AA003B14FC}

3. Under the above subkey, create fSystemGlobalClass as the value name with a REG_DWORD type and set its value data to 1.

Or, you can upgrade to Microsoft Windows 2000 Server with Terminal Services, which does not have the same restriction.

...

Please notice that you use the registry editor at your own risk.



Regards,
Timm Herget
Adiscon

Jim D wrote:Frustrated by the same DCOM error. Has anyone resolved it? It has only begun happening in the last few weeks, so I suspect the latest Critical Updates. Has anyone found how to stop it?
What about "disabling" the DCOM service?

RESOLUTION

Add these users back to the Users group, and then restart Internet Information Services (IIS):
1. Click Start, click Programs, click Administrative Tools, and then click Computer Management to open the Computer Management console.
2. In the left pane, expand Local Users and Groups, and then click the Groups folder.
3. In the right pane, right-click the Users group, and then click Properties.
4. Click Add.
5. In the Select Users or Groups dialog box, locate the Look in drop-down box, and then select the local computer.
6. Select Authenticated Users, and then click Add. Select INTERACTIVE, and then click Add. Click OK, click Apply, and then click Close to close the properties for the Users group.
7. In the left pane, expand Services and Applications, and then click Services.
8. In the right pane, right-click IIS Admin Service, and then click Restart.
9. In the Restart Other Services confirmation dialog box, click Yes.

Anonymous wrote:^^^^ That was actually a changed one i got after starting in safe mode.
The usual one is;

The server {9F92FFA3-40D1-475A-9323-A39C705DAB86} did not register with DCOM within the required timeout.

Help???

start -> run
Dcomcnfg.exe