Skip to main content

Problem Solve Report deployment error in SharePoint Integration mode

Image
By
Today post related to SSRS Access Denied Problem.

I have a two system attached in a farm.
  • SharePoint Site
  • SharePoint SSRS (Reporting)
In SharePoint Site SSO already implemented. I need to move my SharePoint Content database as well as report database server database to new Server.

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  

  1. "An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode"
  2. "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


  1. Open the Registry Editor (regedit).
  2. 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.
  3. Open the following key: HKLM\System\CurrentControlSet\Control\Lsa.
  4. Create a new DWORD value called DisableLoopbackCheck.
  5. Set the value to 1.
  6. Reboot the server. 
  7. Note: This is required for the change to take effect.
  8. 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

Popular posts from this blog

SharePoint RPC Protocols Examples Using OWSSVR.DLL

By
What is SharePoint RPC Protocols? Part 1 This reference includes information about the methods and usage of SharePoint Foundation Remote Procedure Call (RPC) protocol. This protocol can be used in Win32-based applications or in ASPX applications to make HTTP POST requests to the server. Methods in this protocol that do not modify the contents of the database can also be used in URL protocol to make HTTP GET requests. Definition taken from http://msdn.microsoft.com/en-us/library/ms448359.aspx You will find the OWSSVR.DLL in SharePoint 2010 Server Physical Path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI and MOSS C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI OWSSVR.DLL List of commands DialogView  Display ExportList GetProjSchema GetUsageBlob HitCounter RenderView To read more about the OWSSVR.DLL command Please read the URL Protocol from Microsoft Blog having a URL http://msdn.microsoft.com/en...
1 comment
Read more

SharePoint 2013 Search Database Part 1

By
SharePoint 2013 Search architecture drastically change, as earlier in FS4SP 2010 we have 2 search applications “FASTContentSSA” and “FASTQuerySSA” and 7 total database in use. Following are the List of DB (FS4SP) FASTContentSSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTQuerySSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTSearchAdminDatabase : Fast Search Admin Database  In SharePoint 2013 search has only 1 Search Service application and 4 database in use. No property store database need any more, now the properties are directly stored inside the index component and all the index directly indexed to the physical system where FS4SP data comes from database as well as from the File system now data directly stored and indexed/ retried from the Physical disk because of this performance increase and search experien...
Post a Comment
Read more

STS CryptographicException Error : Key set does not exist

By
Common mistakes Both SharePoint Site and SSO Site NOT running on the same application pool. Application pool identity user doesn’t have permission to access the certification.  Solution to this problem Set the same identity pool to  : 2. Be sure to grant rights to the certificate for the App Pool running the web service Start -> Run -> MMC File -> Add/Remove Snapin Add the Certificates Snap In Select Computer Account, then hit next Select Local Computer (the default), then click Finish On the left panel from Console Root, navigate to Certificates (Local Computer) -> Personal -> Certificates You're certificate will most likely be here. Right click on your certificate -> All Tasks -> Manage Private Keys Set you're private key settings here. Add app pool account Reset iis
Post a Comment
Read more