Hi Everyone, The System Attendant won't start. I've been receiving the following errors after installing a newExchange 2003 server on my domain. Unexpected error Logon failure: unknown user name or bad password. Facility: LDAP Provider ID no: 8007052e Microsoft Exchange System Attendant occurred. and Process INETINFO.EXE (PID=1916). Topology Discovery failed, error 0x80040952. Please help me. Thanks, Kiszer15

Hi Kiszer, this appear be a problem with DNS or Account, What is the account that is starting the service? Do you have others Log erros?Have (or anybody)Applied any security Update or any software at Network?IsEnable the Exchanges machine account ? DNS Resolution in your Domain, its fine? The Exchange server is a DC? If you have other erros or news post it.

Hi Friend, Please try this. Looked in DNS found no forward lookup zone and could not create a Active Directory integrated zone, but was able to create a Primary forward look up zone. Starting and Stopping the Netlogon and DHCP client service created the SRV records.When trying to make the forward lookup zone an Active Directory Integrated Zone we receive the following error message:Found the following event in the Directory Services log, suspect AD corruption found KB 258062, used NTDSUTIL to check integrity, integrity was OK, Ran ntdsutil files semantic database analysis go, this failed with an error, then ran ntdsutil files semantic database analysis go fixup, this completed successfully, defraged it according to KB 232122, still see the following event in Directory Services log after running this procedure:Event Type: ErrorEvent Source: NTDS GeneralEvent Category: Global Catalog Event ID: 1126Date: 9/23/2007Time: 5:24:29 PMUser: NT AUTHORITY\ANONYMOUS LOGONComputer: NTFS1Description:Active Directory was unable to establish a connection with the global catalog. Additional Data Error value:8430 The directory service encountered an internal failure. Internal ID:3200c45YOUR ACTION: Make sure a global catalog is available in the forest, and is reachable from this domain controller. You may use the nltest utility to diagnose this problem. running the following command resolved this issue:nltest /sc_change_pwd:<netbiosdomainname> # Domain with a Single DCThe following is from KB 3285611. To reset the password in a multiple DC environment use "netdom resetpwd /serverervername /userdomain\administrator /passworddassword" (Make sure that the netdom command returns the command completed successfully. Otherwise it didn't work.) Where servername is a DC other than the DC whose password is invalid. Then set the KDC to manual on the problem DC and reboot.2. To reset the password in a single DC environment use "nltest /sc_change_pwdomain" I hope that it will fix the issue. Best regards. Farhat Nishat.

Dear Farhat, In my situation your solution doesn't seem to work over here. I run a DC and a Exchange server 2003 everything is running on Server 2003 Enterprise Rel.2. Your solutionto use nltest /sc_change_pwdomain works fine, because the server tell's me it's done and okay!! But after that I can't start the Microsoft Exchange System Attendant. It give the same error Unexpected error Logon failure: unknown user name or bad password. Facility: LDAP Provider ID no: 8007052e Microsoft Exchange System Attendant occurred Does someone else have the same problem and knows the answer consurning this error? Kind regard Hugo van der Putten.

hi,read on http://support.microsoft.com/kb/940845i had a diffrent error for ExchangeSA not starting, but i've combined method 3, for pause the starting of the service.. and set the service to retry on failure 3 times.solved the issue nicely.yet again keep in mind that you shouldn't choose to run exchange on a DC/GC ..good luck !ilan.

Hi All, Installing Exchange server in a Domain controller is One of the major reason that cause the System Attendant not to start. Initially when a DC re-starts due to power failure/fluctuation it automatically starts the services related to DC immediately, similarly it also start the other application services which is installed on DC. So when DC and Excahnge services starts at same time it gives high priority to DC and exchange fails to start. Since we know that the Exchange server is purely dependent on DC. So if any Windows service cannot start, Exchange Server will not start. So add the following registry key to the affected server to delay the initial attempt to start the Microsoft Exchange System Attendant. Try this below: 1. Login to DC where Exchange server is installed 2. Click Start -Type Regedit.exe at Start search to Goto Registry Editor, Take Registry backup. Refer Do it on your own: Best way to take a Registry Backup mohammedathaur.blogspot.com/2011/07/registry-backup.html to take registry backup. 3. Navigate to the below path. HKEY_LOCAL_MACHINE\\System\CurrentControlSet\Services\MSExchangeSA\Parameters 4. Create registry subkey DWORD and name it as BootPause 5. Double click the Dword and set the Registry value (Decimal the value is in seconds) to 120. 6. Restart the Exchange server to make the changes to be take effect. Regards MohammedAthaur Rehman A