Prev: Unable to connect using RDP
Next: Scheduled Task error code:The task completed with an exit code of
From: Paulo Lima on 20 Feb 2007 07:07
I found a solution in
"Windows Server 2003 Standard - DCOM Problems in General Discussion"
where Wavellan proposed:
-----------------
For those of you who are interested, I finally resolved this issue. It
apears as some MS patch changed the permissions on the following
registry key:

HKEY_CLASSES_ROOT\CLSID

In order to resolve the problem, the following permissions were added

Registry Key: HKEY_CLASSES_ROOT\CLSID (and all child keys and values)

Permissions Added:

Authenticated users: Read access
Network Service: full control
--------------------
I recommend a full reading of the reffered article.
Good luck.


"lushtanet" wrote:

> Helo everybody
>
> I have an error log under my system event, which pops up every time I
> restart the server.
>
> Event Type: Error
> Event Source: DCOM
> Event Category: None
> Event ID: 10010
> Date: 11.07.2005
> Time: 23:51:03 PM
> User: N/A
> Computer:
> Description:
> The server {D61A27C6-8F53-11D0-BFA0-00A024151983} did not register with DCOM
> within the required timeout.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> As sugested by microsoft online help I shoud contect the vendor of the
> aplications cosing this error. From the registry settings I can see that it's
> about this .dll file:
> "C:\WINNT\system32\ntmssvc.dll"
>
> This error log started to pop up after I have upgradet the Win2k Advance
> server to win 2003 ent SP1.
>
> Any ideas on this whay I'm geting this error log.
 | 
Pages: 1
Prev: Unable to connect using RDP
Next: Scheduled Task error code:The task completed with an exit code of