k-meson
asked on
Getting MSExchangeSA Event ID 1005 Login failure error and services will not start.
I have a problem which I think stems from some AD corruption that I have had on SBS 2003.
I have got the server booting up after running ntdsutil offline compression etc. but now Exchange services will not start and I am getting the following error messages:
MSExchangeSA Event: 1005 Category: General
Unexpected error Logon failure: unknown user name or bad password. Facility: Win32 ID no: 8007052e Microsoft Exchange System Attendant occurred.
MSExchangeDSAccess Event: 2114 Category: Topology
Process INETINFO.EXE (PID=5104). Topology Discovery failed, error 0x80040931.
I have already re-run forestprep and domainprep for exchange in case there were missing components in the AD after a cleanup but this has not helped. Also re-applied Exchange SP2.
This is SBS Single server environment so do not have facility to rebuild AD from another server.
I think the problem is mainly to do with the local service account not being recognized by AD and am also getting
USERENV Event: 1053
Windows cannot determine the user or computer name. (Access is denied. ). Group Policy processing aborted.
Any suggestion greatly appreciated.
I have got the server booting up after running ntdsutil offline compression etc. but now Exchange services will not start and I am getting the following error messages:
MSExchangeSA Event: 1005 Category: General
Unexpected error Logon failure: unknown user name or bad password. Facility: Win32 ID no: 8007052e Microsoft Exchange System Attendant occurred.
MSExchangeDSAccess Event: 2114 Category: Topology
Process INETINFO.EXE (PID=5104). Topology Discovery failed, error 0x80040931.
I have already re-run forestprep and domainprep for exchange in case there were missing components in the AD after a cleanup but this has not helped. Also re-applied Exchange SP2.
This is SBS Single server environment so do not have facility to rebuild AD from another server.
I think the problem is mainly to do with the local service account not being recognized by AD and am also getting
USERENV Event: 1053
Windows cannot determine the user or computer name. (Access is denied. ). Group Policy processing aborted.
Any suggestion greatly appreciated.
Try typing the following in a DOS prompt:
nltest /sc_change_pwd:<netbiosdom
nltest /sc_change_pwd:<netbiosdom
ASKER
Exchange System Attendant is running as local service.
nltest does not run, not recognised as a command.
Have just spotted that I have a number of items listed as ForeignSecurityPrinciples such as NT AUTHORITY\SYSTEM in the AD Tree. Should these be in a proper container? If so how do I re-create?
nltest does not run, not recognised as a command.
Have just spotted that I have a number of items listed as ForeignSecurityPrinciples such as NT AUTHORITY\SYSTEM in the AD Tree. Should these be in a proper container? If so how do I re-create?
The ForeignSecurityPrinciples folder is empty by default.
I have never come across this before and googling does not bring up anything useful.
Having had a corrupted AD - do you have a System State backup you can use to restore AD from?
Have a read of the following EE Question:
https://www.experts-exchange.com/questions/22074580/Best-way-to-recover-a-corrupt-sbs-2003-server.html
I have never come across this before and googling does not bring up anything useful.
Having had a corrupted AD - do you have a System State backup you can use to restore AD from?
Have a read of the following EE Question:
https://www.experts-exchange.com/questions/22074580/Best-way-to-recover-a-corrupt-sbs-2003-server.html
ASKER
Unfortunateley I have no system state back-ups which is why I had to run a fix on the AD in the first place. I have a copy of the corrupt AD file before fixing which I may try to re-instate to see what happens.
It is all a bit frustrating!
It is all a bit frustrating!
ASKER
Server will now not boot up at all....
Looks like I may need to set up my new SBS 2008 and start again.
Any other ideas appreciated - will get back to this tomorrow.
Looks like I may need to set up my new SBS 2008 and start again.
Any other ideas appreciated - will get back to this tomorrow.
What changed?
I thought we were talking SBS 2003 not SBS 2008?
I thought we were talking SBS 2003 not SBS 2008?
ASKER
Yes currently running 2003.
Tried to swap ntds.dit with previous version before defrag etc. but now server reports security error and will not start. Changed files back and got same result.
I do have a copy of SBS2008 that I was due to implement when hardware became available but wanted to migrate. Fortunateley I have all data backed up so can start from fresh but need new tin to do it with.
Would really like to get this one running again if I can though as didn't really expect to need to purchase at this stage.
Tried to swap ntds.dit with previous version before defrag etc. but now server reports security error and will not start. Changed files back and got same result.
I do have a copy of SBS2008 that I was due to implement when hardware became available but wanted to migrate. Fortunateley I have all data backed up so can start from fresh but need new tin to do it with.
Would really like to get this one running again if I can though as didn't really expect to need to purchase at this stage.
You cannot just copy and paste the NTDS.DIT file and hope it works. You would have to reboot into Directory Service Restore Mode and restore that way.
Have a read of the following:
http://technet.microsoft.c
If you don't have a proper system state backup, you may well end up spending more time trying to finx than trying to rebuild.
Your best course of action may be to call Microsoft and pay them the small fee to troubleshoot the problem for you. They should be able to tell you fairly quickly if it can be achieved and save you some time, unless you have plenty to spare.
Have a read of the following:
http://technet.microsoft.c
If you don't have a proper system state backup, you may well end up spending more time trying to finx than trying to rebuild.
Your best course of action may be to call Microsoft and pay them the small fee to troubleshoot the problem for you. They should be able to tell you fairly quickly if it can be achieved and save you some time, unless you have plenty to spare.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Sorry we could not help, but glad you got it fixed in the end.
Sonds like a nasty problem.
Sonds like a nasty problem.
Look down the list of services for Exchange system Attendant. In the right-hand column, what is the Log On As name shown? Is it Local System or something else?