Επεξεργασία

Κοινή χρήση μέσω

MSSQLSERVER_17053

  • Άρθρο

Applies to: SQL Server

Details

Attribute Value
Product Name SQL Server
Event ID 17053
Event Source MSSQLSERVER
Component SQLEngine
Symbolic Name OS_ERROR
Message Text %ls: Operating system error %ls encountered.

Explanation

Generic operating system error occurred. The error message wraps a more specific operating system (OS) error, which can be used to help diagnose that failure. Examples would include reads or writes to data or log files that fail, registry read/write operations, or other unexpected Win32 API call failures.
You'll frequently see this error together with other error messages in the SQL Server error log. The operating system errors are shown with their numeric value, followed by the text message of the error.

User Action

Here are examples of how you may see 17053 error together with other errors. Each example provides ideas on how to approach the specific scenario.

Example with OS error 665

In this case, the underlying OS error 665 indicates a file system limitation has been encountered during file write or read.

Error: 17053, Severity: 16, State: 1.
K:\DATA\MyDB.MDF_MSSQL_DBCC11: Operating system error 665(The requested operation could not be completed due to a file system limitation) encountered.

The operating system returned error 665(The requested operation could not be completed due to a file system limitation) to SQL Server during a write at offset 0x00031397ce2000 in file 'K:\DATA\MyDB.MDF_MSSQL_DBCC11'.

Resolution:

If you run into this scenario, follow the steps in this article to resolve: OS errors 665 and 1450 are reported for SQL Server files

Example with SQL Server error 9001 and underlying OS errors 1117 and 21

In this case, the underlying OS error 1117 indicates the disk device has an error or is physically damaged.

Error: 17053, Severity: 16, State: 1.
SQLServerLogMgr::LogWriter: Operating system error 1117(The request could not be performed because of an I/O device error.) encountered.

Write error during log flush.

Error: 9001, Severity: 21, State: 5.
The log for database 'SQLContoso' is not available. Check the operating system error log for related error messages. Resolve any errors and restart the database.

In this case the underlying OS error is 21, which indicates the disk device is offline and not available for the OS and SQL Server to use.

Error: 17053, Severity: 16, State: 1.
SQLServerLogMgr::LogWriter: Operating system error 21(The device is not ready.) encountered.
Write error during log flush.

Error: 9001, Severity: 21, State: 4.
The log for database 'ContosoDB' is not available. Check the operating system error log for related error messages. Resolve any errors and restart the database.

Resolution:

If you encounter a similar scenario, address the underlying OS error. In this case work with your system administrator and hardware vendor to ensure that the disk device is online, functioning properly and there are no errors and damage reported. In cases like this one, you may have to check the physical integrity of the databases once the disk device is restored by running DBCC CHECKDB. If database damage is reported, restore a last known good database backup.

Example with SQL Server error 9001 and underlying OS errors 170

In this case, the underlying OS error 170 indicates the files on disk are being used or locked by some other program, most commonly a file system filter driver.

Error: 17053, Severity: 16, State: 1.
SQLServerLogMgr::LogWriter: Operating system error 170(The requested resource is in use.) encountered.

Write error during log flush.

Error: 9001, Severity: 21, State: 5.
The log for database 'SQLContoso' is not available. Check the operating system error log for related error messages. Resolve any errors and restart the database.

Resolution:

If you encounter a similar scenario, address the underlying OS error. In this case work with your system administrator to ensure that the database and log files aren't locked by other programs. Most commonly anti-virus or host protection software, defragmentation software, or backup software that holds locks on the files for a long time may cause this OS error. Make sure to exclude database files from being scanned or used; see How to choose antivirus software to run on computers that are running SQL Server.

In WSFC (clustered) environments, if drives aren't properly configured on the back end they may lock database files when they aren't supposed to. For more information on storage for WSFC, see Failover Clustering hardware solution and Failover cluster instances with SQL Server on Azure Virtual Machines - Storage

Example with SQL Server error 9002 and underlying OS error 112

In this case, the underlying OS error 112 indicates the disk volume is out of space.

Error: 17053, Severity: 16, State: 1.
L:\SQLLOG\Contoso.LDF: Operating system error 112(There is not enough space on the disk.) encountered.

Error: 9002, Severity: 17, State: 5.
The transaction log for database 'ContosoDb' is full due to 'DATABASE_MIRRORING'.

Error: 5149, Severity: 16, State: 3.
MODIFY FILE encountered operating system error 112(There is not enough space on the disk.) while attempting to expand the physical file 'L:\SQLLOG\Contoso.LDF'.

Resolution:

If you encounter a similar scenario, address the underlying OS 112 error. In this case work with your system administrator to free up disk space on the device and then attempt to address the full transaction log. For detailed steps on troubleshooting error 9002, see Troubleshoot a Full Transaction Log (SQL Server Error 9002).