DCOM error in event log

[Richard Annison]

Can anyone help me with this problem, I have run SFC /scannow but it hasn't
helped.


Source: DCOM
EventID: 10003

Access denied attempting to launch a DCOM Server using
DefaultLaunchPermssion. The server is:
{00020906-0000-0000-C000-000000000046}
The user is Unavailable/Unavailable, SID=Unavailable.

 

[zizz]

This is not a serious problem - but it can be a pain to
get rid of. Google up Gibson's DECOMbobulator and read
the material that goes along with this freebie utility.
You may notice that it occurs about every two minutes,
and it will usually go away if you turn off your firewall.
Not sure what gets it started but Messenger service is one
suspect. Don't think it's in any way virus related/
zizz

 

[sinbad]

Take a look here :
http://www.annoyances.org/exec/forum/winxp/1081190860

sts -

 

[John R. Sellers]

This is not a serious problem - but it can be a pain to
get rid of. Google up Gibson's DECOMbobulator and read
the material that goes along with this freebie utility.

I was just about to suggest that.

http://grc.com/dcom/

 

[Andrew Portess]

Can anyone help me with this problem, I have run SFC /scannow but it hasn't
helped.


Source: DCOM
EventID: 10003

Access denied attempting to launch a DCOM Server using
DefaultLaunchPermssion. The server is:
{00020906-0000-0000-C000-000000000046}
The user is Unavailable/Unavailable, SID=Unavailable.

Are you reading the error in the Event Viewer? Have you disable any of the
Win XP services? Have you suddenyl lost any functionality of XP? Can't
remember which services it is but this can be caused by disabling various
services within XP - even if you don't need them running DCOM may rely in
them. If it isn't causing a problem then don't worry about it - there are
numerous messages that come up in the event viewer which might suggest a
problem but in reality they are not an issue. Search google for Black
Vipers website on XP services for more info.

Andy

 

[Richard Annison]

Thanks for the help DCOMbob has disabled DCOM and the errors seem to have
gone away.

I'd still like know what caused the error. It only started about a week ago.

At least its fixed.

Thanks

Richard