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

"Sorry, Word Web App can't open this ... document because the service is busy." Office WebApp

Problem: Intermitten requests are not returning the pdf/word documents.  Most requests are working and occasionally 1 request doesn't work.  Every 4th request tries to get the pdf to display on Office Web Apps for a few minutes without any error message and then stops trying and displays the message "Sorry, Word Web App can't open this ... document because the service is busy." Initial Hypothesis: Originally I thought it was only happening to pdfs but it is happening to word and pdf documents (I don't have excel docs in my system).  My monitoring software SolarWinds is badly configured on my OWA servers as the monitor is showing green, drining into the servers monitoring the 2 application monitors are failing.  The server should go amber if either of the 2 applications fail and in turn red after 5 minutes.  At this point I notice that I can't log onto my 4 OWA/WCA server.  Web request are not being returned.  I look at my KEMP load balancer and it says al
Continue Read

Unable to create a "Send to Connection"- verification failed -url is a not a valid routing destination

ISSUE : Unable to successfully create a send to connection. When creating the Send to connection from Sharepoint 2010 Central Administration and click on Test URL for the Destination URL , we get the following error "verification failed -url is a not a valid routing destination" we see the following entry in the ULS logs Url validation failed for http://gmallya.test.com/sites/testrecordcenter/_vti_bin/OfficialFile.asmx   during Record and document center connection configuration with exception The request failed with HTTP status 401: Unauthorized .:  at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)     at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)     at Microsoft.SharePoint.OfficialFileSoap.GetServerInfo()     at Microsoft.SharePoint.ApplicationPages.OfficialFileAdminPage.<>c__DisplayClass2.&l
Continue Read