{"id":16247,"date":"2018-02-20T11:29:41","date_gmt":"2018-02-20T11:29:41","guid":{"rendered":"https:\/\/www.stellarinfo.com\/blog\/?p=16247"},"modified":"2023-08-24T11:49:27","modified_gmt":"2023-08-24T11:49:27","slug":"sql-server-error-15105-unable-to-open-physical-file","status":"publish","type":"post","link":"https:\/\/www.stellarinfo.com\/blog\/sql-server-error-15105-unable-to-open-physical-file\/","title":{"rendered":"SQL Server Error 15105 – Unable to Open Physical File"},"content":{"rendered":"
When trying to back up a SQL database, the backup may fail and the following error message is displayed on the screen:<\/p>
\n<\/figure>\n<\/div>
What is SQL Server Error 15105?<\/strong><\/h2>
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.<\/p>
Most Probable Reasons to Cause Error 15105 <\/strong><\/h2>\n
Space Issue: Lack of space where the database backup file is to be created<\/li>\n\n\n\n
Conflict with permissions: Inadequate permissions to access the location of backup data-file that is assigned to SQL Server service account<\/li>\n\n\n\n
Issue with MDF File: Trying to attach an MDF file which was not detached properly<\/li>\n\n\n\n
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.<\/li>\n\n\n\n
Location conflict: Backup file copied from the computer other than the destination computer<\/li>\n\n\n\n
Ineffective Security: Backup file blocked due to security reasons<\/li>\n\n\n\n
Corrupt Windows Operating System (OS)<\/li>\n\n\n\n
Virus attack<\/li>\n\n\n\n
Issue with software application where it is not installed properly<\/li>\n\n\n\n
Innumerable startup entries and registry issues<\/li>\n<\/ol>
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.<\/p>
How to Resolve SQL Server Error 15105<\/strong><\/h2>
The workaround process involves creating backup files of SQL database with following precautions and steps:<\/p>
\n
Using Backup<\/span><\/strong> <\/li>\n<\/ol>
Steps before backup<\/strong><\/p>
\n
The drive volume should have enough space to upload backup files efficiently<\/li>\n\n\n\n
Perform defragmentation followed by space-check to ensure that it is more than 15%<\/li>\n<\/ul>
Steps for backup<\/strong><\/p>
\n
Locate the original folder on Shared Network<\/strong> and right click on the Folder<\/strong><\/li>\n\n\n\n
Click on Sharing and Security<\/strong> options<\/li>\n\n\n\n
Go to Permissions<\/strong> for Sharing tab<\/li>\n\n\n\n
Assign Full Access<\/strong> to the target account. If security is not the concern, then assign Full Access to everyone<\/strong> but take care to mention a specified period and once the restoring process is complete, modify the assigned permissions<\/strong>.<\/li>\n\n\n\n
Once the permissions are attached, click on Apply<\/strong> followed by Ok<\/strong><\/li>\n\n\n\n
Go to Security<\/strong> tab and add that specific account for which full permits<\/strong> are granted. Assign<\/strong> appropriate privileges to the account.<\/li>\n\n\n\n
Click on Apply<\/strong> followed by Ok<\/strong><\/li>\n\n\n\n
Take a backup of the database. There are chances of getting successful backup results.<\/li>\n<\/ul>
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.<\/p>
\n
Alternate and Ultimate Solution<\/strong> <\/li>\n<\/ol>
![\"SQL](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2018\/02\/SQL-database-error-15105.png\")
<\/figure>\n<\/div>![\"Stellar\"](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2020\/12\/Free-Download-New.jpg\")
<\/a><\/figure>\n<\/div>![\"Stellar\"](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2019\/04\/Select-SQL-Database.jpg\")
<\/figure>\n<\/div>![\"Stellar\"](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2018\/04\/Repair-selected-sql-database.jpg\")
<\/figure>\n<\/div>![\"Stellar\"](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2020\/12\/Preview-1024x786.png\")
<\/figure>\n<\/div>![\"Stellar\"](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2019\/04\/7-stellar-Repair-for-ms-sql-new-or-live.png\")
<\/figure>![\"Stellar\"](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2017\/11\/mvp-logo.png\"){kind=logo}
<\/a><\/figure>\n<\/div>