Error 7023

[Peter]

I get error 7023 repeatedly whenever I delete a programme.

I can't understand how to get the Hotfix below, and whether it is applicable
to XP SP3.

http://support.microsoft.com/kb/328213/en-us

help!

JB

 

[MowGreen [MVP]]

Is the system event log showing the exact same error as in the KB
article ? Update.exe should have been updated to a much higher version
[the latest is V. 6.3.13.0] than what is showing in the article by the
installation of SP2 and SP3, along with the myriad security updates
issued since this KB was published.

MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============

 

[Peter]

As far as Error 7023, it only happens when I Add/Delete a program (I think
only deleting). I have other Errors: 10010 DCOM which happens EVERY TIME I
start the computer and I don't know what to do; and ID1 ACPIEC which is
happening more and more frequently and again I am at a loss.

Any help on these would be much appreciated, so that I try to understand
what is going on in my very slow computer. All the MS updates are up to
date. I have XP Home SP3.

Below the errors that I keep getting:


Product: Windows Operating System
ID: 7023
Source: Service Control Manager
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_SERVICE_EXIT_FAILED
Message: The %1 service terminated with the following error:
%2

Explanation
The specified service stopped unexpectedly with the error indicated in the
message. The service closed

safely.


--------------------------------------------------------------------------------------------------------------------------------------------------------------

Product: Windows Operating System
ID: 10010
Source: DCOM
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_RPCSS_SERVER_START_TIMEOUT
Message: The server %1 did not register with DCOM within the required
timeout.

Explanation
The Component Object Model (COM) infrastructure tried to start the named
server; however, the server

did not reply within the required timeout period. There might be a deadlock,
or the program might not

have responded to the server initialization code within the timeout period
of two minutes

-----------------------------------------------------------------------------------------------------------------------------------------------------------

Product: Windows Operating System
ID: 1
Source: ACPIEC
Version: 5.2
Symbolic Name: ACPIEC_ERR_WATCHDOG
Message: %1: The embedded controller (EC) hardware didn't respond within the
timeout period. This

may indicate an error in the EC hardware or firmware, or possibly a poorly
designed BIOS which

accesses the EC in an unsafe manner. The EC driver will retry the failed
transaction if possible.

Is the system event log showing the exact same error as in the KB article
? Update.exe should have been updated to a much higher version [the latest
is V. 6.3.13.0] than what is showing in the article by the installation of
SP2 and SP3, along with the myriad security updates issued since this KB
was published.

MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============

I get error 7023 repeatedly whenever I delete a programme.

I can't understand how to get the Hotfix below, and whether it is
applicable to XP SP3.

http://support.microsoft.com/kb/328213/en-us

help!

JB

 

[R. McCarty]

Has this computer ever had a Registry Cleaner used on it ? Also has
any Services had their Start Mode modified. It seems to me like you've
got a series of dependency group failures. I would clear both the App
and System Event Logs and do a reboot. Then check both logs for all
warnings and errors. Does your boot cycle time run ~45-60 Seconds
or is it significantly longer.

