Has anyone else experienced this?  We use the TRIRIGA/Kurve Reporting Add-On/App and it isn't working after applying Platform Fix Pack 5.0.5.  We've identified the following information to share and get feedback:

• Fix Pack 5.0.5 was required due to a security fix
  • FP .5 included updated JAR files and BIRT Viewer UI updates
    • Also mentioned the Axis jar file being updated among other Security updates
• Initial issue is that all existing reports won't load (same with graphs)
  • Have around 150 reports and graphs, none work 
  • Upon clicking a report, the Loading Reports is displayed, then the Loading Query Data is displayed, but the spinning wheel just keeps spinning  
    • This is typically followed very quickly by the count of rows that will be included in the report even if it takes a few moments to display the report output/content, this never happens now, just the spinning wheel
  • Enhance Report Rendering mode is disabled in the Admin Console (but most of our reports don't include large datasets)
  • The Source Query does not have any special characters.  The Source Query runs fine in the classic TRIRIGA UI.  Exporting the report SQL also runs fine in the Admin Console under the Database Query Tool
• When trying to Create a new report, we select the record type Report and no matter which existing report is selected, we get the following error:
  • Query does not exist or is not valid.  Please contact your administrator for assistance.
  • Also says, AxiosError: Request failed with status code 500
  • Tried creating new query in classic UI with very small output (40 records/rows)
    • Was able to see the query for selecting when creating a new report in the Reporting App, but get same error as above
• Can't find much in the FP .05 Read Me or online, other than some basic troubleshooting
  
  • Online searches seem to confuse the TRIRIGA Reporting Add-On/App with the Eclipse BIRT Reporting tool (not sure if there's some connection?)
  • There's mention of checking the logs but couldn't find any additional helpful info in the logs
  • There's mention of JDBC driver config maybe being a cause, but that's primarily with DB2, we use Oracle

Any help, thoughts, updates, experience with troubleshooting the TRIRIGA Reporting would be greatly appreciated.  Thank you.

We use Tjene Kurve, not TRIRIGA Reporting so there is a version discrepancy, but I think this might apply to your case as well.

You have not specified from which version of the platform did you upgrade from, nor the version of your Reporting module, but I think you have to reach out to IBM and get the applicable fix pack for your environment.

Hope this helps,

Vladimir

Thanks Vladimir, this helps. 

We are using TRIRIGA Reporting 1.1.25, which is the highest version available in the IBM Software Access Catalogue.  We're on TRIRIGA App v11.6.1 and upgraded from Plat version v5.0.2 to v5.0.5 recently, which is when the issue started.  Not sure if we can try the Kurve v 1.29 or 2.0, but I do see mention of v1.28 and 1.29 having TRIRIGA enhancements, just not sure where to download them. 

We did submit a support ticket to Kurve but haven't heard back.  We did submit a case to IBM, but with the severity set 3, the response can take some time.  Appreciate your feedback and hope one of the newer versions is available for us to try.  

Kurve Support provided the following response and fixes: 

We've seen similar behavior with other clients after upgrading to Platform 5.0.3+, due to changes in the underlying IBM BusinessConnect API.

Minimal next step (stay on TR v1.1.25)

We have a platform‑specific fix pack for TRIRIGA Reporting 1.1.25, released in December 2025.

• Please search for TRIRIGAReporting_1.1.25_LA5.0.3-TIV-TAP-FP50in IBM Fix Central
• Download and OM/install the package.

Recommended next step (upgrade to TR v1.2.1)

Alternatively, we recommend upgrading to the latest TRIRIGA Advanced Reporting v1.2.1 feature pack, which includes this fix plus additional improvements. We understand this might involve a bit more preparation and exploration of the new features and UI modifications.

• Please search for TRIRIGAReporting_1.2.1_LA5.0.3-TIV-TAP-FP80 in IBM Fix Central
• Download and OM/install the package.

We have completed review and testing of both options:

• I was unable to find TRIRIGAReporting by searching IBM Fix Central.  I was able to see and download the files under the TRIRIGA Application Platform as platform fix packs 5.0.3.50 and 5.0.3.80.  
• I started with FP50.  The read me states this should only be applied to platform versions 5.0.3 and 5.0.4.  We have already upgrade to 5.0.5.  I still applied the fix pack and it appears to have corrected the issue.
  • There's no mention of this issue in the base platform fix pack read me files.  Someone might want to update the 5.0.5 and 5.0.6 read me content to include something about this.  I also don't remember seeing the 5.0.3.50 and 5.0.3.80 when I downloaded 5.0.5 several months ago (but that could be on me). 
• I then upgraded to FP80, which also appears to work.  Although, when running reports this FP includes a feature which pops up a window about 1.2.1 Migration completed with errors, and shows which columns are affected.  Most reports seem to work, but we need to do more testing because some reports returned no results (which may just be the report config). 
  • Note:  Normally, full version releases like 1.2 (or 1.2.1 if that's the base version) would be found in the IBM Software Catalog like 1.1.25 and prior versions.  Just an FYI, although I imagine with the transition to MREF, things may be different going forward.

Hope this is helpful and thanks to all for the support.  

------------------------------
Todd Allen
Solution Architect
Wipro
------------------------------