Windows Server 2003 Standard - DCOM Problems

Recently, my Windows Server 2003 box started acting up. I am not sure
if one of the hotfixes downloaded automatically by the server caused
this or a recently installed application is the culprit.

When the server boots, it goes all the way to the CTRL+ALT+DEL window.
After logging in, the Windows Desktop and Taskbar just seem to never
appear. It just sits there. Eventually, after several minutes, the
desktop appears but is generally unresponsive. In Safe Mode, the
desktop appears with no problems.

After some research and troubleshooting, I was able to get to the
desktop by disabling the Computer Browser service and the DCOM Server
Process Launcher service. By doing so several applications no longer
work like Backup Exec.

I searched the Microsoft Knowledge Base and found the following
article:
http://support.microsoft.com/kb/904388/en-us

So, I called Bill over at Microsoft and was sent the following hotfix:
http://support.microsoft.com/kb/910730/

After it was installed, I re-booted the server and was able to get to
the desktop. But, I enabled the two offending services, BAM! The
server freezes up again and becomes unresponsive. Now, I am back to
square one.

I ran MSCONFIG, disabled all non-Microsoft services, re-booted again,
enabled the two services, BAM! Same problem.

Has anyone seen this or experiencing the same problems?

When DCOM is enabled, I receive the following errors:

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 8/19/2006
Time: 9:38:18 AM
User: N/A
Computer: BIGPAPA
Description:
The server {BA126AE5-2166-11D1-B1D0-00805FC1270E} 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.


and

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 8/19/2006
Time: 9:30:54 AM
User: N/A
Computer: BIGPAPA
Description:
The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} 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.

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

[niallo32]

The same thing happened me and I used the same solution to resolve the problem.

Did you identify what MS Update caused the problem??

Thanks...

This solution helped us to. Thanks god for your brain! :D

just to thank you for you sharing this solution that really solved my problem.
An additional note for anyone who may need, i applied the same solution in a
Windows 2003 Server (NT 5.2 SP1) box and in a Windows XP SP2 Tablet PC and
everything is working fine!

[Scubabob]

Thanks Wavellan for the info on the security permissions for CLSID tree

I also had the following problems occur after
Applications run on server kept disabling Network card IP (broadcom, netxtreme II)

fix was Component services\Computers\My computer\DCOM config\netman object
Add permissions
NETWORK SERVICE check the following
Local Launch
Remote Launch
Local Activation
Remote Activation

Next was to update the Network card driver to ver 5.2

This seemed to fix all the problems, haven't had a reoccurance of the problem for two days now

Cheers