As to the hardware issue does your Device Manager have a clean
listing ? - ( No Red X's or Yellow Exclamation marks ).

As far as Error 7023, it only happens when I Add/Delete a program (I think
only deleting). I have other Errors: 10010 DCOM which happens EVERY TIME
I start the computer and I don't know what to do; and ID1 ACPIEC which is
happening more and more frequently and again I am at a loss.

Any help on these would be much appreciated, so that I try to understand
what is going on in my very slow computer. All the MS updates are up to
date. I have XP Home SP3.

Below the errors that I keep getting:


Product: Windows Operating System
ID: 7023
Source: Service Control Manager
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_SERVICE_EXIT_FAILED
Message: The %1 service terminated with the following error:
%2

Explanation
The specified service stopped unexpectedly with the error indicated in the
message. The service closed

safely.


--------------------------------------------------------------------------------------------------------------------------------------------------------------

Product: Windows Operating System
ID: 10010
Source: DCOM
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_RPCSS_SERVER_START_TIMEOUT
Message: The server %1 did not register with DCOM within the required
timeout.

Explanation
The Component Object Model (COM) infrastructure tried to start the named
server; however, the server

did not reply within the required timeout period. There might be a
deadlock, or the program might not

have responded to the server initialization code within the timeout period
of two minutes

-----------------------------------------------------------------------------------------------------------------------------------------------------------

Product: Windows Operating System
ID: 1
Source: ACPIEC
Version: 5.2
Symbolic Name: ACPIEC_ERR_WATCHDOG
Message: %1: The embedded controller (EC) hardware didn't respond within
the timeout period. This

may indicate an error in the EC hardware or firmware, or possibly a poorly
designed BIOS which

accesses the EC in an unsafe manner. The EC driver will retry the failed
transaction if possible.

Is the system event log showing the exact same error as in the KB article
? Update.exe should have been updated to a much higher version [the
latest is V. 6.3.13.0] than what is showing in the article by the
installation of SP2 and SP3, along with the myriad security updates
issued since this KB was published.

MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============

I get error 7023 repeatedly whenever I delete a programme.

I can't understand how to get the Hotfix below, and whether it is
applicable to XP SP3.

http://support.microsoft.com/kb/328213/en-us

help!

JB

 

[Peter]

Thank you very much for your help.

As for Registry cleaner the answer is yes. Over the years (4/5) I have used
in the past RegCleaner and more recently CCleaner.

I nver played around with Services, other than in MSconfig, where I disabled
most of what I felt was not necessary at Startup.

The boot is very long! I get the clock after some 15 seconds followed by
the battery and the sound icons, but then I have to wait some 90/120 seconds
for the Internet and McAfee to come up, strangely usually Internet before
McAfee. I have cable connected to a router and then to the computer through
a cable. The delay, I guess in my ignorance may be due to handshaking
between the computer and the router with McAfee making things worse. Even
after all the icons are up I find it difficult to open anything at all for
some time. Eventually everything works reasonable well, until McAfee or
someone else decides to check updates and then the susytem goes into a
crawl, as if the memory was being hijacked. Checking on CPU use does not
show excessive use which makes it strange why the computer should virtually
hang if the CPU has over 90% free usage.

Incidentally, I have done repeatedly all sorts of Virus/trojan/etc checks
and I am confident that the computer is clean; unmless of course all the
different programmes are useless...

Thank you again for your help.

JB

I will wait for your response before clearing the App and System Event Logs.

Has this computer ever had a Registry Cleaner used on it ? Also has
any Services had their Start Mode modified. It seems to me like you've
got a series of dependency group failures. I would clear both the App
and System Event Logs and do a reboot. Then check both logs for all
warnings and errors. Does your boot cycle time run ~45-60 Seconds
or is it significantly longer.

As to the hardware issue does your Device Manager have a clean
listing ? - ( No Red X's or Yellow Exclamation marks ).

As far as Error 7023, it only happens when I Add/Delete a program (I
think only deleting). I have other Errors: 10010 DCOM which happens
EVERY TIME I start the computer and I don't know what to do; and ID1
ACPIEC which is happening more and more frequently and again I am at a
loss.

Any help on these would be much appreciated, so that I try to understand
what is going on in my very slow computer. All the MS updates are up to
date. I have XP Home SP3.

Below the errors that I keep getting:


Product: Windows Operating System
ID: 7023
Source: Service Control Manager
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_SERVICE_EXIT_FAILED
Message: The %1 service terminated with the following error:
%2

Explanation
The specified service stopped unexpectedly with the error indicated in
the message. The service closed

safely.


--------------------------------------------------------------------------------------------------------------------------------------------------------------

Product: Windows Operating System
ID: 10010
Source: DCOM
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_RPCSS_SERVER_START_TIMEOUT
Message: The server %1 did not register with DCOM within the required
timeout.

Explanation
The Component Object Model (COM) infrastructure tried to start the named
server; however, the server

did not reply within the required timeout period. There might be a
deadlock, or the program might not

have responded to the server initialization code within the timeout
period of two minutes

-----------------------------------------------------------------------------------------------------------------------------------------------------------

Product: Windows Operating System
ID: 1
Source: ACPIEC
Version: 5.2
Symbolic Name: ACPIEC_ERR_WATCHDOG
Message: %1: The embedded controller (EC) hardware didn't respond within
the timeout period. This

may indicate an error in the EC hardware or firmware, or possibly a
poorly designed BIOS which

accesses the EC in an unsafe manner. The EC driver will retry the failed
transaction if possible.

Is the system event log showing the exact same error as in the KB
article ? Update.exe should have been updated to a much higher version
[the latest is V. 6.3.13.0] than what is showing in the article by the
installation of SP2 and SP3, along with the myriad security updates
issued since this KB was published.

MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============


Peter wrote:

I get error 7023 repeatedly whenever I delete a programme.

I can't understand how to get the Hotfix below, and whether it is
applicable to XP SP3.

http://support.microsoft.com/kb/328213/en-us

help!

JB

 

[R. McCarty]

Using McAfee almost always inflicts a "Noticeable" performance loss.
So some of your issues are most definitely related to McAfee. The boot
sequence indicates service time outs ( up to 30 Seconds ).

The kind of errors you report can be the result of Registry Cleaning. It's
like death of a thousand cuts for a PC. The registry is a large database
of "HIGHLY" interdependent links and associations. Removing what
seems to be invalid keys/values may not result in immediate damage, but
will show up later as that association is called on.

Registry Cleaning ( & it's merits ) ranks as the top on-going issue here.
This post is likely to kick off the "Yes it works", "No it Doesn't" threads.

Unfortunately once the Registry is hacked on, there is no method of
repair to a known valid state. You can probably get the machine back to
a working state, but you'll never know or trust the integrity of the
Registry.
The time it will take to get a Clean/Error free boot may not be worth the
effort. I'd be inclined to recommend a fresh install and choose another
Security product excluding any McAfee or Norton brand.

If you can't resist the urge to clean the Registry at the least invest in an
imaging program like Acronis True Image and make regular images. This
way when something gets broken you can roll the machine back to a
working/reliable state.

Thank you very much for your help.

As for Registry cleaner the answer is yes. Over the years (4/5) I have
used in the past RegCleaner and more recently CCleaner.

I nver played around with Services, other than in MSconfig, where I
disabled most of what I felt was not necessary at Startup.

The boot is very long! I get the clock after some 15 seconds followed by
the battery and the sound icons, but then I have to wait some 90/120
seconds for the Internet and McAfee to come up, strangely usually Internet
before McAfee. I have cable connected to a router and then to the
computer through a cable. The delay, I guess in my ignorance may be due
to handshaking between the computer and the router with McAfee making
things worse. Even after all the icons are up I find it difficult to open
anything at all for some time. Eventually everything works reasonable
well, until McAfee or someone else decides to check updates and then the
susytem goes into a crawl, as if the memory was being hijacked. Checking
on CPU use does not show excessive use which makes it strange why the
computer should virtually hang if the CPU has over 90% free usage.

Incidentally, I have done repeatedly all sorts of Virus/trojan/etc checks
and I am confident that the computer is clean; unmless of course all the
different programmes are useless...

Thank you again for your help.

JB

I will wait for your response before clearing the App and System Event
Logs.

Has this computer ever had a Registry Cleaner used on it ? Also has
any Services had their Start Mode modified. It seems to me like you've
got a series of dependency group failures. I would clear both the App
and System Event Logs and do a reboot. Then check both logs for all
warnings and errors. Does your boot cycle time run ~45-60 Seconds
or is it significantly longer.

As to the hardware issue does your Device Manager have a clean
listing ? - ( No Red X's or Yellow Exclamation marks ).

As far as Error 7023, it only happens when I Add/Delete a program (I
think only deleting). I have other Errors: 10010 DCOM which happens
EVERY TIME I start the computer and I don't know what to do; and ID1
ACPIEC which is happening more and more frequently and again I am at a
loss.

Any help on these would be much appreciated, so that I try to understand
what is going on in my very slow computer. All the MS updates are up to
date. I have XP Home SP3.

Below the errors that I keep getting:


Product: Windows Operating System
ID: 7023
Source: Service Control Manager
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_SERVICE_EXIT_FAILED
Message: The %1 service terminated with the following error:
%2

Explanation
The specified service stopped unexpectedly with the error indicated in
the message. The service closed

safely.


--------------------------------------------------------------------------------------------------------------------------------------------------------------

Product: Windows Operating System
ID: 10010
Source: DCOM
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_RPCSS_SERVER_START_TIMEOUT
Message: The server %1 did not register with DCOM within the required
timeout.

Explanation
The Component Object Model (COM) infrastructure tried to start the named
server; however, the server

did not reply within the required timeout period. There might be a
deadlock, or the program might not

have responded to the server initialization code within the timeout
period of two minutes

-----------------------------------------------------------------------------------------------------------------------------------------------------------

Product: Windows Operating System
ID: 1
Source: ACPIEC
Version: 5.2
Symbolic Name: ACPIEC_ERR_WATCHDOG
Message: %1: The embedded controller (EC) hardware didn't respond within
the timeout period. This

may indicate an error in the EC hardware or firmware, or possibly a
poorly designed BIOS which

accesses the EC in an unsafe manner. The EC driver will retry the failed
transaction if possible.










"MowGreen [MVP]" <[email protected]> escreveu na mensagem
Is the system event log showing the exact same error as in the KB
article ? Update.exe should have been updated to a much higher version
[the latest is V. 6.3.13.0] than what is showing in the article by the
installation of SP2 and SP3, along with the myriad security updates
issued since this KB was published.

MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============


Peter wrote:

I get error 7023 repeatedly whenever I delete a programme.

I can't understand how to get the Hotfix below, and whether it is
applicable to XP SP3.

http://support.microsoft.com/kb/328213/en-us

help!

JB

 

[Peter]

Thank you so much.

Could you give me an idea of what the ID: 1: ACPIEC is all about?

Best

JB

Using McAfee almost always inflicts a "Noticeable" performance loss.
So some of your issues are most definitely related to McAfee. The boot
sequence indicates service time outs ( up to 30 Seconds ).

The kind of errors you report can be the result of Registry Cleaning. It's
like death of a thousand cuts for a PC. The registry is a large database
of "HIGHLY" interdependent links and associations. Removing what
seems to be invalid keys/values may not result in immediate damage, but
will show up later as that association is called on.

Registry Cleaning ( & it's merits ) ranks as the top on-going issue here.
This post is likely to kick off the "Yes it works", "No it Doesn't"
threads.

Unfortunately once the Registry is hacked on, there is no method of
repair to a known valid state. You can probably get the machine back to
a working state, but you'll never know or trust the integrity of the
Registry.
The time it will take to get a Clean/Error free boot may not be worth the
effort. I'd be inclined to recommend a fresh install and choose another
Security product excluding any McAfee or Norton brand.

If you can't resist the urge to clean the Registry at the least invest in
an
imaging program like Acronis True Image and make regular images. This
way when something gets broken you can roll the machine back to a
working/reliable state.

Thank you very much for your help.

As for Registry cleaner the answer is yes. Over the years (4/5) I have
used in the past RegCleaner and more recently CCleaner.

I nver played around with Services, other than in MSconfig, where I
disabled most of what I felt was not necessary at Startup.

The boot is very long! I get the clock after some 15 seconds followed by
the battery and the sound icons, but then I have to wait some 90/120
seconds for the Internet and McAfee to come up, strangely usually
Internet before McAfee. I have cable connected to a router and then to
the computer through a cable. The delay, I guess in my ignorance may be
due to handshaking between the computer and the router with McAfee making
things worse. Even after all the icons are up I find it difficult to
open anything at all for some time. Eventually everything works
reasonable well, until McAfee or someone else decides to check updates
and then the susytem goes into a crawl, as if the memory was being
hijacked. Checking on CPU use does not show excessive use which makes it
strange why the computer should virtually hang if the CPU has over 90%
free usage.

Incidentally, I have done repeatedly all sorts of Virus/trojan/etc checks
and I am confident that the computer is clean; unmless of course all the
different programmes are useless...

Thank you again for your help.

JB

I will wait for your response before clearing the App and System Event
Logs.

Has this computer ever had a Registry Cleaner used on it ? Also has
any Services had their Start Mode modified. It seems to me like you've
got a series of dependency group failures. I would clear both the App
and System Event Logs and do a reboot. Then check both logs for all
warnings and errors. Does your boot cycle time run ~45-60 Seconds
or is it significantly longer.

As to the hardware issue does your Device Manager have a clean
listing ? - ( No Red X's or Yellow Exclamation marks ).


As far as Error 7023, it only happens when I Add/Delete a program (I
think only deleting). I have other Errors: 10010 DCOM which happens
EVERY TIME I start the computer and I don't know what to do; and ID1
ACPIEC which is happening more and more frequently and again I am at a
loss.

Any help on these would be much appreciated, so that I try to
understand what is going on in my very slow computer. All the MS
updates are up to date. I have XP Home SP3.

Below the errors that I keep getting:


Product: Windows Operating System
ID: 7023
Source: Service Control Manager
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_SERVICE_EXIT_FAILED
Message: The %1 service terminated with the following error:
%2

Explanation
The specified service stopped unexpectedly with the error indicated in
the message. The service closed

safely.


--------------------------------------------------------------------------------------------------------------------------------------------------------------

Product: Windows Operating System
ID: 10010
Source: DCOM
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_RPCSS_SERVER_START_TIMEOUT
Message: The server %1 did not register with DCOM within the required
timeout.

Explanation
The Component Object Model (COM) infrastructure tried to start the
named server; however, the server

did not reply within the required timeout period. There might be a
deadlock, or the program might not

have responded to the server initialization code within the timeout
period of two minutes

-----------------------------------------------------------------------------------------------------------------------------------------------------------

Product: Windows Operating System
ID: 1
Source: ACPIEC
Version: 5.2
Symbolic Name: ACPIEC_ERR_WATCHDOG
Message: %1: The embedded controller (EC) hardware didn't respond
within the timeout period. This

may indicate an error in the EC hardware or firmware, or possibly a
poorly designed BIOS which

accesses the EC in an unsafe manner. The EC driver will retry the
failed transaction if possible.










"MowGreen [MVP]" <[email protected]> escreveu na mensagem
Is the system event log showing the exact same error as in the KB
article ? Update.exe should have been updated to a much higher version
[the latest is V. 6.3.13.0] than what is showing in the article by the
installation of SP2 and SP3, along with the myriad security updates
issued since this KB was published.

MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============


Peter wrote:

I get error 7023 repeatedly whenever I delete a programme.

I can't understand how to get the Hotfix below, and whether it is
applicable to XP SP3.

http://support.microsoft.com/kb/328213/en-us

help!

JB