SQL Server 2012 Reporting Services Tips, Tricks, and Troubleshooting

SQL Server 2012 Reporting Services Tips, Tricks, and Troubleshooting


This is the Microsoft SQL Server 2012 page for general issues and questions. This page will be updated regularly as more content and resources become available.

 

Other Resources


SQL Server 2012 Release Notes
Power View Overview (en-US)
Primary page for information on troubleshooting SSRS issues and errors

_____________________________________________________________________________________________________________________________________________________________________________________

Using an Older Version of ReportViewer with SQL Azure Reporting

Issue:

If you try to use a version of the ReportViewer control that is older than the version that is included in Visual Studio 2010 SP1, you might see the following error:

"Retrieving the print .CAB file by name is no longer supported. Specify the CLSID of the .CAB file via the rs:PrintControlClsid parameter."


Workaround:

Azure client print controls have different CLSIDs. Print cabs built for Azure are different than those built for on-premises. Because the ReportViewer control in Visual Studio 2010 SP1 retrieve those CLISIDs from Azure server, the control fails requests for print cabs from earlier versions of ReportViewer.

To resolve this issue, use the Microsoft Report Viewer 2010 SP1 or later versions. You can download the Microsoft Report Viewer 2010 SP1 Redistributable Package from Microsoft Download Center, at http://go.microsoft.com/fwlink/?LinkId=240146.


Troubleshoot Installation and Upgrade Issues with SQL Server 2012


See the SQL Server Books Online topic Troubleshoot a Reporting Services Installation

 

SharePoint Mode Issues


You do not see the SQL Server Reporting Services Service in SharePoint Central Administration after Installing Reporting Services



Background:

If after successfully installing Microsoft SQL Server 2012 Reporting Services in SharePoint mode and the Microsoft SQL Server Reporting Services Add-in for SharePoint 2010, you do not see “SQL Server Reporting Services” in the following two menus, then the Reporting Services service has not been registered:

 

SharePoint 2010 Central Administration -> "Application Management" -> "Manage Services on Server" page

Or
SharePoint 2010 Central Administration -> "Application Management" -> "Manage Service Applications" ->"New" menu

Workaround:

To register and start the Reporting Services SharePoint Services, complete the following:
Open the

  1. SharePoint 2010 Management Shell with administrator privileges.Right click the icon and click, "Run As Administrator". Run the following three cmdlets from the shell:
    • Install-SPRSService
    • Install-SPRSServiceProxy
    • Get-SPServiceInstance -all |where {$_.TypeName -like "SQL Server Reporting*"} | Start-SPServiceInstance
  2. Verify the SQL Server Reporting Services Service shows status as “Started” on the page: SharePoint 2010 Central Administration -> "Application Management" -> "Manage Services on Server"

Note:  When running the PowerShell commands, if you receive an error  similar to this one, "The term 'Install-SPRSservice' is not recognized as the name of a cmdlet, function, script file, or operable program," install the Reporting Services add-in for SharePoint Products and then re-run the commands. See Where to find the Reporting Services add-in for SharePoint Products, http://msdn.microsoft.com/en-us/library/069ac476-6336-44a9-a0e7-db1c4888948f.

You Are Not Able to Start Reporting Services Configuration Manager

Background:

This is by design with the SQL Server 'Denali' release.  Use SharePoint Central Administration to configure a SQL Server 'Denali' report server in SharePoint mode.  The Reporting Services configuration manager is only used for report servers in Native mode.

Native Mode Issues


See Also


Sort by: Published Date | Most Recent | Most Useful
Comments
  • Richard Mueller edited Revision 14. Comment: Fix heading lines in HTML to improve the TOC

  • Craig Guyer - MSFT edited Revision 15. Comment: removing older references to pre-release version

Page 1 of 1 (2 items)