Exchange 2003 LDAP problem
Hello, I have the following problem on my exchange server: System Attendant service doesn't start (neither all dependent services) When checking the event viewer I get: Unexpected error Logon failure: unknown user name or bad password. Facility: LDAP Provider ID no: 8007052e Microsoft Exchange System Attendant occurred. And - Microsoft Exchange System Attendant failed to start. Does anyone have any "lights" on the subject ? Thank you in advance, BR
October 17th, 2008 7:49pm

Hi, It can be various problems: - check that DNS is configured correctly - run dcdiag/netdiag and check if no errors are found - check http://support.microsoft.com/kb/940845 Regards, Johan blog: www.johanveldhuis.nl
Free Windows Admin Tool Kit Click here and download it now
October 17th, 2008 9:37pm

Hi Johan, Thank you for your reply. Regarding your answer, most of the scenerios were ruled out: Network is 100%; This is just a server on the domain DC is up and running and can ping between both servers etc. I ran DCdiag, since it's point out to be something regarding permissions, and it passed all tests. Regarding the support link, I already had checked that support (and many others) and dound out that non of the suggestions applies. The only one that I didn't tried was themethod 2, since it will only create new dependencies and probably will not solve my problem. I still want to point out the error itself - LDAP and Bad Username and Password - does anyone knows what this means ? the service runs as local account. BR
October 17th, 2008 10:35pm

Hello BR, Are you running Exchange services under any user account? If so then check the user account settings. It is recommended to run it under LocalSystem. http://support.microsoft.com/kb/239762
Free Windows Admin Tool Kit Click here and download it now
October 18th, 2008 7:46pm

Hi Amit, The problem goes far then the service log on. After I read your post, and yes the Local System account was set on the log on, I decided to do the reverse: I tryied to log on with a user (administrator for the domain) - the stragest thing happened "Access Denied". Clear the problem is the the service loging on to the DC. Does any one have any idea (I will try to create a new post on the right forum regarding services log on issues)? BR
October 19th, 2008 1:57am

Hi, Please run gpedit.msc, expand Computer Configuration, Windows Settings, Security Settings, Local Policies, User Rights Assignment: In the right panel, please double click "Access this computer from the network", please post the users that was listed in that interface on the forum. Thanks Allen
Free Windows Admin Tool Kit Click here and download it now
October 21st, 2008 9:36am

Hi Allen, Sorry for the late reply. All domain admins, Domain Administrator, Entreprise administrator figure on the GPO for the local machine. Again, the problem goes a litlle bit far than Exchange: All services on the server where Exchange resides have problems connecting to the domain controller; For this reason the exchange system Attendant can not start since it can not contact AD; If I choose a service, any service and place the log on with the Domain Administrator account I get "Access Denied"; If I do the same opertion on another server on teh Domain I have no problems and the service starts running. Does anyone have any ideia why does this happen - it also happen after I reinstall 100 % the server, so I'm guesssing problems or configs and the DC level..... BR
October 29th, 2008 5:05am

Hi, Please continue expanding the GPO based on the above steps, then add the following user into Access this computer from the network. Authenticated Users, Everyone, Then check this issue. Thanks Allen
Free Windows Admin Tool Kit Click here and download it now
October 29th, 2008 12:32pm

Hi Allen, First of all your first and last post are completly right. When we depoyed the DC we actually implemented some security policies recommended by Microsoft changing the default (and mention by you) values on the Domain Controller GPO. So the changes you suggested worked 100%. I just have one problem left, althought information store service is running on exchange and changes to the domain controller you suggested were implemented, I can not mount the mail box store. Any idea ? BR
October 31st, 2008 3:47am

Hi, Whether any event log were generated? Please let me know. Thanks Allen
Free Windows Admin Tool Kit Click here and download it now
November 3rd, 2008 8:39am

The MAPI call 'OpenMsgStore' failed with the following error: The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance. The MAPI provider failed. Microsoft Exchange Server Information Store ID no: 8004011d-0526-00000000
November 6th, 2008 12:51pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics