Export (0) Print
Expand All

Troubleshooting SQL Reporting Services Issues

Updated: June 1, 2009

Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2

This topic provides troubleshooting information to help you resolve issues using SQL Reporting Services in Configuration Manager 2007 R2.

noteNote
The information in this topic applies only to Configuration Manager 2007 R2 and Configuration Manager 2007 R3.

When you display reports containing data from client computers running a different language version of Windows than the version installed on the site server, localized report data from the client computer might display incorrectly in reports generated by SQL Reporting Services.

Solution

There is currently no workaround to this issue.

When you modify the properties of a displayed SQL Reporting Services report in the Configuration Manager console and then rerun the report, the report display is not refreshed.

Workaround

Use one of the following workarounds:

  • In the Report Options dialog box, select Open reports in a new window.

  • Close and then reopen the Configuration Manager console, and then run the report again.

If you have specified Use Reporting Services Reports for Admin console report links in the Report Options dialog box and then remove the reporting services point site role, report links in the Configuration Manager console will fail to display and you will receive the error message Unable to launch the report because it does not exist on the report server or the report server is unavailable.

Solution

Use one of the following solutions:

  • Clear the Use Reporting Services Reports for Admin console report links check box before removing the reporting services point site role.

  • In the Report Options dialog box, reselect the reporting point under Classic Reporting and then click OK.

When you try to run a SQL Reporting Services report from the Configuration Manager console, the report fails with insufficient privileges.

Solution

When reports are retrieved from SQL Reporting Services to the Configuration Manager console, the report properties are also retrieved. To retrieve these properties, use one of the following workarounds:

  • Modify the Browser role to include the Consumes Reports privilege.

  • Create a new role with the same privileges as the Browser role, and add the Consumes Reports privilege to this role.

  • Run the report directly from your SQL Reporting Services Web page.

For additional information, see Configuration Manager 2007 Information and Support.
To contact the documentation team, email SMSdocs@microsoft.com.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft