Skip to main content

Operating system error 5(Access is denied.)

Actually I should write this post before my last post Network shared Backup , which I shared yesterday. I have decided I will share this week on network database activity. Show this is my 2nd post on the same. While I was started to backup, restore and creating a database on network shares I faced below errors. And most of the cases issues are related to Start-up services. Generally when we install SQL server the service will be Local or Network in this situation it will not work until we will not change start-up services or we will give full access to the network shared folder.  


Msg 3201, Level 16, State 2, Line 1
Cannot open backup device '\\192.168.XX.XX\ITDev\suman\bak\abc.bak'. Operating system error 5(Access is denied.).
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.

RESTORE DATABASE [world2] FROM  DISK = N'\\192.168.x.xx\ITDev\suman\bak\abc.bak' WITH  FILE = 1, 
MOVE N'world' TO N'\\192.168.xx.xx\ITDev\suman\bak\world.mdf', 
MOVE N'world_log' TO N'\\192.168.xx.xx\ITDev\suman\bak\world_log.ldf',  NOUNLOAD,  STATS = 5


Open SQL Server Services (Run->compmgmt.msc). You will see like below

Now change the start-up user which have full access on the file.

After changes we will see like below…

Now try again restore command...

RESTORE DATABASE [world2] FROM  DISK = N'\\\ITDev\suman\bak\abc.bak' WITH  FILE = 1, 
MOVE N'world' TO N'\\\ITDev\suman\bak\world.mdf', 
MOVE N'world_log' TO N'\\\ITDev\suman\bak\world_log.ldf',  NOUNLOAD,  STATS = 5


6 percent processed.
11 percent processed.
15 percent processed.
22 percent processed.
26 percent processed.
30 percent processed.
35 percent processed.
41 percent processed.
46 percent processed.
50 percent processed.
55 percent processed.
61 percent processed.
66 percent processed.
70 percent processed.
75 percent processed.
81 percent processed.
86 percent processed.
90 percent processed.
97 percent processed.
100 percent processed.
Processed 360 pages for database 'world2', file 'world' on file 1.
Processed 3 pages for database 'world2', file 'world_log' on file 1.
RESTORE DATABASE successfully processed 363 pages in 1.893 seconds (1.496 MB/sec).


Popular posts from this blog

mongoDB error : aborting after fassert() failure

What to do when facing errors on mongoDB “aborting after fassert() failure” I like errors, in mongoDB this is the first error I faced and luckily many times. This error i faced during restoring name-space on local and restarting db system. I am still searching the exact root cause of this issue but i am able to resolve the current problem through below steps. Remove all relevant namespace files from data-file route path.. Now repair mongo instance using mongod process. mongod --repair ////////// execute command from bin folder path  Then start server using mongd process, if started server successfully then .. mongod  ////////// execute command from bin folder path Restore last backups as normal process. Now check database by connecting mongo shell. Thanks for reading,  Please comment your experience if you faced and also share knowledge if you have better steps to resolve...  

SQL71562: external references are not supported when creating a package from this platform

Last week I got this error from one of developer who was trying to deploy his project from Testing server to SQL Azure QA server. He was using “Deploy Database to SQL Azure” option from SSMS Tool-Task option. After connecting to SQL Azure portal when operation started to deployment below errors occurs. Validation of the schema model for data package failed. Error SQL71562: Error validating element has an unresolved refrence to object xx.dbo.xxxx external refrences are not supported when creating a package from this platform . Reason: The reason of the this error was; some functions of project was dependent on master database and only single database was being deploy to SQL Azure. DACFx must block Export when object definitions (views, procedures, etc.) contain external references, as Azure SQL Database does not allow cross-database external references So, this error was coming. Solution : I suggested him to create those function to locally

How to add an article in Transactional Replication

If we have a set-up of Transactional Replication for Data Distribution running and wanting to add new object to replication on other server we can follow below process. To add an article In Transaction replication with PUSH Subscription