IIQ Console Connecting Error

D:\Program Files\Apache Software Foundation\Tomcat 9.0\webapps\identityiqdev\WEB-INF\bin>iiq console
Setting iiq.hostname to DCA-DEV-689-console
org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘systemStarter’ defined in class path resource [iiqBeans.xml]: Invocation of init method failed; nested exception is java.lang.RuntimeException: sailpoint.tools.GeneralException: could not extract ResultSet

we restored the prod db in our dev server and copied the identityiq folder and updated prop file

tried starting the tomcat and connecting to iiq console is failing with above error

Hi @Mani_AMAT

Could you please provide the following details?

  • OS version:
  • Java version:
  • IIQ version and patch level:
  • Database version:
  • JDBC Driver file name:
  • server.xml
  • identityiq.spt_database_version;

I have worked on a similar setup, and the above-mentioned details are crucial to understand the issue.

Thanks & Regards,
Pattabhi

1 Like

Hi @Mani_AMAT,

In my experience performing an upgrade from 7.0p6 to 8.4p2, we were in a similar situation where we were unable to connect to iiq console after restoring data from the Production to the Stage environment.
{ cross check the environment variable like java version, tomcat base version, path }

We have tried commands like iiq.bat console -u spadmin -p admin

The underlying issue was:

The OS version difference (2012 vs. 2022) was a major issue, along with other factors like the DB component (SQL Server 2016), JDBC driver files, iiq.properties, and server.xml file.

You can refer to my topic: Step-by-Step: Best Practices for IdentityIQ 7.1p6 to 8.4p2 Upgradation where I listed all the components key for a successful migration.

So, in your case, it could be one of the following:

  1. OS version difference or Database issue config issue.
  2. Driver file issue with respect to java version.
  3. Misconfiguration of iiq.properties or server.xml
  4. Corrupted deployed folder content during the restore.
  5. Possibly database default schema configuration.

I hope this will help you troubleshoot your iiq.bat console connectivity issue.

Thanks & Regards,
Pattabhi

Hi @pattabhi,

Please find the requested details below

  • OS version: 10.0.20348 N/A Build 20348
  • Java version: java version “17.0.12” 2024-07-16 LTS
  • IIQ version and patch level: 8.2 p1
  • Database version: 16.0.1000.6
  • JDBC Driver file name: mssql-jdbc-9.2.1.jre8.jar
  • server.xml
  • identityiq.spt_database_version; - 8.2-12

Hi @Mani_AMAT

OS: Windows Server 2022 & DB: MS SQL Server 2016 looks good aligned with my approach.

As per SailPoint Installation document of IdentityIQ 8.2, we need to use jdk 1.8(8) or JDK 11

So my recommendation is downgrade java from JDK 17 to JDK 11 and use following driver file.

mssql-jdbc-12.6.3.jre11.jar

(or) latest: mssql-jdbc-12.10.1.jre11.jar