Operating System error 5(Access is Denied)

Question

Post reply

Operating System error 5(Access is Denied)

March 13, 2018 at 5:42 pm

This was removed by the editor as SPAM

Viewing 6 posts - 16 through 20 (of 20 total)

You must be logged in to reply to this topic. Login to reply

habeeb.matrix SSC Enthusiast Points: 161 More actions · Answer 1

I had this issue and all the solutions online was kind of misleading to my issue. I have the solution here.

http://dotnet-programming-solutions.blogspot.com/2012/10/attach-database-encountered-operating.html

The solution was to Run SSMS as Administrator.

jaylweb SSC Veteran Points: 282 More actions · Answer 2

habeeb.matrix (10/17/2012)
I had this issue and all the solutions online was kind of misleading to my issue. I have the solution here.
http://dotnet-programming-solutions.blogspot.com/2012/10/attach-database-encountered-operating.html
The solution was to Run SSMS as Administrator.

I'm not sure why you were trying to give full rights to NETWORK SERVICE since you we're trying to attach a database as a logged on user. The user you were logged on as needed full rights to "C:\testApp\App_Data\MyDB.mdf" not NETWORK SERVICE.

I'm glad you found a work around for your situation. But for those having the "Error 5" issue via the running SQL service might need to resolve the file permission issue.

habeeb.matrix SSC Enthusiast Points: 161 More actions · Answer 3

In most of the case, the issue must be resolved just by running SSMS as Administrator.

It might need Administrator privilege for file access.

Thanks and Regards,

Habeeb

http://dotnet-programming-solutions.blogspot.com

Hemant.R Ten Centuries Points: 1286 More actions · Answer 4

hi , OS error 5 corrsponds to permissions issue on the file and folder paths.

plz change path & check.

Check for the privileges whenever you get such an error

Sinfonico25 SSC Veteran Points: 257 More actions · Answer 5

Hello saidapurs, you must be careful when changing the service's login user; you must disable the "password expiration policy" from those users (local and destination server's users) in order to prevent issues when connecting to the share folder created on the destination server/PC. I highly recommend you to create an exclusively SQL Server Service's User to prevent this issue and other ones.

If you have a NAS you will not have this issue in public folders.

Hope it help you.