EventSystem & netman startup errors logged on bootup

  • Thread starter Thread starter Robert
  • Start date Start date
R

Robert

Every time I boot my Windows XP Home computer, the following two system
errors are logged:

Event ID 10005 - DCOM got error "The service database is locked. "
attempting to start the service EventSystem with arguments "" in order to
run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF}

Event ID 10005 - DCOM got error "The service database is locked. "
attempting to start the service netman with arguments "" in order to run the
server: {BA126AE5-2166-11D1-B1D0-00805FC1270E}

I recently did a clean (formatted drive) reinstall of Windows XP Home
Edition and added all updates. The computer is networked with one other.
Everything seems to be working very well, but I am concerned about these
errors that are logged with every bootup. They do not occur with the other
computer, which is essentially identical.

Could someone please tell what these mean, and their significance? I would
greatly appreciate any information or comments.

Thanks, Robert
 
Thanks for the reply. Your link took me to a MS page that explained how to
determine the vendor of the service programs in question, and that I should
contact the vendor. I found that netman was netman.dll and EventSystem was
es.dll. Unfortunately, the vendor of each is Microsoft.

Any other ideas? Thanks again, Robert
 
Netman is the Network Connections service in Services.

EventSystem is the COM+ Event System service in Services.

COM+ Event System
http://www.blackviper.com/WinXP/service411.htm#COM+_Event_System

Network Connections
http://www.blackviper.com/WinXP/service411.htm#Network_Connections

I ignore all DCOM errors.

Unless you need DCOM for anything...

DCOM Windows XP Do You Need It?
http://www.updatexp.com/dcom-windows-xp.html

How to disable DCOM support in Windows
http://support.microsoft.com/default.aspx?scid=kb;en-us;825750
 
Thanks much for the information; very educational. I notice that Network
Connections and COM+ Event System services are both running after boot up.
Perhaps they were already running when DCOM tried to start them? (just
guessing). I wonder why DCOM tried to start them. Maybe some rogue
application? Very interesting and confusing.

Robert
 
Robert,

You need Network Connections. You probably do not need COM+ Event System.

IMHO, DCOM *is* a rogue application. ;-)

For example...

I have DCOM and StiSvc disabled. StiSvc = Windows Image Acquisition (WIA).
WIA provides image acquisition services for scanners and cameras. I have
neither.

If I open any jpg file, I get a DCOM error.

[[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 StiSvc with arguments "" in order to run the
server.]]

No kidding, it's disabled. :-)
 
Back
Top