MSExchangeSA will not start

Running Microsoft Exchange 2007.  Rebooted server and broke Exchange.  Please help me.  Think I have it narrowed down to MSExchangeSA:

Log Name:      Application
Source:        MSExchangeSA
Date:          4/28/2009 7:12:27 PM
Event ID:      1005
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Unexpected error Logon failure: unknown user name or bad password. Facility: Win32 ID no: 8007052e Microsoft Exchange System Attendant  occurred.
Event Xml:
<Event xmlns="">
    <Provider Name="MSExchangeSA" />
    <EventID Qualifiers="49152">1005</EventID>
    <TimeCreated SystemTime="2009-04-29T00:12:27.000Z" />
    <Security />
    <Data>Logon failure: unknown user name or bad password. Facility: Win32 ID no: 8007052e Microsoft Exchange System Attendant </Data>
Who is Participating?
SirHWConnect With a Mentor Author Commented:
Turns out it was a problem with a St. Bernard 30H iPrism web filter.  We were demoing a new firmaware that joins to the 2008 AD and it entered a registry key that caused the problem.  I deleted the key and the problem was resolved.
First and foremost, ensure that the credentials entered for the System Attendant service (if running as a user account) are entered correctly.  Try starting the service manually after confirming the credentials.

If that's not it, check your DNS, secure channel to a DC, and that the computer account is valid.  You can run netdiag for assistance with this.

Is your exchange server also a DC?
SirHWAuthor Commented:
The service is running as a local service.  I tried to run it as user, no dice.

I will try the suggestions in the second paragraph in the AM,

Yes, my Exchange server is also a DC, against best practices.  Suggestions?
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Steven WellsSystems AdministratorCommented:
This can be caused if Exchange services start before Domain Services.
Are all your domain services running, such as netlogon?
Also check that the exchange server is a member of the exchange servers group in Active Directory.
This group should be in the Microsoft Exchange Security Groups OU
This is where the system attendent checks it can start.

Have you also tried the troubleshooting tool with exchange (exchange bpa)

could you elaborate more, like waht happened at your server end ?

there might be few more event id's in the application log lie  2114 ,1005 ....., etc.

let me know all the error messages. also try testing replication between the DC/GC. what is the RU applied on your server. did you made any recent updates ?
SirHWAuthor Commented:
I applied 5 windows security updates, rebooted, problem manifested itself, uninstalled updates, rebooted, same problem.

Replication is a no go from Excahnge GC to the DC.
Steven WellsSystems AdministratorCommented:
Can you list any othe event log errors ? Are any exchange services trying to start?

Is there any other warns such as disk space etc?
 could you please upload some of the error messages from the application log ?

you could try running "setup /prepareAD" command by using the exchange 2007 disk.

i think this should resolve your issue.

Are you still facing the same issue ?

Please let me know if you need any help.



Do let me know if you need any help.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.