BUG: SQL Server Setup May Stop Responding on a Very Fast DriveLast reviewed: February 6, 1998Article ID: Q180649 |
The information in this article applies to:
SYMPTOMSInstalling 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.
CAUSESetup 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).
WORKAROUNDTo 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. STATUSMicrosoft 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
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |