BUG: SQL Server Does Not Start with Five Missing Mirror Files (235125)


The information in this article applies to:

  • Microsoft SQL Server 6.5
This article was previously published under Q235125
BUG #: 18761 (SQLBUG_65)

SYMPTOMS

When SQL Server mirroring is used and more than four mirror files have been lost, the SQL Server may not restart upon request. The following types of error messages will be visible in the SQL Server error log:
udopen: operating system error 3(The system cannot find the path specified.) during the creation/opening of physical device C:\SQL\DATA\SQLDB.MIR

udactivate (mirror): failed to open device C:\SQL\DATA\SQLDB.MIR for vdn 33 SQL Server i/o to the device will be disabled
udunmirror: i/o error on secondary device 'C:\SQL\DATA\SQLDB.MIR'

WORKAROUND

To overcome this problem with SQL Server mirroring, use miroring provided by Windows NT Server software or take advantage of hardware disk arrays that support various RAID levels.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 6.5.
Modification Type:MajorLast Reviewed:10/3/2003
Keywords:kbBug kbpending KB235125
©2003 Microsoft Corporation. All rights reserved.