Event id 7031 service control manager windows 2000

Track users' IT needs, easily, and with only the features you need. Learn More ». Get answers from your peers along with millions of IT pros who visit Spiceworks. Has anyone seen this on SBS ? Best Answer. Laban M. This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. Now, I keep getting metabase update failure on all the exchange server. I called microsoft support back on this issue and they are stumped on it. Anyone else experience this problem?

Unexpected error An unknown error has occurred. ID no: a Microsoft Exchange System Attendant occurred. You need to be a member in order to leave a comment. Sign up for a new account in our community. It's easy! Already have an account? Sign in here. MSFN is made available via donations, subscriptions and advertising revenue.

The use of ad-blocking software hurts the site. Can this be resolved. Wednesday, March 2, AM. All instructions are in our Wiki article below Should you have any questions please ask us. I didn't fix anything. The problem remains. Thursday, March 3, AM. Friday, March 4, AM. Friday, March 4, PM. Did you run DISM, and what did it say? Nothing has changed. DISM - system health is clean or not corrupted. There was no requirement to run health restore.

Here is the output of one of the services:. Of course it can't because you are shutting down. The question remains why does it give the error message and why does it want to restart when the system is shutting down? Seeing that the error happens at shutdown makes it less of a concern than if the error happened at startup IMO. Also, you can't rule out the Shutdown procedure.

Other than the VMware service, the others don't appear when you run service. You can see them in task manager under the services tab and of course in the Registry. As the event viewer entry states to "restart the service" as its not listed in Services to be able to do this. Keep in mind that these are 'hidden services' You can see them in task manger under the services tab.

Again let me repeat. These messages are generated when you shutdown or restart Windows. Of course everything ends during this time.

Their properties show that they are supposed to restart if stopped unexpectedly, but not at shutdown IMO.

This makes no sense to me. I really don't think this is causing any problems whatsoever because you are shutting them down when Windows is shutting down. If it happened at startup then that may be a problem. Either the services are setup incorrectly or the shutdown function is not acting correctly for these services.

Shutdown should end them without them trying to restart.