Microsoft Exchange System Attendant service fail to start. I find System event with event id 7000, source Service Control Manager, and description "The Microsoft Exchange System Attendant service failed to start due to the following error: Microsoft Exchange System Attendant is not a valid Win32 application." Exchange has sp1 without Rollups and OS is 2003 x64 R2 with SP2. How can I solve this problem?

Hi, Was there any changed on the server like antivirus change or update on any thing like that since it seen like there are some file missing, is there any other error event ID's present or not.Ripu Daman Mina | MCSE 2003 & MCSA Messaging

Hi, There were not any changes by antivirus and anything like things. Other error messages are absent in System log. Actually, it was some failure on the server before this situation, probably unplugged power cable. After this I restored queue mdb-file with eseutil, because it was damaged.

Increase diagnostics logging on system attendant , EMC \ server object \\\... and wait for few events., try to catch the event from where it stopped working, can you afford a restart etc. Finally you can also to a reinstall of exchange 2007 server. http://support.microsoft.com/kb/320202 though this can be just an indicator,.

this also may be a vague indicator http://support.microsoft.com/kb/325680

this also may be a vague indicator http://support.microsoft.com/kb/325680 thanks, but this way is not suitable for me because this files are absent in that directories.

Increase diagnostics logging on system attendant , EMC \ server object \\\ ... and wait for few events., try to catch the event from where it stopped working, can you afford a restart etc. Finally you can also to a reinstall of exchange 2007 server. http://support.microsoft.com/kb/320202 though this can be just an indicator,. it's good idea - increasing diagnostics logging in EMC. Can you tell me the exact location at EMC, where I can do it. I see increasing logging on Receive connectors only. May be I search it in the wrong location?

Thank you for help! I had solved this problem very simply. I had installed latest Rollup update for this Exchange service pack. And all Exchange services are working properly now.