Share via

Reporting issues

  • Article

Applies To: Forefront Client Security

This topic contains the following sections:

Unable to access reports on a remote reporting server

Subreport could not be shown

SSA Summary report shows Error for Windows Version check

In this topic, you will find information regarding troubleshooting the reports in Client Security. While troubleshooting issues with reports, remember that SQL Server Reporting Services, MOM, and IIS are involved in the generation and rendering of the reports.

Troubleshooting Reporting Services

For information about issues with SQL Server Reporting Services, see Troubleshooting Reporting Services (https://go.microsoft.com/fwlink/?LinkID=82251).

For information about issues with MOM reporting, see Troubleshoot MOM Reporting (https://go.microsoft.com/fwlink/?LinkId=86298).

For information about issues with IIS 6.0, see Troubleshooting IIS 6.0 (https://go.microsoft.com/fwlink/?LinkId=82254).

Unable to access reports on a remote reporting server

After installation of SQL Server Reporting Services, an attempt to access the remote Report Manager might result in the following message: "The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write access to 'C:\Windows\Microsoft.Net\Framework\v2.0.50727\Temporary ASP.NET Files.'"

Background

This issue may occur on topologies with remote MOM reporting servers.

Solution

To resolve this problem, you must explicitly grant network service write permissions to the .NET Framework folder on the remote MOM reporting server.

To grant write permissions to the .NET Framework folder

  1. Open the following folder:
    C:\Windows\Microsoft.Net\Framework\ v2.0.50727\Temporary ASP.NET Files

  2. Right-click the folder and click Sharing and Security.

  3. Click the Security tab and click Add.

  4. In the Enter the object names to select box, type Network Service, and then click OK.

  5. Under Allow, ensure that the Read & Execute, List Folder Contents, and Read check boxes are selected.

  6. Under Allow, select the Write check box, and then click OK.

  7. In the warning message that appears, click Yes.

Subreport could not be shown

Opening a report for Client Security might result in the following error being displayed in one or more areas of the report: "Error: Subreport could not be shown."

Background

There are two possible reasons for this error:

  • Wrong location   The reporting server is pointing to the wrong computer running SQL Server or a SQL Server instance.

  • Insufficient permissions   The account configured (in SQL Server Reporting Services) to connect to the reporting database does not have appropriate permissions for the database.

Solution

To determine which reason is causing the error, attempt to directly open the subreport reporting the error, by clicking the name of the subreport.

If the reporting server is pointing to a wrong location, the report displays an error similar to the following:

Error message

An error has occurred during report processing.

Cannot create a connection to data source 'SystemCenterReporting'. Cannot open database "SystemCenterReporting" requested by the login. The login failed. Login failed for user username.

To verify the correct SQL Server computer and instance path

  1. In Report Manager, navigate to the report generating the error and click the Properties tab.

  2. Click Data Sources and under a Shared data source, note the path.

  3. Open the reporting Web site. If you chose the default virtual directory for reports, the URL is:

    https://hostname/Reports/

    If you chose to secure the viewing of reports with HTTPS, the URL is:

    https://hostname/Reports/

  4. Click SCDW.

  5. In the Connection type list, ensure that Microsoft SQL Server is selected.

  6. In the Connection string box, ensure that the correct SQL Server computer and instance name are entered.

Note

A period (.) denotes the local computer.

If the account has insufficient permissions, the report displays an error similar to the following:

Error message

An error has occurred during report processing. (rsProcessingAborted) Query execution failed for data set 'DSDashboardComputersTrend'. (rsErrorExecutingCommand) EXECUTE permission denied on object 'prSAS_UX_DashboardComputersTrend', database 'SystemCenterReporting', schema 'dbo'.

To determine if you are experiencing the SQL Server permissions issue

  1. Open the reporting Web site. If you chose the default virtual directory for reports, the URL is:

    https://hostname/Reportserver/

    If you chose to secure the viewing of reports with HTTPS, the URL is:

    https://hostname/Reportserver/

  2. Click Microsoft Operations Manager Reporting, click Microsoft Forefront Client Security, and scroll to DashboardComputersTrend.

  3. Click DashboardComputersTrend.

    If you are experiencing a SQL Server permissions issue, an error similar to the preceding error appears.

To grant permissions to the SQL Server computer

  1. In Report Manager, click SCDW and note the account in the Connect using section. This is the account under which the database is contacted.

  2. On the server with the System Center Reporting database, start SQL Server Management Studio.

  3. In the tree, expand Security, and then expand Logins. Do one of the following:

    • If the user account is listed, right-click the account, click Properties, and then go to step 5.

    • If the user account is not listed, right-click Logins and choose New Login.

  4. In the Login name box, enter the user account (domain\username).

  5. In the Login Properties dialog box, click User Mapping, and then under Users mapped to this login, select the System Center Reporting check box.

  6. Under Database role membership for: System Center Reporting, select the db_owner check box, and then click OK.

SSA Summary report shows error for Windows Version check

When viewing the Security State Assessment Summary report, you may see Error under Score for the Windows Version check.

Background

This error can occur for client systems that have WMI corruption problems.

Solution

To resolve the WMI corruption that causes this reporting error, you must register again all of the WMI dynamic-link library (DLL) files.

To register again WMI DLL files

  1. On the client computer reporting the error, open a Command Prompt window. (Click Start, click Run, and type cmd.)

  2. At the command prompt, type the following command:

    cd %windir%\System32\Wbem

  3. At the command prompt, type the following command:

    for %i in (*.dll) do RegSvr32 –s %i