DCOM and COM+ Errors

[TrojanSquirrel]

Hi,

I have a Win2000 pro system attatched to my network that I access via VNC and only use for file storage.

I have had this box as a regular desktop with no problems untill I moved it to my work and started using it as described above.

Now I get random restarts and DCOM errors in the system log (event id: 10005) and COM+ errors in the application log (event id: 4106 event system).

Just a thought; but could this be anything to do with VNC running as a system service?

Regards,

Rob

http://www.transcom.net

 

[bcastner]

I need Source:....... and Event ID to help you.

The first error, if it does not mention service starting issues, is informational.

These error messages are generated because another application, such as Microsoft Transaction Server, has already started the Dcom (the Distributed Component Object Model) Service. These messages do not indicate an actual problem and are benign." The recommended solution is to install the latest Service Pack

For the second, I would need the complete error text. But if you have QoS enabled on the client disable it.


____________________________
Users Helping Users

 

[TrojanSquirrel]

Hello sir.

The COM+ error's source is the Event System and the text is as follows:

The COM+ Event System raised an unexplained access violation at address 0x762A08C4, attempting to access address 0x00000000.
Please contact..... blah, blah, blah.
es!DllUnregisterServer+0x1084
es!DllUnregisterServer+0x1b9c
boinc!BOINClsNetworkAlwaysOnline+0x7af

The Dcom error is as follows:

DCOM got error "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it."
attempting to start the service EventSystem with arguments "" in order to run the server:
{1BE1F766-5536-11D1-B726-00C04FB926AF}

Just installed the latest updates for 2000pro and have not the restart yet.

Are these errors related to the restart problem, or should I be looking elsewhere? I've got a feeling it could be the bios battery failing and I'm chasing after ghosts in the machine!

As the first problem seems to be related to the Boinc screensaver (not updated for at least a year and has run fine on all my machines since it was released!), I'll disable it for a while.

Thanks as always mr bcastner!

Regards,

Rob

http://www.transcom.net

 

[bcastner]

{1BE1F766-5536-11D1-B726-00C04FB926AF}is the GUID of the COM+ Event Sevice.

It does not Like BOINC.


____________________________
Users Helping Users

 

[TrojanSquirrel]

Thanks for that. Now I know where to focus my attention.

Funny how an app can run happily for years and then after a os reinstall (clean) it starts to play up.

I've been running seti@home and later Boinc on all my personal machines since almost the start of seti@home and this is the first problem I have had with it. I even managed to get it to run on winME for at least three days in a row (usually had to fdisk and reinstall ME after such a long time running!!) without problems.... Still, we live and learn eh.

Good job there are people like you and some of the other TT regulars to teach the likes of I.

Thanks again.

Regards,

Rob

http://www.transcom.net

 

[bcastner]

A long shot but you might try Control Panel|Administrative
Tools|Component Services|Computers|My Computer|DCOM Config. When you clickon the DCOM Config branch. You may get notices that some EXE files are not completely registered. Make sure you recognize each application as a valid
program and say yes to record data regarding it.

____________________________
Users Helping Users

 

[TrojanSquirrel]

Thanks for all your help bcastner.

I have a feeling that the problem may have been with a failing HDD.

Soon after I started getting strange reboots and then the machine failed to boot to Windows. Further investigation showed bad sectors on the primary HDD.

It has now been replaced and Win 2000 pro and Boinc are playing nicely together now.

Thanks again for your help.