Failed to retrieve text for this error reason 15105

The log shipping backup job for one of our databases is failing with the error message:

Read on «D:DataFilename.mdf» failed: 1(failed to retrieve text for this error. Reason: 15105)

Attempting to run the job out of schedule (to see if this gleans any additional data) results in a failure with the same message.

What is the cause of this message and how would I resolve it?

Select @@VERSION:

Microsoft SQL Server 2008 R2 (SP3) — 10.50.6220.0 (X64) Mar 19 2015
12:32:14 Copyright (c) Microsoft Corporation Standard Edition (64-bit)
on Windows NT 6.1 (Build 7601: Service Pack 1)

DB Compatibility Level: SQL Server 2008 (100)

Recovery model: Bulk-logged

Results of DBCC CHECKDB:

DBCC CHECKDB ('DatabaseName') WITH PHYSICAL_ONLY reports:

DBCC results for 'DatabaseName'.
Msg 8966, Level 16, State 2, Line 1
Unable to read and latch page (1:2112497) with latch type SH. 1(failed to retrieve text for this error. Reason: 15105) failed.
Msg 8966, Level 16, State 2, Line 1
Unable to read and latch page (1:2112498) with latch type SH. 1(failed to retrieve text for this error. Reason: 15105) failed.
Msg 8966, Level 16, State 2, Line 1
Unable to read and latch page (1:2112499) with latch type SH. 1(failed to retrieve text for this error. Reason: 15105) failed.
Msg 8966, Level 16, State 2, Line 1
Unable to read and latch page (1:2112500) with latch type SH. 1(failed to retrieve text for this error. Reason: 15105) failed.
CHECKDB found 0 allocation errors and 4 consistency errors not associated with any single object.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:2112497) allocated to object ID 557349150, index ID 1, partition ID 72057601138884608, alloc unit ID 72057601177681920 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:2112498) allocated to object ID 557349150, index ID 1, partition ID 72057601138884608, alloc unit ID 72057601177681920 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:2112499) allocated to object ID 557349150, index ID 1, partition ID 72057601138884608, alloc unit ID 72057601177681920 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:2112500) allocated to object ID 557349150, index ID 1, partition ID 72057601138884608, alloc unit ID 72057601177681920 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
CHECKDB found 0 allocation errors and 4 consistency errors in table 'schemaname.tablename' (object ID 557349150).
CHECKDB found 0 allocation errors and 8 consistency errors in database 'DatabaseName'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (DatabaseName).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

When trying to back up a SQL database, the backup may fail and the following error message is displayed on the screen:

What is SQL Server Error 15105?

MS SQL error 15105 hits the SQL database when a user tries to create database file backup on a network shared disk. Also, when hosting database file on a network share is not supported then the error 15105 occurs.

Most Probable Reasons to Cause Error 15105

1. Space Issue: Lack of space where the database backup file is to be created
2. Conflict with permissions: Inadequate permissions to access the location of backup data-file that is assigned to SQL Server service account
3. Issue with MDF File: Trying to attach an MDF file which was not detached properly
4. Conflict in folder location: Location of the folder in the error message is not of the same instance as the user wants to store the backup thus the service does not have access to the folder.
5. Location conflict: Backup file copied from the computer other than the destination computer
6. Ineffective Security: Backup file blocked due to security reasons
7. Corrupt Windows Operating System (OS)
8. Virus attack
9. Issue with software application where it is not installed properly
10. Innumerable startup entries and registry issues

Refer the factors mentioned above and analyze the exact reason for this error and try to fix it accordingly. Below listed methods will help you resolve the error 15105.

How to Resolve SQL Server Error 15105

The workaround process involves creating backup files of SQL database with following precautions and steps:

1. Using Backup

Steps before backup

• The drive volume should have enough space to upload backup files efficiently
• Perform defragmentation followed by space-check to ensure that it is more than 15%

Steps for backup

• Locate the original folder on Shared Network and right click on the Folder
• Click on Sharing and Security options
• Go to Permissions for Sharing tab
• Assign Full Access to the target account. If security is not the concern, then assign Full Access to everyone but take care to mention a specified period and once the restoring process is complete, modify the assigned permissions.
• Once the permissions are attached, click on Apply followed by Ok
• Go to Security tab and add that specific account for which full permits are granted. Assign appropriate privileges to the account.
• Click on Apply followed by Ok
• Take a backup of the database. There are chances of getting successful backup results.

Hopefully, the SQL server error 15105 is resolved, and SQL server backup device is accessible. However, it may happen that manual method does not produce useful results, due to corruption in SQL backup file or the source from where it is backed up, and this leads to inaccessibility of backup data.

1. Alternate and Ultimate Solution

Manual methods have limitations. Also, these processes are lengthy and time-consuming hence, use the SQL repair software to resolve the error. One of the most recommended software by SQL Administrators is Stellar Repair for MS SQL software which fixes the corruption in MDF files and resolves the SQL server error 15105.

Note: Stellar Repair for MS SQL software repairs the corrupt MDF & NDF files, hence there is no need to use the corrupt backup file to recover the database.

Repair SQL database in Simple Steps:

1. Install and Open software

1. Select the corrupt database and click on Repair button

1. Preview of all tables and other components of the database is displayed for verification. Also, a Log Report is available to analyse the repaired database-content

1. Save in MDF file format. Alternatively, you can save in other formats– CSV, HTML or XLS.

The SQL Recovery software recommended by Microsoft MVPs

Conclusion

SQL Administrators never want to get into the situation where they are unable to open the file due to SQL server backup error 15105, but there is no sure-shot way to avoid the error if it strikes. The best alternative is to download and install the Stellar Repair for MS SQL software and resolve the problem when it occurs. The 4-step solution fixes corruption-related errors and ensures that the database is accessible 24×7.