Hi everyone, we had a power skike and server restart and since thenthe System Attendant wil not start so Exchange is dead.The following errors occur on every restart attempt:Event Type:ErrorEvent Source:MSExchangeSAEvent Category:General Event ID:9152Date:4/13/2009Time:12:38:57 PMUser:N/AComputer:AGUIRREDescription:Microsoft Exchange System Attendant reported an error '0xc1034a70' in its DS Monitoring thread. Event Type:ErrorEvent Source:MSExchangeSAEvent Category:General Event ID:1005Date:4/13/2009Time:12:38:52 PMUser:N/AComputer:AGUIRREDescription:Unexpected error The remote procedure call failed. Facility: Win32 ID no: c00706be Microsoft Exchange System Attendant occurred. This error occurs on mutliple services:Event Type:ErrorEvent Source:MSExchangeSAEvent Category:General Event ID:9317Date:4/13/2009Time:12:38:52 PMUser:N/AComputer:AGUIRREDescription:Failed to register Service Principal Name for exchangeMDB; error code was c00706be.I have alreeady checked/set full permissions to the Exchange server for the System account.I have checked the Exchange DB andit came out clean.Any other ideas and pointer would really help.TIAMartin KultermanneStar CommunicationsOffice: +1 (312) 275-0291Email: Martinator2000@yahoo.com

Forgot to mention:We are running Exchange 2003 SP2

I would start with some networking tests. Make sure the server can ping the other Exchange Servers and the Domain Controllers. Make sure you can ping the server from a remote Server.Then I would check for any authentication issues with the server or user account. Check to make sure the SPNs are correct in AD, also make sure the machine account password is still good.Is this the only Exchange Server in your org?Otherwise Call Microsoft and see what they can do but it almost sounds like a permissions issue.BP

Hi BP, thanks for you reply. Sorry, I should have provided more detail before. We have one Exchange Server that runs on the PDC on Win2K3 SP2. Exchange has been running fine for months, this started after a power spike/restart last night. I have always had strange problems but until now they didn't prevent things from working OK. DCDIAG returns Directory Binding Error 1726 during initial setup and DsBindWithSpnEx() failed with error 1722, The RPC server is unavailable. Not sure how to check for authentication issues with the server or user account but other services using those accounts seem to start OK. You are corect about the SPN issue. I am also getting an SPN error Event Type:ErrorEvent Source:MSExchangeSAEvent Category:General Event ID:9317Date:4/13/2009Time:12:38:52 PMUser:N/AComputer:AGUIRREDescription:Failed to register Service Principal Name for exchangeMDB; error code was c00706be.events.asp. The System Attendant uses the Local System Account. How do I check that in AD? Not sure how to check that SPN's are correct in AD?How do I check the machine account password?

To check the SPN: Run command: -- ldifde f check_SPN.txt t 3268 d l ServicePrincipalName r (servicePrincipalName=Host*) p subtreeThat should list all the SPNs. And: setspn L mailboxserver Should list the spn for the mailbox server.what about firewall, you could do a test-servicehealth from a EMS to see if there are any services not starting required by exchange.BP

Issue description: MSExchangeSA service cant be started Troubleshooting: 1. Please verify if the problematic server object is the member of the Exchange Domain Servers group 2. Please check the permission on the problematic server via ADSI Editor a. Launch ADSI Editor b. Expand to Configuration Container->CN=Configuration, DC= Domain_Name ,DC=com->CN=Services ->CN=Microsoft Exchange->CN= Your_Organization_Name->CN=Administrative Groups ->CN= Your_Administrative_Group_Name->CN=Servers->CN=Server_Name c. Right-click CN=Server_Name and select Properties d. Go to Security tab, find ServerName$ object and make sure that it has been allowed for all permissions, including Full Control Notes: If CN=Server_Name is CN=Server1, ServerName$ should be Server1$ 3. Please check if "Allow inheritable permissions from parent to propagate to this object" had been unchecked on the Computers container, if yes, please re-check it and replicate DCs 4. Please run ExBPA on the problematic server for a health and permission check Resources: Event ID 9152 Source MSExchangeSA Event ID 9317 Source MSExchangeSA MSExchangeSA Does Not Start and Events 9001 and 1005 Are Logged Failed to register Service Principal Name for exchangeRFR; error code c10379bc

