Odd EventSystem Error

[Guest]

I just checked my Error Log in the "Help and Support Center" for the first
time. I'm running XP Pro SP2 (clean install), with all the latest updates.

I notice I get the following error every day: "The COM+ Event System
detected a bad return code during its internal processing. HRESULT was
8007041F from line 44 of d:\qxp_slp\com\com1x\src\event
s\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services
to report this error."

There are several other errors I also get every day. My computer doesn't
crash, but these things are in my error log. Here are the others:

Service Control Manager -- The Bac1ammgl service failed to start due to the
following error: The system cannot find the file specified.

DCOM -- DCOM got error "%1055" attempting to start the service EventSystem
with arguments "" in order to run the server: {1BE1F766-5536-11D1-B
726-00C04FB926AF}

DCOM -- DCOM got error "%1055" attempting to start the service netman with
arguments "" in order to run the server: {BA126AE5-2166-11D1-B
1D0-00805FC1270E}

Like I said, these are reported every day, so I have dozens of these in the
log. At least it's consistent. And as I said, the computer seems to be
working fine.

1 - Should I "report this error"? To whom?

2 - Does anyone recognize these errors or have any suggestions?

Thanks for any help. Googling and searching on the MS site didn't give me
anything useful.

 

[vasudhagoteti]

Hi Brain,
Did you find an answer for your questions?? Even I am facing the same
problem, I get these error messages and all of a sudden my laptop
shutsdown without any warning and I checked the error log and found all
these messages.. do let me know if you have found anything about these
errors.
Thanks.

 

[Guest]

Not all of them. I never did figure out what the Bac1ammgl service was. Very
frustrating, and I get that error *every* time I boot up. It does not appear
to be a real service, and I can't figure out where the file is even specified
so I can delete it. Regedit won't let me delete the Bac1ammgl keys and
subkeys. It appears to be a parallel arbitrator (a type of parallel port
driver, I guess), but it does not have a file reference or even a space in
the Administrative Tools>Services dialog. Anyway, I am living with that error
with no ill effects other than a chronically long error log.

The DCOM errors I was able to fix. It's a long story, but just try this:
create a password for yourself to log onto Windows. I'm assuming your
computer just boots up right now without any login.

Apparently, the little pause created by making you log on is enough that the
services start up without the problems. Hopefully this will work for you. It
worked for me. Good luck!