IIQ not starting after adding jar

Administration & Troubleshooting
, , ,
1

Hi All ,

My IIQ Dev env was working earlier , I had moved few jar intoa java/lib/security folder while the service was running . I had assumed the service was stopped . Anyhow , i noticed this and immediately stopped the service post adding of the files. When I restarted , IIQ is not restarting .Then i reverted to before , undoing all changes ,still same issue

I have tried iiq console command , and i can see error :  login failed to database .

Please note I didnt change anything in iiq.properties file . so user and password to connect to sqlserver db is same .

Attatching the catalina logs and iiq console logs for reference /

I have tried to use sql server management studio to connect to the db i am getting the same login failed error.This is quite peculiar , as it was working prior. Any pointers on why getting a login issue as it seems quite unrealted ?

Can the system be restored anyhow ? I have tomcat backup but i dont have XML exporter for XML backup . all the Application and rule XMLs .. is there anyway to fetch them from spt database directly in sql server as this is quite important .

Could it be a certificate issue , but i had not  modified cacerts file

Will creating a new tomcat service help by pointing it to the old database ?

Any help or pointers is much appreciated .

@PaulMeyer

@soswain_resmed

@shyamgarikapudi

@Tyler_Harman

@wwinterstein

@arthur_altman

@cyates

@joeyhertling2017

@vishal_kejriwal

iiq console.log (1.79 KB)
catalina2.log (14.5 KB)

2

As per the console log, it seems like an issue with the IIQ schema. Please check the schema version in spt_database_version table.

For more details, please have a look into the below topic.
https://community.sailpoint.com/t5/IdentityIQ-Forum/i-am-not-able-to-login-to-iiq-it-gives-errors-as-Exception/m-p/130372#M112311

3

Thank you  @soswain_resmed  for the reply , it was indeed a database issue , just unfortunate that the timing coincided with adding of the jars . DB had been migrated to a new server . After the new server details were entered , and connecting to DB through SQL Server Management Studio , Sailpoint was up and running