Sql server операция create file вызвала ошибку операционной системы

I have a database file .mdf from MS SQL EXPRESS in folder:

C:Program FilesMicrosoft SQL ServerMSSQL10.SQLEXPRESSMSSQLDATA

I would like to attach it to MS 2008 R2 (MSSQL10_50.MSSQLSERVER) but using Server Management Studio I receive the following error:

CREATE FILE encountered operating system error 5(failed to retrieve text for this error. Reason: 15105) while attempting to open or create the physical file

Do you have any idea how to solve it?

asked Jun 24, 2012 at 15:07

I was able to solve the problem running MS SQL Management Studio as ADMINISTRATOR.

Start->Run->services.msc->scroll through the list of services until you find SQL Server->right-click->properties->Log On tab:

Then choose Local System Account and check the Allow service to interact with desktop checkbox.

Restart the service.

answered Feb 27, 2019 at 14:12

Giving admin rights or full control to my database install location solved my problem

I had the same problem. After several tries, I realized that connecting the sql server with windows authentication resolved the issue.

I was getting similar error.

CREATE FILE encountered operating system error **32**(failed to retrieve text for this error. Reason: 15105) while attempting to open or create the physical file

I used the following command to attach the database:

EXEC sp_attach_single_file_db @dbname = 'SPDB',
@physname = 'D:SPDB.mdf'

answered Jun 1, 2013 at 20:30

This same problem occurs when the owners of the file have been deleted. When this happens, if you go to the file’s properties, you will see a SID rather than a user name. Take ownership of the file (giving yourself FULL CONTROL). Once that is done you can do whatever you need to do with the file.

I’ve had this work when logging in as the administrator didn’t do the trick.

answered Nov 30, 2012 at 15:00

As other suggested running as administrator will help.

However this only if the windows user is actually an admisnitrator on the machine which sql server runs.

For example when using SSMS from a remote machine it will not help using «run as administartor» if the user is only a administrator on the machine runing SSMS but not on the machine running SQL Server.

answered May 9, 2013 at 19:39

answered May 23, 2013 at 12:49

I had this issue on Windows 2003 with SQL 2005. I had to take ownership of the files as my Windows user account and I got the database to attache that way.

You have to right click on the file, select Properties, click OK to get past the information screen, click the Advanced button, select your account from the listing of available accounts or groups, apply that change, and Click OK on the Properties screen. Once you have done all that you will be able to manage the file permissions.

I logged into SSMS with Windows Authentication and I was able to attach the database without error.

Cheers!

answered Jan 4, 2014 at 13:19

If you are already running as an adminstrator, make sure the user you are using has the proper server roles.

1. Login as sa (if you can)
2. Expand the Security folder
3. Expand the Logins Folder
4. Right click on the user you would like to use
5. Select Properties
6. Select Server Roles
7. Select all the server roles
8. Click OK
9. Restart SSMS
10. Login with the modified user

answered Apr 24, 2013 at 15:14

answered May 13, 2014 at 4:45

My solution was slightly more complicated. After verifying the user the service was running as, running MSSMS as local and domain administrator, and checking folder permissions, I was still getting this error. My solution?

Folder ownership was still maintained by local account.

Properties > Security > Advanced > Owner > (domain/local user/group SQL services are running as)

This resolved the issue for me.

answered Jul 15, 2014 at 19:22

Opening SSMS as Administrator and running as SQL Auth vs Windows Auth did not work.

What worked was to just change my filename to the same location where the LDF and MDF files are located.

alter database MyDB
add file ( name = N'FileStreamName', 
filename = N'D:SQL DatabasesFileStreamSpace' ) 
to filegroup DocumentFiles;

answered Dec 9, 2014 at 9:54

I got this error when restoring a database that was backed up on another server. After a long struggle this is what I did

1. Enabled Instant File Initialization,

2. Granted permissions (full control) on the folder to the service account and my own windows account,

3. Restarted the SQL service.
   Database restored after that.

answered May 12, 2017 at 21:10

Here are the steps:

1. Right click on the .mdf and .ldf file.
2. Then select properties.
3. On the security -> advanced -> permission add the user which

copy your --.MDF,--.LDF files to pate this location For 2008 server C:Program FilesMicrosoft SQL ServerMSSQL10.MSSQLSERVERMSSQLDATA 2.

In sql server 2008 use ATTACH and select same location for add

answered Mar 17, 2018 at 11:10

In my case, Run as Administrator does not help. I solved the problem by changing the Build-in Account to Local System in Configuration Manager.

Here is what happened in my case.
I was asked to attach files for a database. I was given the file names as follows

• devdb.mdf and devdb.ldf

I proceeded to attach the files and kept getting the files are in use by another process.

I ran a query against the system view select name, physical_name from sys.master_files; and saw that the exact file names were already in use by another database, thus each time I tried to attach the files, I kept getting the error the files are in use by another process(sql server)

Thus if you are getting such a message, then also query against the system view sys.master_files and see which database may already be using the same name files.
Hereafter you will figure out what to do.

thanks.

answered Dec 11, 2018 at 21:33

answered Feb 20, 2019 at 9:58

I also face same problem, but i run Sql server run as administrator so now i resolve the error.

If facing similar issue in SQL Server running on docker container, fix by granting appropriate permissions to volumes.

1. Login to container as root user

   docker exec -it -u root <container id> bash

2. Grant appropriate permissions to all volumes path e.g. /var/opt/sqlserver/data

   chmod 777 </var/opt/sqlserver/data>

answered Mar 9 at 9:25

No need to do all this. Just right click on database files and add permission to everyone. That will work for sure.