Re: COM+ Event System Errors with IDs of 4621?



Dick K
07-10-2005, 12:43 AM
Dick K wrote:
> I'm running fully updated XP SP2 and instances
> of COM+ Event System Errors with Event IDs
> of 4621 recently started to appear in my
> application log.
>
> The event which immediately preceded the first
> occurence of the error was a success audit
> which looks as if it has some bearing on the
> matter.
>
> I'm guessing that the errors are not
> particularly significant but I'd be grateful
> if anyone can confirm this and suggest
> a way of eliminating them?
>
> The properties of each error event are:
>
> Source: EventSystem
> Category (50)
> Event ID: 4621
> Description:
> The COM+ Event System could not remove the
> EventSystem.EventSubscription object {A5978620-
> 5B3F-F1D1-8ED2-00FA0035B753}-{00000000-0000-
> 0000-0000-000000000000}-{00000000-0000-0000-
> 0000-000000000000}. The HRESULT was 80070005.
>
> The proprties of the success audit event are:
>
> Source: OfficeUpdateV3
> Category: None
> Event ID: 0
> Description:
> The description for Event ID ( 0 ) in Source
> ( OfficeUpdateV3 ) cannot be found. The local
> computer may not have the necessary registry
> information or message DLL files to display
> messages from a remote computer. You may be
> able to use the /AUXSOURCE= flag to retrieve
> this description; see Help and Support for
> details. The following information is part
> of the event: V3_2|512156|INSTALL|WINWORD_
> 6754_INTL||2005-04-17 5:20:04|9|SUCCESS|||.

This isn't solved and after a lot of trial and,
mostly, error I've conceded defeat. I noticed a
few things on the way which might just be of
interest to someone so I'll put them on record.

Fast User Switching is involved. I have one admin
and one limited account and I found that If I
always logged off one account before logging
on to the other the errors no longer occurred.
This was too cumbersome to be an acceptable
workaround.

Windows Messenger is also involved. I disabled
it for other reasons and found that I could then
switch between logged on accounts without
any errors appearing. That's acceptable and
it's where I've left things. I disabled Windows
Messenger using the registry hack for "Windows
Messenger 4.5 or later versions on on a Windows
XP Home Edition based computer" described at:

http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B302089

I'm not sure about the relevance of this last
bit but I'll put it in anyway. Somewhere during
the odyssey the Service Control Manager started
generating system log errors with Event IDs of
7023 - "The Application Management service
terminated with the following error: The specified
module could not be found". Since the Application
Management Service is not supported in XP Home
(and Appmgmt.dll is not supposed to be there
to be found)I changed its startup configuration
from Manual to Disabled. That stopped the errors
and may have cured a (then) newly developed
tendency for my ADSL connection to drop out
occasionally.

Dick K

Dick K
07-10-2005, 12:43 AM
Dick K wrote:
> Dick K wrote:
>
>> I'm running fully updated XP SP2 and instances
>> of COM+ Event System Errors with Event IDs
>> of 4621 recently started to appear in my
>> application log.
>>
>> The event which immediately preceded the first
>> occurence of the error was a success audit
>> which looks as if it has some bearing on the
>> matter.
>>
>> I'm guessing that the errors are not
>> particularly significant but I'd be grateful
>> if anyone can confirm this and suggest
>> a way of eliminating them?
>>
>> The properties of each error event are:
>>
>> Source: EventSystem
>> Category (50)
>> Event ID: 4621
>> Description:
>> The COM+ Event System could not remove the
>> EventSystem.EventSubscription object {A5978620-
>> 5B3F-F1D1-8ED2-00FA0035B753}-{00000000-0000-
>> 0000-0000-000000000000}-{00000000-0000-0000-
>> 0000-000000000000}. The HRESULT was 80070005.
>>
>> The proprties of the success audit event are:
>>
>> Source: OfficeUpdateV3
>> Category: None
>> Event ID: 0
>> Description:
>> The description for Event ID ( 0 ) in Source
>> ( OfficeUpdateV3 ) cannot be found. The local
>> computer may not have the necessary registry
>> information or message DLL files to display
>> messages from a remote computer. You may be
>> able to use the /AUXSOURCE= flag to retrieve
>> this description; see Help and Support for
>> details. The following information is part
>> of the event: V3_2|512156|INSTALL|WINWORD_
>> 6754_INTL||2005-04-17 5:20:04|9|SUCCESS|||.
>
>
> This isn't solved and after a lot of trial and,
> mostly, error I've conceded defeat. I noticed a
> few things on the way which might just be of
> interest to someone so I'll put them on record.
>
> Fast User Switching is involved. I have one admin
> and one limited account and I found that If I
> always logged off one account before logging
> on to the other the errors no longer occurred.
> This was too cumbersome to be an acceptable
> workaround.
>
> Windows Messenger is also involved. I disabled
> it for other reasons and found that I could then
> switch between logged on accounts without
> any errors appearing. That's acceptable and
> it's where I've left things. I disabled Windows
> Messenger using the registry hack for "Windows
> Messenger 4.5 or later versions on on a Windows
> XP Home Edition based computer" described at:
>
> http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B302089
>
> I'm not sure about the relevance of this last
> bit but I'll put it in anyway. Somewhere during
> the odyssey the Service Control Manager started
> generating system log errors with Event IDs of
> 7023 - "The Application Management service
> terminated with the following error: The specified
> module could not be found". Since the Application
> Management Service is not supported in XP Home
> (and Appmgmt.dll is not supposed to be there
> to be found)I changed its startup configuration
> from Manual to Disabled. That stopped the errors
> and may have cured a (then) newly developed
> tendency for my ADSL connection to drop out
> occasionally.
>
> Dick K

Sorry everyone. Tried to add to an old post
using "reply to" and somehow generated a new
one. Guess the oringinal post was gone from
server but not from my mail cache.

Dick K

Rock
07-10-2005, 12:44 AM
Dick K wrote:


> This isn't solved and after a lot of trial and,
> mostly, error I've conceded defeat. I noticed a
> few things on the way which might just be of
> interest to someone so I'll put them on record.
>

Thanks for posting back. It will help others.

--
Rock
MS MVP Windows - Shell/User


Re: COM+ Event System Errors with IDs of 4621?