Re: DCOM Errors in Event Logs.

Here are the enents logged on the workstation.
this is from the workstation
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10009
Date: 3/29/2006
Time: 2:16:49 PM
User: xxxxxxx\xxxxxx
Computer: xxxxx
Description:
DCOM was unable to communicate with the computer dell1600 using any of the
configured protocols.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

and here is the event logged on the server.
Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 537
Date: 3/29/2006
Time: 9:06:43 PM
User: NT AUTHORITY\SYSTEM
Computer: xxxxxx
Description:
Logon Failure:
Reason: An error occurred during logon
User Name: xxxxxx
Domain: xxxxxxx
Logon Type: 3
Logon Process: Kerberos
Authentication Package: Kerberos
Workstation Name: -
Status code: 0xC00002EE
Substatus code: 0x0
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: -
Source Port: -


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

"JerryP" <annoymous@xxxxxxxxxxxxx> wrote in message
news:e88gTNHVGHA.4956@xxxxxxxxxxxxxxxxxxxxxxx
What do you suggest I do, should I try removing the HP printer, reboot and
see if the log clears. I am desperate for any kind of help right now.

"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa@xxxxxxxxxxx>
wrote in message news:eJnwLJHVGHA.6084@xxxxxxxxxxxxxxxxxxxxxxx
These days when I see dcom errors it may be those stupid HP printer
monitors.

Russ Grover wrote:

There should be more than just that error what else does it give?
IE like unable to connect to computer or something like that.

(I remember seeing those last year a lot on servers but not recently)
How is your server for Service packs and Updates? etc?






.

Relevant Pages