COM+ Event System error after latest Windows XP updates

I just installed the latest batches of Windows XP updates that were waiting
for me this morning 07/16/2005. Now every time I reboot my computer I get a
serious event error goes something like this "The COM+ Event System detected
a bad return code during its internal processing. HRESULT was C0000005 from
line 44 of d:\qxp_slp\com\com1x\src\events\tier1\eventsystemo bj.cpp. Please
contact Microsoft Product Support Services to report this error." When I send
to Microsoft I get the message back that there is no additional
information.....lots of help there..does anyone know what I can do to take
care of this error....it wasn't there this morning when I booted up first
time before updates, but each reboot after the updates the error is there....

Thanks in advance for anyones help!

Woody

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Woody wrote:
> I just installed the latest batches of Windows XP updates that were waiting
> for me this morning 07/16/2005. Now every time I reboot my computer I get a
> serious event error goes something like this "The COM+ Event System detected
> a bad return code during its internal processing. HRESULT was C0000005 from
> line 44 of d:\qxp_slp\com\com1x\src\events\tier1\eventsystemo bj.cpp. Please
> contact Microsoft Product Support Services to report this error." When I send
> to Microsoft I get the message back that there is no additional
> information.....lots of help there..does anyone know what I can do to take
> care of this error....it wasn't there this morning when I booted up first
> time before updates, but each reboot after the updates the error is there....

Hmm today I noticed that the COM+ Event System on my Windows 2000 SP4
machine had died. I tried various different things to try and get it
working or even to see why it wasn't working, but couldn't find anything.

I got the following in my Application Event Log twice after which COM+
wouldn't start (Timeout (30000 milliseconds) waiting for the COM+ Event
System service to connect.):

The COM+ Event System detected a bad return code during its internal
processing. HRESULT was 8007041D from line 42 of .\eventsystemobj.cpp.
Please contact Microsoft Product Support Services to report this error.

I searched fairly extensively on the Web for that return code and although
there were quite a few results I couldn't find anything relevant.

In the end I just restored a disk image I took a few days ago and it's
working fine now.

- --
Adam Piggott, Proprietor, Proactive Services (Computing).
http://www.proactiveservices.co.uk/

Please replace dot invalid with dot uk to email me.
Apply personally for PGP public key.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)

iD8DBQFC2Seo7uRVdtPsXDkRAme3AJ4w1NigXzIs8yTjm0GMqZ HAi4nolwCgh1jR
vm5Qolu7CQVeV2I3qqAPc+o=
=c6+3
-----END PGP SIGNATURE-----

Woody again. I just went through the Add/Remove programs and removed Windows
XP latest Security Update KB90214 and rebooted and this has fixed my problem.
I hope that Microsoft is also reviewing this message board and looks into the
problem that this update has or could cause. I will not reinstall it until I
get assurances from Microsoft that they have taken care of whatever problems
this update might cause. Thought I would let everyone know what I did to take
care of my problem.

"Woody" wrote:

> I just installed the latest batches of Windows XP updates that were waiting
> for me this morning 07/16/2005. Now every time I reboot my computer I get a
> serious event error goes something like this "The COM+ Event System detected
> a bad return code during its internal processing. HRESULT was C0000005 from
> line 44 of d:\qxp_slp\com\com1x\src\events\tier1\eventsystemo bj.cpp. Please
> contact Microsoft Product Support Services to report this error." When I send
> to Microsoft I get the message back that there is no additional
> information.....lots of help there..does anyone know what I can do to take
> care of this error....it wasn't there this morning when I booted up first
> time before updates, but each reboot after the updates the error is there....
>
> Thanks in advance for anyones help!
>
> Woody
>