Export (0) Print
Expand All

General troubleshooting

Published: December 16, 2009

Applies To: Forefront Client Security

You determine what the issue is by first identifying when the problem occurs during Client Security operation. The following table describes possible server problems and their causes. Client troubleshooting is covered later in this guide.

 

Issue Possible cause

The Client Security console does not fully open.

Inadequate user account permissions on the collection (or OnePoint) database

The console displays no trends or gauges.

  • Reporting server or the SQL Server computer hosting the reporting database unreachable or down

  • User account permissions issues

  • IIS configuration problems (such as Secure Sockets Layer (SSL) or port issues)

  • Inadequate SQL Server database permissions

  • Client Security Configuration wizard has not been completed

Clicking a report in the Client Security console produces a "ReportingServiceUnavailable" message.

  • SQL Server Reporting Services stopped

  • Server running SQL Server Reporting Services unavailable

Clicking a report in the Client Security console results in a "Permissions granted to username are insufficient for performing this operation" message.

  • Inadequate permissions to the reporting database or the SQL Server Reporting Services server

Clicking a report produces a "Page cannot be displayed" error.

  • World Wide Web service not running

  • Issues with contacting the reporting server

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft