Managing Active Directory does not always have to be complicated. If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why
Exchange 2003 enterprise suddenly shutdown slowly
Two months ago, we had migrated our Exchange server from 2000 Standard to 2003 Enterprise, and the total mailbox size is around 11GB...So far, it is normally running and quickly restart time (overall around 3-4 minutes, included all Exchange services started)
Today we try to restart our Exchange Enterprise, but the speed is very slowly, and hold on "the Windows is shutting down..". srceen. At last, we only manually power off and power on the Exchange server after 5-7 minutes...
After reboot, we have not found any error in Event Log.. And then further to search some information that talk about..
"Normally the timeout for exchange services to stop is 10 minutes. If you have a large Enterprise ...."
" Decrease the value of "WaitToKillServiceTimeout"
HKEY_LOCAL_MACHINE\SYSTEM\
The default value of "WaitToKillServiceTimeout"
Question..
1. 10 Minutes is really a normal restarting time for Exchange server (Enterprise), rite ?
2. Why no same case was happened as before... and also checked our record
- "priv.edb" + "priv.stm" around 15.7GB for the latest reboot
- "priv.edb" + "priv.stm" over 17GB today
In fact, The server will swtich on Enterprise mode when over Standard Checkpoint (16GB)... (it maybe wrong, it is just my personal supposition), so it need more time to stop and start all Exchange services in
real Enterprise mode.
Can explain the whole Exchange procedure to us please? Why it was changed ? What's the main reason ? Thanks a lot !
Today we try to restart our Exchange Enterprise, but the speed is very slowly, and hold on "the Windows is shutting down..". srceen. At last, we only manually power off and power on the Exchange server after 5-7 minutes...
After reboot, we have not found any error in Event Log.. And then further to search some information that talk about..
"Normally the timeout for exchange services to stop is 10 minutes. If you have a large Enterprise ...."
" Decrease the value of "WaitToKillServiceTimeout"
HKEY_LOCAL_MACHINE\SYSTEM\
The default value of "WaitToKillServiceTimeout"
Question..
1. 10 Minutes is really a normal restarting time for Exchange server (Enterprise), rite ?
2. Why no same case was happened as before... and also checked our record
- "priv.edb" + "priv.stm" around 15.7GB for the latest reboot
- "priv.edb" + "priv.stm" over 17GB today
In fact, The server will swtich on Enterprise mode when over Standard Checkpoint (16GB)... (it maybe wrong, it is just my personal supposition), so it need more time to stop and start all Exchange services in
real Enterprise mode.
Can explain the whole Exchange procedure to us please? Why it was changed ? What's the main reason ? Thanks a lot !
Asked:
3-
3
1 Solution
Yes, I will try it.
But I still have a question, why it is normally running and quickly restart time (overall around 3-4 minutes, included all Exchange services started) as before ?
But I still have a question, why it is normally running and quickly restart time (overall around 3-4 minutes, included all Exchange services started) as before ?
Well, It is related to Load on the Server, increase in sizes etc. Services will take longer over a period of time to shutdown.
But what is concerning is the fact that from 2-3 mins you are saying it has touched 10-12 mins overnight, but since there are no error logs at all, no services failing, I would also look at following:
Thanks
Nitin
But what is concerning is the fact that from 2-3 mins you are saying it has touched 10-12 mins overnight, but since there are no error logs at all, no services failing, I would also look at following:
- Are the DCs fine, any errors there
- Were any Groul Policies applied offlate that might not be optimized and it might be taking time
- Network Swithces, check there, it could be due to delays in communicaiton between DC and Exchange (thought within expected limits)
Thanks
Nitin
>>Are the DCs fine, any errors there
Yes, fine. No any errors
>>Were any Groul Policies applied offlate that might not be optimized and it might be taking time
No
>>Network Swithces, check there, it could be due to delays in communicaiton between DC and Exchange (thought within expected limits)
So far, no Network Switches changed. DC and Exchange are located on same Network Switches
Yes, fine. No any errors
>>Were any Groul Policies applied offlate that might not be optimized and it might be taking time
No
>>Network Swithces, check there, it could be due to delays in communicaiton between DC and Exchange (thought within expected limits)
So far, no Network Switches changed. DC and Exchange are located on same Network Switches
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
Yes Exchange is slow to reboot as all the dependent Exchange services do take time to stop and then later on start. Do you have DC also on the same server, it would also attribute to slow shutdown and startup.
Till the time you do not see any errors etc in Evertvwr I would say it is pretty ok. But just in case you are keen on improving the speeds, I would recommend the following 2 links that would automate stopping of services first then reboot
- http://www.msexchange.org/
- http://support.microsoft.c
- http://www.msexchange.org/
Hope this helpsThanks
Nitin