SharePoint 2013 SSRS – The remote server returned an error: (500) Internal Server Error

While (trying) to install SharePoint Server Reporting Services at one of my clients, I got into some pretty nice errors (SSRS Errors, Gotta catch ‘em all!). This one was the one that made me crazy for a few weeks because I never found out why I was having it, however I found out a way to fix it that worked, so I will share it with you in order to not lose hair over it like me. The error is basically getting a The remote server returned an error: (500) Internal Server Error whenever you click on either “System Settings” or “Manage Jobs”


The error:





This doesn’t tell us much, however when we go into Event Viewer we find two event IDs that are related to this and they both have similar messages.




Event ID 6398



The thing we find in common in both those errors is “Could not find permission set named ‘ASP.Net'”. After countless hours spent on google, bing and even yahoo and after even some of the best SharePoint people I know couldn’t find the issue, I discovered a way to make it work. Is this the best way? Probably not. I hope that it will help people that were in the same situation at me and want to get SSRS Working. Here are the steps.
What you probably already done to get to the error:
  • Install Reporting Servers + Addin
  • Run the PowerShell commands (Install-SPRSService & Install-SPRSServiceProxy & get-spserviceinstance -all |where {$_.TypeName -like “SQL Server Reporting*”} | Start-SPServiceInstance)
  • Create the SSRS Service Application.
What I did to fix it:
  • Delete the SSRS Service Application as well as Databases.
  • Run the following PowerShell command: “get-spserviceinstance -all |where {$_.TypeName -like “SQL Server Reporting*”} | Stop-SPServiceInstance”
  • Run the following PowerShell command: “Install-SPRSService –Uninstall’
  • Run the following PowerShell command: “Install-SPRSServiceProxy –Uninstall’
  • Go to Control Panel, Select SQL Server and then click REPAIR. Do a full repair of the SSRS + Addin feature (you shouldn’t have anything else installed on the server anyway, so just select all)
  • Run the PowerShell commands (Install-SPRSService & Install-SPRSServiceProxy & get-spserviceinstance -all |where {$_.TypeName -like “SQL Server Reporting*”} | Start-SPServiceInstance)
  • Create the SSRS Service Application.
Now everything should work! Drop a comment if this helped!

 

Comments

Post a Comment

Popular posts from this blog

"There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word." Office WebApp Error

Problem: When Opening a word document I get the following error when Office Web Apps tries to render the document " There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word. " Initial Hypothesis: Check the ULS logs on the Web Front End (SharePoint Server) as this doesn't tell me much.  I found the following issue in my UL S: WOPI (CheckFile) - Invalid Proof Signature for file SandPit Environment Setup.docx url: http://web-sp2013-uat.demo.dev/Docs/_vti_bin/wopi.ashx/files/6d0f38c0d5554c87a655558da9cedcad?access_token... Resolution: Run the following PS> Update-SPWOPIProofKey -ServerName "wca-uat.demo.dev" More Info: http://technet.microsoft.com/en-us/library/jj219460.aspx
Continue Read

"We’re sorry. We ran into a problem completing your request. Please try that again in few minutes." Excel Service SharePoint

Image
This article explains about Excel related issue in our SharePoint 2013 Environment. Whenever user tries to open excel files uploaded in document library, it launches browser to open the file and then displays below error- " We’re sorry. We ran into a problem completing your request. Please try that again in few minutes." Also see below screenshot- As part of issue analysis, following checks were performed- 1.) Check if Excel Services is running. ( This was running in our case. ) Open Central Administration -> System Settings -> Manage Services on Server -> Excel Calculation Service -> Started 2.) Check if Excel Service Application is associated to Web Application in question. ( This was configured in our case. ) Open Central Administration -> Application Management -> Manage Web Applications -> Select Web Application -> Select Configure Service Associations 3.) Check if Trusted File Location is configured for Excel Service...
Continue Read

Deployment error "The web.config is invalid on this IIS Web Site"

I've developed a webpart that deploys and works properly in my DEV environment. When I attempt to deploy to PROD I get the following error: SOMESERVER : http://acme.com/ : SharePoint - 41981 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\41981\web.config. SOMESERVER : http://acme.com/ : SharePoint - 41981 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\41981\web.config. SOMESERVER1 : http://acme.com/ : SharePoint - 23994 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\23994\web.config. None of these virtual directories exist. Any ideas how to resolve? Solution : In Central Administration-> Operation-> Services on Server, please stop the Windows SharePoint Services Web Application service , SharePoint will remove the sites in IIS. And then start the Windows SharePoint Services Web Application service agai...
Continue Read