INF: Message in Errorlog When Physical Dump File Absent

 Last reviewed: April 8, 1997
Article ID: Q151106

The information in this article applies to:
  • Microsoft SQL Server, versions 6.0 & 6.5

SUMMARY

This article mentions two messages related to backup devices that can appear in the SQL Server errorlog when the actual physical file for the dump device does not exist.

MORE INFORMATION

When you create a disk dump device, the corresponding physical file is not created until you actually dump to it at least once. Before ever dumping to that device, if you try to see what it contains (by clicking the Plus Sign ("+") in front of the dump device name in SQL Enterprise Manager, Server Manager), you will get the following error message in the errorlog: 

   dbvolopen: Backup device 'c:\bak\test.dat' failed to open, operating
   system error = 2(The system cannot find the file specified)
There is no actual physical file corresponding to the null dump device "diskdump" even after you actually dump to it. If you click the "+" in front of "diskdump," you will get the following message in the errorlog: 

   kernel   read_db_hdr: Read failure on backup device 'nul', returned
   operating system error (null)

Additional query words: sem tool
Keywords : kbprg kbusage SSrvEntMan SSrvErr_Log
Version : 6.0 6.5
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 8, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.