In the recent past, I have been writing about different error messages on SQL Server that one encounters. Thanks to my blog readers who have been sharing a lot of errors with me either by email or by blog comments and asking for solution. If I find something interesting and more helpful to other, I write a blog for that. This is one of such blog.
2015-05-05 10:00:00.440 Backup Error: 3203, Severity: 16, State: 1.
2015-05-05 10:00:00.440 Backup Read on “M:\MSSQL\TLog\Production_1.ldf” failed: 1(Incorrect function.)
2015-05-05 10:00:00.440 Backup Error: 3041, Severity: 16, State: 1.
2015-05-05 10:00:00.440 Backup BACKUP failed to complete the command BACKUP LOG ProductionDB. Check the backup application log for detailed messages.
When I was searching for other emails with error message, I found another one as below.
2014-01-05 16:07:38.19 Backup Error: 3203, Severity: 16, State: 1.
2014-01-05 16:07:38.19 Backup Read on “M:\DatabaseName_DefaultData.ndf” failed: 1117(failed to retrieve text for this error. Reason: 15100)
This error would vary based on the actual cause. In first error message, it is operating system error 1 and in second case, it is operating system error 1117. To convert any operating system error number to text, we can use windows net command (net helpmsg) from command prompt as shown below
If you notice the second message, we are not seeing the text of the message 1117 but we are seeing “failed to retrieve text for this error. Reason: 15100”
What you should do in case of such error?
You should start looking at system and application event log based in operating system error. The example error which I have shown above are due to hardware level issues. Here is what we found in event log:
Log Name: System
Date: 5/5/2015 09:32:11 AM
Event ID: 51
Task Category: None
Description: An error was detected on device \Device\Harddisk4\DR4 during a paging operation.
Here is an article which explained event ID 51 https://docs.microsoft.com/en-us/troubleshoot/windows-server/backup-and-storage/event-id-51-information
Have you ever seen any similar errors? Put into the comment section to help others and share your knowledge. The best thing about these errors is that we get to learn from each other interesting concepts.
Reference: Pinal Dave (https://blog.sqlauthority.com)