Hi DB and thanks again.The ldifde command returned a listing with my PDC with Exchange, my other DC and allcomputers on the network. Here's the PDC:dn: CN=AGUIRRE,OU=Domain Controllers,DC=amazonia,DC=comchangetype: addservicePrincipalName: MSSQLSvc/aguirre.amazonia.com:1433servicePrincipalName: MSSQLSvc/aguirre.amazonia.comservicePrincipalName: exchangeAB/AGUIRREservicePrincipalName: exchangeAB/aguirre.amazonia.comservicePrincipalName: exchangeMDB/aguirre.amazonia.comservicePrincipalName: exchangeMDB/AGUIRREservicePrincipalName: exchangeRFR/aguirre.amazonia.comservicePrincipalName: exchangeRFR/AGUIRREservicePrincipalName: SMTPSVC/AGUIRREservicePrincipalName: SMTPSVC/aguirre.amazonia.comservicePrincipalName: NtFrs-88f5d2bd-b646-11d2-a6d3-00c04fc9b232/aguirre.amazonia.comservicePrincipalName: ldap/aguirre.amazonia.com/ForestDnsZones.amazonia.comservicePrincipalName: GC/aguirre.amazonia.com/amazonia.comservicePrincipalName: HOST/aguirre.amazonia.com/AMAZONIAservicePrincipalName: HOST/AGUIRREservicePrincipalName: HOST/aguirre.amazonia.comservicePrincipalName: HOST/aguirre.amazonia.com/amazonia.comservicePrincipalName: E3514235-4B06-11D1-AB04-00C04FC2DCD2/32c124bf-1d79-42d1-959b-62b4a437cc09/amazonia.comservicePrincipalName: ldap/32c124bf-1d79-42d1-959b-62b4a437cc09._msdcs.amazonia.comservicePrincipalName: ldap/aguirre.amazonia.com/AMAZONIAservicePrincipalName: ldap/AGUIRREservicePrincipalName: ldap/aguirre.amazonia.comservicePrincipalName: ldap/aguirre.amazonia.com/DomainDnsZones.amazonia.comservicePrincipalName: ldap/aguirre.amazonia.com/amazonia.comservicePrincipalName: DNS/aguirre.amazonia.comThe setspn command failed as follows:C:\>setspn -L AGUIRREFailed to bind to DC of domain AMAZONIA, error 0x6be/1726 -> The remote procedure call failed. C:\>setspn -L AGUIRRE.AMAZONIA.comFindDomainForAccount: DsGetDcNameWithAccountW failed!Cannot find account AGUIRRE.AMAZONIA.com C:\>setspn -L LocalhostFindDomainForAccount: DsGetDcNameWithAccountW failed!Cannot find account Localhost C:\>setspn -L 192.168.254.11FindDomainForAccount: DsGetDcNameWithAccountW failed!Cannot find account 192.168.254.11 C:\>setspn -L exchangeAB/AGUIRREFindDomainForAccount: DsGetDcNameWithAccountW failed!Cannot find account exchangeAB/AGUIRRE C:\>setspn -L exchangeAB/aguirre.amazonia.comFindDomainForAccount: DsGetDcNameWithAccountW failed!Cannot find account exchangeAB/aguirre.amazonia.com We are running ISA 2004 as our firewall. Not sure what EMS is. All of the services requires for the Exchange SA are up and running.

Hi James and thank you for your reply. Yes, the server is part of the Exchange Domain Servers group. The ADSIEditor reports that the "Allow inheritable permissions from parent to propagate to this object" flag is checked for the Server Object and it has Full Control. The ExBPA Health Check returned a couple of system issues (3GB swith and so on) but nothing unusual. The Permissions Check returned a pretty large XML file but no errors as far as I can see. Let me know what you need from that. Resources: Event ID 9152 - This is Exchange 2003 and there is no password entry under Admin Group - Properties - General Event ID 9152 - It seems that something is wrong with the SPNs -setspn -l exchangeMDB/AGUIRRE and -setspn -l exchangeMDB/aguirre.amazonia.com both returned account not found for FindDomainForAccount. Events ID 9001 and 1005 - Exchange SA was able to load ABV_DG.dll according to the Event Log. Failed to Register SPN - I reinstalled Exchange SP2 yesterday to no effect.

Hmm.... Has the computer name been used before? Did the machine account tomb stone in AD?BP

The server name is old and has never been used before.This problem started after a power surge and restart on Sunday.Exchange had been working fine for months until that point.The last admin change on that server wasin ISA to openupanother SMTP port, 587, for some Comcast users. That was over a week ago.Any other ideas???

Hard Drive Space? ESEUtil to check database health? I would reach out to MS. Sounds like your Exchange server is down and it can't get back in.Another thought would be to build a new exchnage server, restore teh database etc....BP

Hi everyone, I just realized that there is another problem that must be related to this.For the last week or twoI had been randomly getting the following error in my Outlook 2007 client:You are repeatedly prompted to enter your credentials when you try to connect to an Exchange mailbox by using Outlook 2007described in MS Article ID 927612which recommends unregistering and re-registering the exchangeAB SPN.Unfortunately, I can't do that becuase setspn fails as follows:C:\Documents and Settings\Administrator>setspn -L aguirreFailed to bind to DC of domain AMAZONIA, error 0x6be/1726 -> The remote procedure call failed.Any ideas?

Can you ping your DC?Can you telnet to your DC on port 389? What about DNS?Sounds like a communication problem with your DC. how many DCs? Could be replication issue etc.BP

Hi BP, got it resolved.I unplugged my external nic and shut down ISA server and voila everything works.I brought back ISA and everything is still working although I am still getting RPC Call failed errors on certain functions.I am trying to figure out what I'm missing in ISA Server.Thank yoiu for your help.Cheers