DCOM error in Windows 2003 Server System Log

wayne · 08-12-2004, 04:11 AM

Approximately evey two and half hours I get the following message in the System event log:

DCOM got error "The operation completed successfully. " and was unable to logon PCUWNET\sweepupd in order to run the server: {3E2E4965-2518-40A4-A72B-95FCE2809D03}

As usual I cannot find anything on the Microsoft website! I did have an account sweepupd which was used for Sophos Anti Virus updates but I have removed this. All Sophos services are running with the System account.

Any help would be very much appreciated.

ashishm79 · 12-29-2007, 09:25 AM

Can anybody help me out with the DCOM error in Windows 2003 Server system log

Karnivore · 01-03-2008, 05:57 AM

Have a look through this post: shut Down Promblems

I used the fix at the bottom, and it solved my problem (although mine were more to do with a slow shutdown)

08-12-2004, 04:11 AM	#1 (permalink)
wayne Registered User Join Date: Jul 2004 Posts: 3 OS: 2000	DCOM error in Windows 2003 Server System Log Approximately evey two and half hours I get the following message in the System event log: DCOM got error "The operation completed successfully. " and was unable to logon PCUWNET\sweepupd in order to run the server: {3E2E4965-2518-40A4-A72B-95FCE2809D03} As usual I cannot find anything on the Microsoft website! I did have an account sweepupd which was used for Sophos Anti Virus updates but I have removed this. All Sophos services are running with the System account. Any help would be very much appreciated.

12-29-2007, 09:25 AM	#2 (permalink)
ashishm79 Registered User Join Date: Dec 2007 Posts: 1 OS: WIN2003 SP3	Re: DCOM error in Windows 2003 Server System Log Can anybody help me out with the DCOM error in Windows 2003 Server system log

01-03-2008, 05:57 AM	#3 (permalink)
Karnivore Registered User Join Date: Dec 2007 Location: Stoke, UK Posts: 7 OS: XP Pro, SP2	Re: DCOM error in Windows 2003 Server System Log Have a look through this post: shut Down Promblems I used the fix at the bottom, and it solved my problem (although mine were more to do with a slow shutdown)