Error message: exception report instance was not successfully created.

Document ID : KB000044453
Last Modified Date : 14/02/2018
Show Technical Document Details

Issue: The Configuration of CMS for CABI 4.1 SP3 results in exceptions if using 64-bit DSN, if you select 32-bit DNS architecture mismatch warning appears

If you configure both DSN as 64-bit – no errors in CMS looks clean

               Analysis reports work

               Audit reports throws exception

 

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

 

2016-06-24 07:54:28,399 ERROR [com.netegrity.ims.exception.EventExecuteStateException] (Thread-206) Exception: : java.lang.Exception: Report instance was not successfully created.  Please see the application server logs and the report server.

       at com.netegrity.webapp.page.reporting.ReportingInstanceEvent.createObject(ReportingInstanceEvent.java:202) [user_console.jar:]

       at com.netegrity.webapp.page.reporting.ReportingInstanceEvent.longRunningEventExecute(ReportingInstanceEvent.java:119) [user_console.jar:]

       at com.netegrity.ims.AbstractLongRunningEvent$RunningEvent.run(AbstractLongRunningEvent.java:293) [ims.jar:]

       at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_31]

 

2016-06-24 07:54:28,399 ERROR [com.netegrity.ims.exception.EventExecuteStateException] (Thread-206) Execution of event: ReportingInstanceEvent failed.  Exception encountered: Exception:Report instance was not successfully created.  Please see the application server logs and the report server.

2016-06-24 07:54:28,399 ERROR [ims.tmt.events] (Thread-206) Failed to execute ReportingInstanceEvent.

 ERROR MESSAGE:

Exception:Report instance was not successfully created.  Please see the application server logs and the report server.

2016-06-24 07:54:28,399 ERROR [ims.tmt.events] (Thread-206) Error during event execution [8242b4ea-0a829ea5-0048882f-b91c6483] ReportingInstanceEvent

If you Configure both DSN as 32-bit – no reports work 

Additional info

CABI 4.1 SP3 is install in the 32-bit program files, however it’s a 64-bit application: C:/Program Files (x86)/CA/SC/CommonReporting4/SAP BusinessObjects Enterprise XI 4.0/win64_x64/sia.exe" //RS//BOEXI40SIALODBL510VM048

Resolution:

CMS CABI 4.1 SP3 report server setup two DSN as followed:

  •         Report DB : 64 bit created from C:\Windows\System32\odbcad32.exe : Driver SQL Server
  •         Audit DB : 32 bit created from C:\Windows\SysWOW64\odbcad32.exe : Driver SQL Server  (NOTE warning when configuring DSN: architecture mismatch between application and driver – if you ignore error audit reports will work , however inside CMS auditing reports an warning no connection to Audit DB)

“Warning: There is no connection to the Auditing Data Store from the CMS LODBL510VM048.CentralManagementServer”

 

 

AdminUI 

  1. Report Server Connections uses the Agent API to connect and communicate see documentation
  2. Audit Report Connections : Name and DSN should be the same, DB server HOST : use servername and not IP address, database is the same database used on CMS CABI 4.1 SP3 system (note CMS tables and siteminder audit tables) 
  3. Make sure to allow mixed content (HTTP/HTTPS) in the browser (firefox/ie). 

By follow these instructions you will see a warning during the install, you can follow with 32 DSN for audit / DSN name should be the same as the one define in AdminUI/PS 

 

Reports for analysis and audit will now work in Admin UI