| Event Id | 17204 |
| Source | MSSQLServer |
| Description | %1: Could not open device %2 for virtual device number (VDN) %3!d!. |
| Event Information | CAUSE: The file listed in the message is not accessible to SQL Server for read and/or write operations during startup or database recovery. SQL Server might not be able to find the file, the file may be locked by another application, or SQL Server may not have permissions to access the file. This error is usually raised in combination with 17207 %1: Operating system error %3 during the creation/opening of physical device %2. RESOLUTION: 1. Check the SQL Server error log and the Event Viewer logs for any other errors that occur at the same time as this error. 2. Verify that the file exists in the exact path listed in the error. If it does not, move the file to that path. 3. Verify that the file does not have the read only attribute set to true. 4. Verify that the SQL Server startup account has read and write permissions to the folder and file. 5. Verify that the file is not held open by another process such as backup software or virus scanner software. 6. If you can rename the file then it is not locked by another application. 7. If this error resulted after you moved databases to a new location, put all files back in their original location. 8. Run hardware diagnostics for the drive where the file resides to verify the disk and file are healthy. 9. If the file listed is encrypted, verify that the version and edition of Windows and of SQL Server support encrypted files If you get this error from rebuildm.exe verify that you choose the location of files from the original SQL Server installation CD or of a copy of those original files. |
| Reference Links | Microsoft product: SQL Server Version: 2000.80.760.0 Event Source: MSSQLServer Event ID: 17204 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.