I came across this in a custom T-SQL-based log-shipping implementation for a major migration of hundreds of DBs over the last couple of weeks.I'm not sure the error message was "access denied", might have been something less specific.Recently I faced this issue with SQL 2008 R2 and the below solution worked for me: 1) Create a new database with the same name as the one you are trying to restore 2) While restoring, use the same name you used above and in the options, click the overwrite option You might give the above a shot if the other solutions don't work.The backup creator had MSSql version 10 installed, so when he took the backup it also stores the original file path (to be able to restore it in same location), but I had version 11, so it could not find the destination directory.From the location where you have stored your Exchange 2013 files run The first dialog gives you the opportunity to check for updates to the setup files before you proceed.
I am getting error messages in my event logs randomly stating my DNS server is unable to create a resource record: The DNS server was unable to create a resource record for 08d0c81f-d338-4790-9f7b-54bc20441616._msdcs.
My hunch is: you've already restored that database previously, and now, upon a second restore, you didn't check the checkbox "Overwrite existing database" in your restore wizard - thus the existing file cannot be overwritten and the restore fails.
Those backups are always the whole database (or at least one or several filegroups from that database).
Microsoft is conducting an online survey to understand your opinion of the Technet Web site.
If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.