BUG: SQL Server Setup May Stop Responding on a Very Fast Drive

Last reviewed: February 6, 1998
Article ID: Q180649
The information in this article applies to:
  • Microsoft SQL Server, versions 6.5
BUG #: NT: 17789 (6.5)

SYMPTOMS

Installing SQL Server on a very fast drive, such as an EMC Symmetrix system, may cause the setup program to stop responding on the "Setup is now installing the initial SQL Server configuration" screen.

CAUSE

Setup stops responding while running the Instmsdb.sql script. The Instmsb.out file will be created, it will but be empty, and the errorlog will contain the following:

   98/01/28 12:28:31.43 spid11   Database 'msdb' cannot be opened - it is
   currently being created.  Wait and try query again.

   98/01/28 12:28:31.43 spid11   Unable to proceed with the recovery of
   dbid <5> because of previous errors.  Continuing with the next database.

These errors may be followed later with an access violation (AV).

WORKAROUND

To work around this problem, copy the SQL Server installation files to the local hard disk drive to edit the Instmsdb.sql file. Add a WAITFOR DELAY

'0:00:01' statement to the very beginning of the Instmsdb.sql script.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words: fails fail hang hangs hung freeze frozed lock
locked up
Keywords : kbbug6.50 SSrvInst
Version : WINNT:6.5
Platform : winnt
Issue type : kbbug
Solution Type : kbworkaround


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 6, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.