Home > IT Answers > DataCenter > VERY slow server startup and shutdown
Shestopalov
55 pts.
0
Q:
VERY slow server startup and shutdown
Dell PowerEdge 2850, Exchange 2003, SQL database corrupt, SQL, Hardware, Exchange 2003 performance, Server Performance
Hi everybody!

We have a problem on our Exchange 2003 server thats been getting worse and worse. We have a Dell PowerEdge 2850 server, and every time we try to shutdown or restart it, it take 10 to 20 minutes just to shut down and another 20 to startup. Sometimes we have to force shut it down because we don't have the luxury of waiting for it. Also during startup we sometimes have to manually restart the server just to get to the desktop, otherwise it seems like it would hangup. I don't know if its trying to go through the Exchange database or whats it doing. We looked through the Event logs and nothing seems out of the ordinary. The server has over 100gb free space, has 2gb ram. I monitored the performance logs and on occasion the processor and memory would do a sharp spike to 100% and come down right a way, other than that the performance log shows a steady 5-10% utilization. So my question is, is there anything we can look for or monitor? Is there a database check utility? Maybe its hanging up trying to load/mount the database (I don't know even if it does that, so I'm kinda probing in the dark here).
ASKED: Jan 31 2009  1:00 AM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
RELATED QUESTIONS
0
Aguacer0
2815 pts.
0
A:
 RATE THIS ANSWER
+1
Click to Vote:
  •   1
  •  0
  • AddThis Social Bookmark Button
It could be any number of things.

Do other machines at your company have the same problem, or just this machine?
Does it still happen if you stop the Exchange services before you reboot the machine?

If you force the server down, then the Exchange service is going to have to cleanly mount the Exchange database when the server comes back online which could explain the long bootup time.

==============================

Is Exchange installed on a domain controller? If so, I would recommend demoting the server to a member server. There is a known issue with Exchange taking a really long time to startup and shut down when it is running on a domain controller.



+++++++++++++++++++++++++++++++++++++++++++++

Besides Exchange, what other applications are you running? Are you running an antivirus product not designed for Exchange? If you are running the Exchange on the DC, definitely go with the option to demote the server to a member server or you may need to modify the regisitry to delay the start of the Exchange services til the AD components are up and running.

You may want to download a demo of a great product I use quite often from Quest. They have a product called Spotlight on Exchange which will show you what's happening on your Exchange Server. Give that a try.
Last Answered: Feb 2 2009  3:23 PM GMT by Aguacer0   2815 pts.
Latest Contributors: BrienPosey   720 pts., Mrdenny   47070 pts.
  •   
0
0
RSS - Discussions Help
Discuss This Answer:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

NetSupport   430 pts.  |   Feb 2 2009  5:48PM GMT

If you’re using SBS 2003 check this.

Subject: SBS 2003 Slow to Shutdown

 <a href="http://support.microsoft.com/?kbid=827610" title="http://support.microsoft.com/?kbid=827610" target="_blank">http://support.microsoft.com/?kbid=82761…</a>

Start Registry Editor. To do this, click Start, click Run, type regedit in the Open box, and then click OK.
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControl
In the right pane, double-click the WaitToKillServiceTimeout value.
In the Value data box, type 120000 (this equals 2 Minutes), and then click OK.
Quit Registry Editor, and then restart Windows Small Business Server 2003.

 

Shestopalov   55 pts.  |   Feb 10 2009  6:12PM GMT

The Exchange server is part of a domain. That could be an issue. I’ve noticed if I let the server to shutdown properly it comes back up faster. Also the slow server start up and shutdown is intermitent so next setp I guess is we will demote the server to local workgroup. Thanks everyone.

 

mrdenny   47070 pts.  |   Feb 12 2009  2:39AM GMT

I’m pretty sure removing an Exchange server from the domain will break Exchange.

 

CosmoC   280 pts.  |   Feb 12 2009  3:05PM GMT

Running Exchange on a Domain Controller will work but is NOT recommended. If Exchange is installed on your only DC then that would probably explain it. You cannot demote the Exchange server to a member server without breaking it if Exchange is running on the same physical DC box. If that’s the case, I would install another DC first.

Try stopping the Exchange services in the order listed below before your next reboot:
net stop MSExchangeES
net stop IMAP4Svc
net stop POP3Svc
net stop RESvc
net stop MSExchangeSRS
net stop MSExchangeMGMT
net stop MSExchangeMTA
net stop MSExchangeIS /Y
net stop MSExchangeSA /Y

 

Lusy   825 pts.  |   Jul 15 2009  5:39AM GMT

Well it is possibility that your server load is enough it’s capability.
you should check about it’s hardware requirement according to your installed software and programed.
You can also check running about unwanted services on your server.
For more server support help please visit at: <a href="http://www.iyogi.net" title="http://www.iyogi. " target="_blank">www.iyogi.net</a>

 
0