Article ID: 180649 - Last Review: October 16, 2003 - Revision: 3.0

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

This article was previously published under Q180649
BUG #: NT: 17789 (6.5)
Expand all | Collapse all

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.

APPLIES TO
  • Microsoft SQL Server 6.5 Standard Edition
Keywords: 
kbbug kbsqlserv650bug KB180649
Retired KB ArticleRetired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
 

Article Translations