BUG: Access Violation if 4 Mirror Device Files Not Available

Last reviewed: April 29, 1997
Article ID: Q115517

The information in this article applies to:

  - Microsoft SQL Server version 4.2
BUG# NT: 791 (4.2)

SYMPTOMS

When a hard disk containing four or more mirror device files is unavailable during startup, SQL Server will experience an access violation and will not start. If the mirror device file on the master device is also unavailable, it will not count towards this total of four unavailable mirror device files.

WORKAROUND

Reduce the number of mirrored database devices that exist on separate physical devices to 2. Use Windows NT disk mirroring or use more advanced disk storage technologies, such as RAID 5.

It is possible to recover successfully, if copies of the mirror device files have been archived to tape. First, replace the physical disk and restore the lost mirror device files in the appropriate directory(s). Start SQL Server, when recovery is complete unmirror the related database devices and delete the mirror device files. Recreate the mirror(s) for the database device(s).

STATUS

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


Additional query words: Windows NT
Keywords : kbbug4.20 kbother SSrvWinNT
Version : 4.2
Platform : WINDOWS
Issue type : kberrmsg


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: April 29, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.