[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

MSExchangeSA will not start

Posted on 2009-04-28
10
Medium Priority
?
2,572 Views
Last Modified: 2012-05-06
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
Computer:      Server-Main.xxx.xxx
Description:
Unexpected error Logon failure: unknown user name or bad password. Facility: Win32 ID no: 8007052e Microsoft Exchange System Attendant  occurred.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchangeSA" />
    <EventID Qualifiers="49152">1005</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-04-29T00:12:27.000Z" />
    <EventRecordID>207057</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Server-Main.xxx.xxx</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Logon failure: unknown user name or bad password. Facility: Win32 ID no: 8007052e Microsoft Exchange System Attendant </Data>
  </EventData>
</Event>
0
Comment
Question by:SirHW
  • 4
  • 3
  • 2
  • +1
10 Comments
 
LVL 5

Expert Comment

by:megs28
ID: 24256671
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?
0
 

Author Comment

by:SirHW
ID: 24256720
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?
0
 
LVL 12

Expert Comment

by:Steven Wells
ID: 24257180
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)

Steven
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 5

Expert Comment

by:jawad1481
ID: 24257642
hi!
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 ?
0
 

Author Comment

by:SirHW
ID: 24263628
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.
0
 
LVL 12

Expert Comment

by:Steven Wells
ID: 24264700
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?
0
 
LVL 5

Expert Comment

by:jawad1481
ID: 24266893
hi!
 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.
0
 
LVL 5

Expert Comment

by:jawad1481
ID: 24286486
HI!

Are you still facing the same issue ?

Please let me know if you need any help.

Thanks.

Jawad.
0
 
LVL 5

Expert Comment

by:jawad1481
ID: 24292930
HI!

Do let me know if you need any help.

Jawad.
0
 

Accepted Solution

by:
SirHW earned 0 total points
ID: 24794956
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.
0

Featured Post

Upgrade your Question Security!

Add Premium security features to your question to ensure its privacy or anonymity. Learn more about your ability to control Question Security today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

As much as Microsoft wants to kill off PST file support, just as they tried to do with public folders, there are still times when it is useful or downright necessary to export Exchange mailboxes to PST files. Thankfully, it is still possible to e…
There can be many situations demanding the conversion of Outlook OST files to PST format and as such, there is no shortage of automated tools to perform this conversion. However, what makes Stellar OST to PST converter stand above the rest? Let us e…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
Suggested Courses

831 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question