Microsoft KB Archive/151106

= INF: Message in Errorlog When Physical Dump File Absent =

Article ID: 151106

Article Last Modified on 3/14/2005

-

APPLIES TO


 * Microsoft SQL Server 6.0 Standard Edition
 * Microsoft SQL Server 6.5 Standard Edition

-



This article was previously published under Q151106



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: kbprogramming kbusage KB151106

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.