Skip to main content

WSS Backup failed - Cannot open backup device

I was trying to backup my WSS 3.0 farm when I encountered this error:

Object SharePoint_Config failed in event OnBackup. For more information, see the error log located in the backup directory. SqlException: Cannot open backup device '\\servername\backup\spbr0001\0000001.bak'. Operating system error 5(Access is denied)

I guessed this would be because of permissions with the backup folder. I had created a shared folder in my server where WSS was installed. I had given Share and security permission "Change/Modify" for the Network Service user. But that did not work. I followed these steps and it solved my issue:

1. Set the SQL Server (MSSQLSERVER) Windows service to run as a domain account and restarted the service and IIS.
2. Granted "change" Share permissions on the backup folder for the user that runs the Central Admin application pool, db SQL account, and WSS Timer service.
3. Granted "Modify" Security permission on the backup folder for the user that runs the Central Admin application pool, db SQL account, and WSS Timer service.
4. Checked if I could access the Shared backup folder
Labels:

Comments

Anonymous said…
Dear,

Do one thing see the Service Account of SQL Server Service.
And grant rights on the sharedfolder where you wanna backup your SP Farm or Objects.

Whenever this normally found when SP Back Service request the SQL Service for DB Backup. SQL Service backup itselft the specified DBs in SP Backup.

This may be valid for different others services as well.

Thanks :)
May 17, 2012 at 6:19 PM
Post a Comment

Popular posts from this blog

"Cannot impersonate user for data source" - SSRS reports

We were getting this strange error while viewing our reports in SharePoint that was deployed using BIDS 2005: An error has occurred during report processing. Cannot impersonate user for data source 'datasource' Logon failed I tried many things but nothing worked. I did some research and found many blog posts which suggested me to reapply the password on the datasource file specified in the error message and save it again. That didn't work for me. I saw some check boxes in the data source file that read "Use as Windows Credentials" and "Set Execution Context to this report" and I didn't know what they meant. I unchecked those in my data source and then when the refreshed the page the report started displaying.
2 comments
Read more

Users do not show up in SharePoint People Search or People Picker

I had this issue with people picker in a classic mode web application in SharePoint 2013 and this site is in 2010 mode - users in certain sub-domains would not show up in People Picker. I was aware of stsadm commands to fix this and we ran the stsadm command to hook up people picker with another domain some time back. The latest issue was that people picker was not returning users from the root domain and few sub domains. After researching on the internet I found (contrary to my thoughts) that we could use PowerShell and not just stsadm to map People Picker to domains. It is a good idea to first check what domains are added/mapped to the web application using the following commands: $wa = Get-SPWebApplication -Identity http://mywebapp.com #List the Domains $wa.PeoplePickerSettings.SearchActiveDirectoryDomains This will list the domains currently People Picker is looking up for that web application. I used the following script to map our AD forest to People Picker:
Post a Comment
Read more

Report Server has encountered a SharePoint error. ( rsSharePointError)

I was receiving this error on the "Report Server Web Service URL" on our SharePoint farm: Report Server has encountered a SharePoint error. ( rsSharePointError) Access to this Web Site has been blocked. Please contact the administrator to resolve this problem. This site URL is configured via Central Administration > Configure Reporting Services Integration > Reporting Services Integration if Reporting Server feature/Add-in is installed on the farm. After doing some research I found out that this page somehow enumerates through entire site collections before it throws this error. As part of troubleshooting step I checked if the domain user configured for reporting service is has sufficient privileges in the farm and also as local admin of the sql box, but this did not solve the issue. We raised this issue with the vendor and they made us update our SQL Server 2005 to latest SP and CU; still we had the error. The reason was nobody was sure if this er
3 comments
Read more