Upgrade 8.3 to 8.4

IdentityIQ (IIQ) IIQ Discussion and Questions
1

Which IIQ version are you inquiring about?

Version 8.4

Share all details related to your problem, including any error messages you may have received.

I am upgrading 8.2p2 to 8.3 then 8.4

Upgraded 8.2p2 to 8.3 upgraded completed

But when I imported sp.init-custom.xml file

I am not able to open entitlement catalog page

Like the entitlement catalog page is opening and when I try to open any entitlement .it returning page not founded
405 code it is showing

2

Hi @sridevi5895,

Can you take a look at the sailpoint log file (configured in log4j2.properties) and paste here the error from that log file?

Thanks,

– Remold

3

in log4j i didnt see any error particualrly for this entitlementcatalog page but let me copy logs here

2024-03-27T02:35:37,960 ERROR main sailpoint.server.Servicer:512 - Unable to install service: TaskLauncher
sailpoint.tools.GeneralException: sailpoint.services.standard.tasklauncher.TaskLauncherService
at sailpoint.server.DynamicLoader.getClass(DynamicLoader.java:191) ~[identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
at sailpoint.server.DynamicLoader.instantiate(DynamicLoader.java:205) ~[identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
at sailpoint.server.Servicer.instantiateService(Servicer.java:605) ~[identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
at sailpoint.server.Servicer.install(Servicer.java:493) ~[identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
at sailpoint.server.Servicer.configure(Servicer.java:334) ~[identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
at sailpoint.server.Servicer.start(Servicer.java:315) ~[identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
at sailpoint.server.Environment.start(Environment.java:492) ~[identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
at sailpoint.server.SystemStarter.springInit(SystemStarter.java:59) ~[identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:?]
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:?]
at java.lang.reflect.Method.invoke(Unknown Source) ~[?:?]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeCustomInitMethod(AbstractAutowireCapableBeanFactory.java:1925) ~[spring-beans-5.2.24.RELEASE.jar:5.2.24.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1867) ~[spring-beans-5.2.24.RELEASE.jar:5.2.24.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1795) ~[spring-beans-5.2.24.RELEASE.jar:5.2.24.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:594) ~[spring-beans-5.2.24.RELEASE.jar:5.2.24.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:516) ~[spring-beans-5.2.24.RELEASE.jar:5.2.24.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:324) ~[spring-beans-5.2.24.RELEASE.jar:5.2.24.RELEASE]
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234) [spring-beans-5.2.24.RELEASE.jar:5.2.24.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:322) [spring-beans-5.2.24.RELEASE.jar:5.2.24.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202) [spring-beans-5.2.24.RELEASE.jar:5.2.24.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:311) [spring-beans-5.2.24.RELEASE.jar:5.2.24.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202) [spring-beans-5.2.24.RELEASE.jar:5.2.24.RELEASE]
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:897) [spring-beans-5.2.24.RELEASE.jar:5.2.24.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:879) [spring-context-5.2.24.RELEASE.jar:5.2.24.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:551) [spring-context-5.2.24.RELEASE.jar:5.2.24.RELEASE]
at org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:144) [spring-context-5.2.24.RELEASE.jar:5.2.24.RELEASE]
at org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:85) [spring-context-5.2.24.RELEASE.jar:5.2.24.RELEASE]
at sailpoint.spring.SpringStarter.start(SpringStarter.java:333) [identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
at sailpoint.server.upgrade.Upgrader.initializeSpring(Upgrader.java:1297) [identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
at sailpoint.server.upgrade.Upgrader.initializeHibernateSpring(Upgrader.java:1330) [identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
at sailpoint.server.upgrade.Upgrader.executeHibernateCommands(Upgrader.java:1230) [identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
at sailpoint.server.upgrade.Upgrader.execute(Upgrader.java:1124) [identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
at sailpoint.server.upgrade.Upgrader.main(Upgrader.java:643) [identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:?]
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:?]
at java.lang.reflect.Method.invoke(Unknown Source) ~[?:?]
at sailpoint.launch.Launcher.main(Launcher.java:250) [identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
Caused by: java.lang.ClassNotFoundException: sailpoint.services.standard.tasklauncher.TaskLauncherService
at jdk.internal.loader.BuiltinClassLoader.loadClass(Unknown Source) ~[?:?]
at jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(Unknown Source) ~[?:?]
at java.lang.ClassLoader.loadClass(Unknown Source) ~[?:?]
at sailpoint.launch.WebInfClassLoader.loadClass(WebInfClassLoader.java:237) ~[identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
at java.lang.ClassLoader.loadClass(Unknown Source) ~[?:?]
at java.lang.Class.forName0(Native Method) ~[?:?]
at java.lang.Class.forName(Unknown Source) ~[?:?]
at sailpoint.server.DynamicLoader.loadRule(DynamicLoader.java:254) ~[identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
at sailpoint.server.DynamicLoader.classForName(DynamicLoader.java:158) ~[identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
at sailpoint.server.DynamicLoader.getClass(DynamicLoader.java:188) ~[identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
… 38 more

4

Assuming you are on Linux, I do suggest to check the permissions on the application server side as a starting point. Check the relations between the user which this application server is running and the new files added during the upgrade.

5

HI Gentjan Kocaqi,

i am not in linux server ,the server there in windows server

6

How to chekc this ,can you sujjest me
—>I do suggest to check the permissions on the application server side as a starting point

7

Actually it will be great to have the logs generated during the upgrade. Also, from your initial post seems the issue occur once the upgraded to iiq8.3 is done but from your logs I do see traces of iiq8.4. What are you exactly troubleshooting atm/which step? Are you able to reproduce/redo it and share more logs? In these cases collecting and checking logs is crucial for troubleshooting in my opinion.

8

Hi @gentjan_kocaqi,

We did upgraded from 8.2P2 to 8.3 and it was successful and we don’t see any errors. After that we upgraded to 8.4 and the upgrade completed with no errors (no errors in the upgrade log). After that we import our customizations using sp.init-custom.xml file. After importing when we try to edit any entitlement we are getting the above error in SailPoint log file.

9

Any red flags during the sp.init-custom.xml import?

10

No red flags during sp.init-custom.xml import

11

With the info I got from you, I will suggest to revert back the upgrade to iiq8.3 and try again to perform iiq8.3 to iiq84. And try to collect as much logs as you can while you do so.

What you’ve provided above is related to another issue and seems something did not go as expected. Check these:

2024-03-27T02:35:37,960 ERROR main sailpoint.server.Servicer:512 - Unable to install service: TaskLauncher

Caused by: java.lang.ClassNotFoundException: sailpoint.services.standard.tasklauncher.TaskLauncherService

But maybe someone else do have other ideas here.

Note: regarding the file permissions, you might check with the windows admins people. Are you using Tomcat as application server? If so, check ‘/webapps/identityiq’ folder.

12

Can you elaborate a bit on your environment?
What application server are you using?
Are you using a supported JRE ? (IIQ 8.4 supports JDK11 and JKD17, not JDK8)
Is there any component in front of your application server, like a proxy (ie Nginx)

Is there anything in the application server log file (for tomcat: ..\logs\catalina.out and/or ..\logs\stderr.log ?

Please also take a look at the following document for the changes between each IIQ version (8.4 is not yet added :frowning: )
IdentityIQ Upgrade Guide - New Features by Version

– Remold

13

I don’t think this is an OOB sailpoint class (as in OOB for a vanilla IIQ install). It looks like it may have been part of an additional package that was installed, then removed during the upgrade.

Do you have a pre-upgrade backup of your lib and lib-connectors folders?

If you over-wrote those, you may have deleted a class your instance was referencing. I would try comparing what’s in your pre-upgrade lib folder to your post-upgrade lib folders and see if you can find it.

You can try decompiling jar files to find the class

14

Based on your description, it appears that you aren’t using a correct upgrade process. I do upgrades for clients all the time. Do you have a written plan you can share? I can review a document but I can’t take time to walk through it with you unless you are a client of mine.

15

Can you also look into the sp.init-custom.xml and see if you are importing any ManagedAttribute ?

If so, can you remove the ManagedAttribute one-by-one using debug and check after each if the Entitlement Catalog page is working.

– Remold

16

An other place to look for errors is the Developer Console in the browser.

In Google Chrome, open the Chrome Menu in the upper-right-hand corner of the browser window and select More Tools > Developer Tools . You can also use Option + ⌘ + J (on macOS), or Shift + CTRL + J (on Windows/Linux).
You may have to select the Console tab.

– Remold