Release Notes › Known Issues › Queries and Reports

Queries and Reports

The following are the known issues related to queries and reports.

Event Data With Non-UTF8 Characters Does Not Display in XML or PDF

Symptom:

Query or report results that contain non-UTF8 characters cannot be exported to XML or PDF formats. This issue applies only to events collected before updating to r12.5.

Solution:

Non-UTF8 characters in historical event data causes XML parsing to fail, which also prevents PDF export. Historical data without non-UTF8 characters exports properly to XML and PDF.

You can also export event data containing non-UTF8 characters as an MS Excel spreadsheet.

Query and Reports Pages Are Displaying Error Messages When the UI is Loading

Symptom:

When a CA User Activity Reporting Module server is loading the Queries and Reports pages, the following error is displayed on the UI:

Error getting query/report results: HTTP request error

Solution:

This error occurs if you have used a medium configuration for collection and reporting servers using CA User Activity Reporting Module as a virtual appliance. In a Hub and Spoke model, we highly recommend that you use a medium deployment configuration for a collection server and a large deployment configuration for a reporting server.

Queries and Reports Fail to Find Host

Symptom:

When you run queries or reports, the following error appears:

Error getting query results: Run Query: Host does not exist

Solution:

This error occurs when you launch a query or report after restarting the igateway, but before UI spindle initialization is complete. Wait at least 5 minutes after restarting igateway before running queries or reports. The delay allows the initialization to finish.