Troubleshooting
This section describes a few issues that could come up when you set up logging.
If you start the ICS_NET_STAT - Process Usage Stats job and it immediately stops:
Make sure that the queues were created correctly. In particular, make sure that the UsageStatQueue exists by completing the following steps:
Log in to the database server and open SQL Server Management Studio. Connect either as the database owner or as someone with administrative privileges.
In the left-hand pane, expand Databases and then expand the logging database.
Under the logging database, expand Service Broker, then Queues.
Verify that the UsageStatQueue is listed.
Check the logging database’s SST_ProcessSetting table. Make sure that CheckForMessages is set to True.
If you expect to see information related to individual logged events and you do not, check to see whether messages are sitting in the queue waiting to be processed. If messages are waiting, that likely means that the ICS_NET_STAT - Process Usage Stats job has stopped or failed.
To check for pending messages:
Log in to the database server and open SQL Server Management Studio. Connect either as the database owner or as someone with administrative privileges.
Run the following script against the logging database:
Select * from UsageStatQueue
If the queue contains messages, it might mean that the ICS_NET_STAT - Process Usage Stats job stopped or failed. Check for failure messages by viewing the job history and take any appropriate actions.
If you are expecting to see information related to aggregated data about the logged events, check to see whether the ICS_NET_STAT – ProcessAggregate job is running. If the job is running successfully, it may be the information does not include the most recent logs and will be processed with the next batch of changes. If the job has failed, check for failure messages by viewing the job history and take any appropriate actions.
The following two settings in JICS can affect your use of Reporting Services:
ReportingToolUrl – Determines the URL to be used for Reporting Services. By default this is /Reports. This values can be manipulated through the Site Manager > Framework settings > Location screen.
LogSiteStats – Turns logging on and off. This values can be manipulated through the Site Manager > Framework settings > Site stats screen. For full details on turning logging on, see Activate Logging.
These values can also be manipulated by updating the FWK_ConfigSettings table in the main JICS database.
Problems Viewing Data in the Reporting Feature
This section describes problems that might occur in the Reporting feature.
In the Reporting feature, if an authorized user clicks on the link labeled Click Here to View All Reports, and an HTTP 503 error displays, the problem may be that JICS is pointing to the wrong URL. Look at the URL in the window displaying the error; if this is not the correct URL, you will need to refer to change it in Site Manager. For details on doing this, see Configuring the URL Used by the Reporting Feature.
In some cases, a user trying to view report data may see an error that states in part “The report server cannot process the report or shared dataset ... Browse to the server or site and select a shared data source, (rsInvalidDataSourceReference).” In this case, the problem might be with the way you set up the logging data source. Refer back to Creating a Data Source and Importing the Reports, paying particular attention to steps 6 through 8. Note that the data source must be located in the Site Stats folder, not in the Jenzabar folder.