Re: 23 Minutes to Shutdown Enterprise Server 2003?

Although it's tempting to blame it on the security patches you installed,
read through my canned answer below as an additional investigative avenue.
I think point #1 applies.

Some of these issues may not be relevant to your Shutdown situation. Skip
the ones that aren't relevant.

1) Freezes at a blank gray background while shutting down. If you wait long
enough (perhaps an hour or more), the system may in fact eventually shut
down.

Try disabling the "Clear virtual memory pagefile" setting via the local
security policy. Or, reduce the size of the pagefile itself. I heard of an
instance where a 32GB pagefile resulted in the system taking more than one
hour to shutdown (4/1/05).

http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/Default.asp?url=/resources/documentation/Windows/2000/server/reskit/en-us/gp/567.asp

2) Hangs at a blinking cursor while shutting down

Is Veritas installed?
http://seer.support.veritas.com/docs/260097.htm

3) Shutdown.exe fails to shutdown server

PsShutdown.exe in the free PsTools suite may work better:
http://www.sysinternals.com/ntw2k/freeware/pstools.shtml

4) Desktop remains up, no shutdown response to CTRL-ALT-DEL or Start >
Shutdown

Possible ACPI issue. Give this article a full read. Title is
'Troubleshooting Windows XP Shutdown Issues' but info is relative to Windows
Server 2003 as well.

http://www.theeldergeek.com/shutdown_issues_in_xp.htm

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

"Keith Jakobs, MCP" <elohir@xxxxxxxxxxxxxxxxxx> wrote in message
news:OAPZYwz3FHA.2196@xxxxxxxxxxxxxxxxxxxxxxx
Greetings:

We have a new box we recently purchased to serve exclusively as a warm
standby SQL server. The only thing it is to be doing will be receiving log
shipping jobs from our primary SQL server. The two boxes are basically the
same hardware, just one has faster processors, but both are quad CPU with 8
GB of memory. The older box is running on Windows 2000 Advanced Server and
the new one is running on Server 2003 Enterprise Edition.

The only thing I have installed on the new box is the O/S, SQL Server, and
SP3 (not SP4 due to memory concerns). I have run the Security Configuration
Wizard on the box. The original box is also only SQL SP3, but running SP4 of
Windows 2000.

Well, the new box has suddenly decided to take about 23 minutes to Shut
Down!!!! This started last week when I applied the latest run security of
patches, and now continues to do so every time. After initiating shutdown,
the server gives me the usual screens about saving my settings, and shutting
down windows, all rather quickly. However, at this point, it gives me the
plain blank gray screen as it continues to shut down windows. Apparently,
the event log records that the Event Log service has been stopped, and the
RAID volume gets busy for a solid 20 minutes or so before the system finally
shuts down. Whatever is holding up the O/S, is doing so after the Event log
has stopped, so there does not seem to be any other related events logged.

I have a hard time believeing this is my RAID arrray on EACH reboot, so can
anyone provide me with some ideas or notions as to what I might be looking
for? As I said, this is supposed to be a warm standby for a VERY critical
database server, so it needs to be supremely reliable, and starting off the
gun with 20 minute shutdowns is NOT a good way to start.

TIA for any help or advice.

Keith C. Jakobs, MCP


.

Relevant Pages

  • SecurityFocus Microsoft Newsletter #164
    ... Got Storage Security Risks? ... MICROSOFT VULNERABILITY SUMMARY ... Chat Client FTP Server Default Username Credential Weak... ... NetServe Web Server is a compact web server for Microsoft Windows ...
    (Focus-Microsoft)
  • Re: im being held in memory
    ... How can I harden my computer or server to secure it from hackers? ... Use firewall software and hardware and antivirus software that is ... Follow the instructions for hardening Windows and IIS at ... Install all service packs and security fixes from Microsoft and otherwise ...
    (microsoft.public.security)
  • MS and security: good effort but no cigar
    ... build upon the progress it's already made in security. ... The low-hanging fruit of millions of insecure Windows machines ... Then there's the issue of poorly secured server applications. ... and execute external virus and filtering ...
    (microsoft.public.windowsxp.general)
  • SecurityFocus Microsoft Newsletter #167
    ... MICROSOFT VULNERABILITY SUMMARY ... Multiple Vendor XML Parser SOAP Server Denial Of Service Vul... ... Proactive Windows Security Explorer ...
    (Focus-Microsoft)
  • Re: Group Policy broke my DCs
    ... > need to be very careful with tweaking services on domain controllers. ... > Group Policy - security policy at the OU level which makes it much easier ... > is complied from the Windows 2003 Server Security guide for baseline core ...
    (microsoft.public.windows.group_policy)
Loading