ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Report Instance Was Not Successfully Created

book

Article ID: 41054

calendar_today

Updated On:

Products

CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On

Issue/Introduction

Problem:

Audit Reports do not run, but the Analysis reports handle without issue.

The following error is generated in the adminui:

"Failed to execute ReportingInstanceEvent. ERROR MESSAGE: Exception:Report instance was not successfully created. Please see the application server logs and the report server."

 

Environment:  

AdminUI O/S: ALL

Report Server O/S: ALL

Audit Store: SQL Server(All versions)

 

Cause: 

The collation sequence is set to a case sensitive sequence.

 

Resolution:

Changing to a case-insensitive collation sequence will fix this problem.

In SQL Server, this can be done in the Maintenance section of the General tab, the database Collation name type should be set to a case insensitive collation

( Example: "SQL_Latin_General_CP1_CI_AS")

The "CI" in the example above stands for "Case Insensitive"

 

Environment

Release: ESPSTM99000-12.51-Single Sign On-Extended Support Plus
Component: