23 Minutes to Shutdown Enterprise Server 2003?

Tech-Archive recommends: Fix windows errors by optimizing your registry



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

  • RE: SBS 2003 Unable to connect to database STS_Config
    ... Uninstall the SQL server from the SBS 2k3 server from add/remove programs ... Uninstall Microsoft SQL Server Desktop Engine (SHAREPOINT) ... If AV software install any extra IIS virtual directory, ...
    (microsoft.public.windows.server.sbs)
  • Re: Memory issues with 64-bit SQL Server 2005 on 64-bit Win 2003 C
    ... I also checked the individual patch levels for the .NET drivers, SQL Server ... The SQL Server is fully patched, however Windows Update reported that the OS ... Lock pages in memory -- I guess you might have taken care of it as well. ...
    (microsoft.public.sqlserver.clustering)
  • RE: migrating from wmsde to sql server
    ... Click Start, point to All Programs\Microsoft SQL Server, and then click ... then click New SQL Server Registration. ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003 Unable to connect to database STS_Config
    ... Uninstall the SQL server from the SBS 2k3 server from add/remove programs ... Uninstall Microsoft SQL Server Desktop Engine (SHAREPOINT) ... If AV software install any extra IIS virtual directory, ...
    (microsoft.public.windows.server.sbs)
  • 18456 Login failed for user NT AUTHORITYSYSTEM
    ... After removing user Builtin\Administrators the server began logging event log ... I think what's going on is the Alert Engine is a service running under local ... system and is unable to connect to SQL server. ...
    (microsoft.public.sqlserver.server)