We value your feedback.
Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!
Course Of The Month
10 days, 21 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Exchange 2003 enterprise suddenly shutdown slowly
Posted on 2008-09-29
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 !
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
3-
3
6 Comments
Hi,
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
Thanks
Nitin
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/
articles/A utomating- Quicker-Ex change-200 0-2003-DC- reboot.htm l - http://support.microsoft.c
om/kb/5550 25 - http://www.msexchange.org/
ExchangeNe ws/July-20 05-SBS-200 3-Slow-Shu tdown-Fix. html
Thanks
Nitin
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
Featured Post
For Any Use & On Any Platform
Contextual Guidance at the moment of need helps your employees/users adopt software o& achieve even the most complex tasks instantly. Boost knowledge retention, software adoption & employee engagement with easy solution.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Read this checklist to learn more about the 15 things you should never include in an email signature.
A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
In this video we show how to create a Contact in Exchange 2013. We show this process by using the Exchange Admin Center.
Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center.
Navigate to the Recipients >> Contact ta…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment.
The video tutorial explains the basics of the Exchange server Database Availability grou…
Suggested Courses
Earn Certification
HTML5 Specialist - Certification
Free withPremium
Course of the Month10 days, 21 hours left to enroll
Earn Certification
MTA Mobility Device Fundamentals (Exam 98-368)
$59.00$53.10
628 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.