Most of SharePoint customers suffer no issues when integrating SQL Server Reporting Services 2012 (SSRS 2012)  with SharePoint 2010 (SP 2010), however we had quite a bit of trouble. So for those who may also be having some trouble, we would describe how to fix the error. You can following the steps bellow:

- First, you should install SQL Server with Reporting Services Add-in for SharePoint
- Install SharePoint on the Reporting Services Server and connect that server up to the farm (using Configuration Wizard)

- Install the rsSharePoint.msi file provided by Microsoft on all your front-end servers running SharePoint

- Run these two commands on all front-end servers running Sharepoint
- Run these two commands on all front-end servers running Sharepoint  

  • Install-SPRSService
  • Install-SPRSServiceProxy

- Navigate to Central Administration -> System Settings > Manage services on server.  Start the SQL Server Reporting Services Service
- Navigate to Central Administration -> Application Management > Manage Service Applications.  Create a new SQL Server Reporting Services Service Application

Problem 1:
"Install-SPRSService : The term 'Install-SPRSService' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again"

Solve:
You should install the Reporting Services SharePoint Add-In (Found on your SQL Server 2012 installation media) on every server running SharePoint. Please don't use the rsSharePoint.msi provided on Microsoft's website.

Problem 2:
"When we try to create a SQL Server Reporting Services Service Application under 'Manage Service Applications', we receive an error relating to permissions to a registry key"

Solve:
There's nothing wrong with your registry except that SharePoint is looking for files that don't exist.  This is because you most likely installed the Reporting Services SharePoint Add-In with the rsSharePoint.msi file that Microsoft provides on their website. That file is a cut-down version of what gets installed when you install the Add-In from the SQL Server 2012 installation media.  Uninstall it from Control Panel, and re-install it with the SQL Server 2012 installation media. 

Problem 3:
"we have created my SQL Server Reporting Services Service Application, but when we try to access any of the links inside it (system settings for instance), we are receiving a 503 unauthorised error message"

Solve:
This may vary from case to case, but for me it was because we ran these commands on every front end server:

  • Install-SPRSService
  • Install-SPRSServiceProxy

When in actual fact, depending on your scenario (SharePoint Standard Licensing we think is the cause), you should only run these scripts on the server that you wish to be running the Server Service. You will need to uninstall them by using the following scripts (remember to delete the application and stop the service  in Central Admin first)

  • Install-SPRSServiceProxy –uninstall
  • Install-SPRSService -uninstall