NTBackup and DCOM error

[Guest]

Greetings

Just updated to SP2 and all was going well. I have a home box, Intel
D845EBG2 mobo with a 1.7 Ghz chip, 1 G RAM, Nvidia display, HP 35470A SCSI
tape drive with an Adaptec SCSI card on board. Before SP2 I had no problems
running NTBACKUP and archiving to tape. Now, NTBACKUP wont start - it hangs
as an image in memory and every two minutes I get the following error:

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 11/13/2004
Time: 7:53:04 PM
User: xxxxxxxxxxx
Computer: xxxxxxxxx
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.

I get the same identical error if I try to start Removable Storage from the
mmc console. Any ideas?

Thanks!

Mark / Grand Forks ND

 

[CWatters]

Greetings

Just updated to SP2 and all was going well. I have a home box, Intel
D845EBG2 mobo with a 1.7 Ghz chip, 1 G RAM, Nvidia display, HP 35470A SCSI
tape drive with an Adaptec SCSI card on board. Before SP2 I had no problems
running NTBACKUP and archiving to tape. Now, NTBACKUP wont start - it hangs
as an image in memory and every two minutes I get the following error:

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 11/13/2004
Time: 7:53:04 PM
User: xxxxxxxxxxx
Computer: xxxxxxxxx
Description:
The server {D61A27C6-8F53-11D0-BFA0-00A024151983} did not register with DCOM
within the required timeout.

claims it was fixed in SP2...

http://support.microsoft.com/default.aspx?scid=kb;en-us;825118&FR=1&PA=1&SD=HSCH

Also try google for D61A27C6-8F53-11D0-BFA0-00A024151983 - might turn up
something.

 

[Guest]

Greetings

I should have put in my post that I've found several fixes on the MS and
other sites, but still no luck. I was wondering if anyone else has run into
this specific issue. I ran the file checker (SFC /scannow) and some files
were reparied. I also found quite a few hits on sites relating to this error.
However, what is odd is the fact that the Removable Storage snap in hangs and
generates the same error.

Thanks for the help!

MisterWeather