Knowledge Base |

# BUG: Missing Log Device Causes Access Violation at Startup

Article ID: 117514

Article Last Modified on 10/16/2003

APPLIES TO

- Microsoft SQL Server 4.21a Standard Edition, when used with:
  - Microsoft Windows NT 4.0

This article was previously published under Q117514
BUG# NT: 831 (4.21)

## SYMPTOMS

During startup, SQL Server generates an access violation and a Dr. Watson error may be displayed. Examining the SQL Server error log will show an error opening a device that contains the active portion of the log.
For example:

       server   Activating disk 'TestLog'
       kernel   udopen: operating system error 2(The system
                cannot find the file specified.) during the
                creation/opening of physical device
                e:\sql\data\TestLog.dat
       kernel   udactivate: failed to open device
                e:\sql\data\TestLog.dat for vdn 2
       kernel   SQL Server i/o to the device will be disabled

The last entry in the error log will show SQL Server attempting to run recovery on the database with the missing log:

       server   Recovering database 'Test'
       kernel   udstartio: vdn 2 has not been set up

## CAUSE

SQL Server is causing an access violation while trying to return an error message.

## WORKAROUND

Verify that the log device exists and is named correctly. The file name and path that SQL Server is attempting to use is recorded in the error log.

## STATUS

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

Additional query words: trap GP-Fault errorlog

Keywords: kbother KB117514