Problem Solve Report deployment error in SharePoint Integration mode
Today post related to SSRS Access Denied Problem.
I have a two system attached in a farm.
I have a updated SSRS Project source code so I need not to backup the report database. So took the back up of SharePoint content database and move it to another system. I installed new SharePoint Server in one machine and SharePoint SSRS other machine and add both server to farm. I attached the backup database with new application guess :) what.. it was working fine.
But the problem comes :( when I was going to deploy reports. It was giving me an access denied. When I open my old reports going to SharePoint Site and open report library still It was giving me an error because the reports only available in SharePoint content database not in Report server database.
Also my old database had not accessed to the Reporting Services account user.First I gave access to my SharePoint content database to Report Service account user.Change the authentication claims to windows.Change the site collection username. I added the Report service account user to built in administrator groups.Delete old reports from my report libraries.
I did the following Points to get things worked for me.
Problem to Deploy reports with SQL server business intelligence.
I have a two system attached in a farm.
- SharePoint Site
- SharePoint SSRS (Reporting)
I have a updated SSRS Project source code so I need not to backup the report database. So took the back up of SharePoint content database and move it to another system. I installed new SharePoint Server in one machine and SharePoint SSRS other machine and add both server to farm. I attached the backup database with new application guess :) what.. it was working fine.
But the problem comes :( when I was going to deploy reports. It was giving me an access denied. When I open my old reports going to SharePoint Site and open report library still It was giving me an error because the reports only available in SharePoint content database not in Report server database.
Also my old database had not accessed to the Reporting Services account user.First I gave access to my SharePoint content database to Report Service account user.Change the authentication claims to windows.Change the site collection username. I added the Report service account user to built in administrator groups.Delete old reports from my report libraries.
I did the following Points to get things worked for me.
Problem to Deploy reports with SQL server business intelligence.
- Make sure you are using http URL rather than https.
- SSRS Service Account is a member of Administrator group.
- SSRS Service Account having an access to the SharePoint Site.
- SSRS Service Account having a access to the SharePoint Content Database as well as the SharePoint Reporting Service URL (Incase to take a backup your site collection and moving to another server)
- Change your authentication mode to window authentication while deploying the report if you set the claim based then the current user will you accessible by the visual studio it will give you error. After changing the Authentication mode to claim to window change the site collection administrator (because claim based user attached the claim with it).
- SharePoint Site URL that is going to use in deployment than it Configured alternate access mapping.
- Still getting the error then you need to see the Permission because both SharePoint Service account as well as the SSRS Service account having a access to deploy the report as well as render the report in the SharePoint Content database.
Common Errors
One Solution : Disable Loopback Check
How to Change the DisableLoopbackCheck Registry Key
- "An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode"
- "Server was unable to process request. ---> The request failed with HTTP status 401: Unauthorized."
One Solution : Disable Loopback Check
How to Change the DisableLoopbackCheck Registry Key
- Open the Registry Editor (regedit).
- Caution: Incorrectly editing the registry can severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.
- Open the following key: HKLM\System\CurrentControlSet\Control\Lsa.
- Create a new DWORD value called DisableLoopbackCheck.
- Set the value to 1.
- Reboot the server.
- Note: This is required for the change to take effect.
- If this resolves the issue, there is a more secure way of making this change.
New-ItemProperty HKLM:\System\CurrentControlSet\Control\Lsa -Name "DisableLoopbackCheck" -Value "1" -PropertyType dword
Please check the Microsoft link to fix the problem http://msdn.microsoft.com/en-us/library/ee384252(v=sql.100).aspx
Comments
Post a Comment