Why does my 2003 DC hang on "Windows is shutting down" on reboot - Exchange errors in logs

meirionwyllt
meirionwyllt used Ask the Experts™
on
When I reboot my Windows Server 2003 domain controller, it never reboots properly, always hanging on the "Windows is shutting down" screen indefinitely.  I have to press and hold the power button for the PC to go off.

Looking at the logs there are always a spate of Exchange Server related errors and warnings after shutdown has been initiated.  Now, I don't know whether these are normal - due to the fact that the PC is shutting down and that some services are stopping ahead of others - or if these errors are actually causing the PC to not to close properly.

See below the first few errors and warning that are produced - there were many more but too many to list - they were all mainly concerned with the Directory Service and LDAP.

Any ideas if these are errors that could contribute to the DC not shutting down properly?
Event Type:	Warning
Event Source:	MSExchangeAL
Event Category:	LDAP Operations 
Event ID:	8033
Date:		15/06/2009
Time:		21:36:58
User:		N/A
Computer:	GWEINYDD
Description:
LDAP search result on directory gweinydd.gellioer.lleol for entry '' was unsuccessful with error:[0x52] Local Error.    
 
For more information, click http://www.microsoft.com/contentredirect.asp.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
 
 
 
Event Type:	Error
Event Source:	MSExchangeAL
Event Category:	LDAP Operations 
Event ID:	8026
Date:		15/06/2009
Time:		21:36:58
User:		N/A
Computer:	GWEINYDD
Description:
LDAP Bind was unsuccessful on directory gweinydd.gellioer.lleol for distinguished name ''. Directory returned error:[0x34] Unavailable.    
 
For more information, click http://www.microsoft.com/contentredirect.asp.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
 
 
 
Event Type:	Warning
Event Source:	MSExchangeDSAccess
Event Category:	LDAP 
Event ID:	2115
Date:		15/06/2009
Time:		21:36:58
User:		N/A
Computer:	GWEINYDD
Description:
Process STORE.EXE (PID=3332). DSAccess needs to close a connection to the Domain Controller gweinydd.gellioer.lleol due to error 0x80040952. 
 
For more information, click http://www.microsoft.com/contentredirect.asp.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
 
 
 
Event Type:	Warning
Event Source:	MSExchangeDSAccess
Event Category:	LDAP 
Event ID:	2115
Date:		15/06/2009
Time:		21:36:58
User:		N/A
Computer:	GWEINYDD
Description:
Process MAD.EXE (PID=2376). DSAccess needs to close a connection to the Domain Controller gweinydd.gellioer.lleol due to error 0x80040952. 
 
For more information, click http://www.microsoft.com/contentredirect.asp.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
 
 
 
Event Type:	Warning
Event Source:	MSExchangeDSAccess
Event Category:	LDAP 
Event ID:	2115
Date:		15/06/2009
Time:		21:36:58
User:		N/A
Computer:	GWEINYDD
Description:
Process INETINFO.EXE (PID=1920). DSAccess needs to close a connection to the Domain Controller gweinydd.gellioer.lleol due to error 0x80040952. 
 
For more information, click http://www.microsoft.com/contentredirect.asp.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
 
 
 
Event Type:	Error
Event Source:	MSExchangeDSAccess
Event Category:	LDAP 
Event ID:	2110
Date:		15/06/2009
Time:		21:36:58
User:		N/A
Computer:	GWEINYDD
Description:
Process STORE.EXE (PID=3332). Could not bind to DS server gweinydd.gellioer.lleol, error 51 at port 389. 
 
For more information, click http://www.microsoft.com/contentredirect.asp.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
 
 
 
Event Type:	Error
Event Source:	MSExchangeDSAccess
Event Category:	LDAP 
Event ID:	2110
Date:		15/06/2009
Time:		21:36:58
User:		N/A
Computer:	GWEINYDD
Description:
Process MAD.EXE (PID=2376). Could not bind to DS server gweinydd.gellioer.lleol, error 34 at port 389. 
 
For more information, click http://www.microsoft.com/contentredirect.asp.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
 
 
 
Event Type:	Error
Event Source:	MSExchangeDSAccess
Event Category:	LDAP 
Event ID:	2110
Date:		15/06/2009
Time:		21:36:58
User:		N/A
Computer:	GWEINYDD
Description:
Process INETINFO.EXE (PID=1920). Could not bind to DS server gweinydd.gellioer.lleol, error 51 at port 389. 
 
For more information, click http://www.microsoft.com/contentredirect.asp.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
 
 
 
Event Type:	Warning
Event Source:	MSExchangeDSAccess
Event Category:	LDAP 
Event ID:	2115
Date:		15/06/2009
Time:		21:36:58
User:		N/A
Computer:	GWEINYDD
Description:
Process STORE.EXE (PID=3332). DSAccess needs to close a connection to the Domain Controller gweinydd.gellioer.lleol due to error 0x80040951. 
 
For more information, click http://www.microsoft.com/contentredirect.asp.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
 
 
 
Event Type:	Error
Event Source:	MSExchangeDSAccess
Event Category:	Topology 
Event ID:	2102
Date:		15/06/2009
Time:		21:36:58
User:		N/A
Computer:	GWEINYDD
Description:
Process STORE.EXE (PID=3332). All Domain Controller Servers in use are not responding: 
gweinydd.gellioer.lleol 
 
 
For more information, click http://www.microsoft.com/contentredirect.asp.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Open in new window

Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Alan HardistyCo-Owner
Top Expert 2011
Commented:
Try shutting down the Exchange Information Store prior to restarting the server.

Often, services hang (or appear to hang) whilst waiting for a service to shut down.  It can quite often be the exchange IS in my experience and manually closing this down before restating can often solve the problem.  It is a pain, but gets around the problem.

There may be a fix, perhaps you are not on the latest Service packs or missing some updates etc.
yes, this is a common issue where exchange is running on a dc. microsoft suggest not running exchange on dc, but in reality of course sometimes budget dictates that we do.

if you find stopping information store does not fix you can shutdown all exchange services prior to shutting down server. in the past I have used a batch file with net stop commands to stop all exchange services and then initiate shutdown. the reason the shutting down gets stuck is because the active directory is shut down before exchange has a chance to shutdown, and so causes the exchange services to hang on shutdown. shutting them down manually effectively resolves this by shutting down whilst active directory is up and running.
Commented:
As stated this is common, this link to Sembee's site should give you what you need:
http://www.amset.info/exchange/shutdown-script.asp
meirionwylltSenior Desktop Engineer

Author

Commented:
Ah yes - great.  I'll compile a batch file from the info on the link and use that to restart the server from now on.

I might not get a chance to try this out for a couple of days - need to pick the right time for the server to be down.  But I will update this thread when this happens.

Thanks.
Great, it's worked for me in the past.

Something like:

net stop "Microsoft Exchange Information Store" /y
net stop "Microsoft Exchange System Attendant" /y
net stop "Microsoft Exchange IMAP4" /y
net stop "Microsoft Exchange Routing Engine" /y
net stop "Microsoft Exchange POP3" /y
net stop "Microsoft Exchange Management" /y
shutdown /r /t 0

Shaun

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial