INF: Message in Errorlog When Physical Dump File Absent

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 :