Who is this article for?

Users who are having issues with accessing Classic via the executable application.

Local Admin permissions are required for some steps.

There are several common issues that you may experience when trying to launch Classic through the executable application. This guide will show you how to resolve them.

1. ‘Failed to launch JVM’ or ‘Error invoking method’ error

This means the application is failing to access the Ideagen Risk Management AWS servers due to one of the following:

• Outgoing access is blocked or restricted on your network.  
• Incoming access is blocked or restricted on your network.
• Direct port access is blocked or restricted on your network.

To troubleshoot access issues: 

1. Check manual access to Ideagen Risk Management resources in AWS.
   You can do this by attempting to access the splash-screen graphic hosted on AWS.
2. Check to see if unauthenticated access is allowed.
   This will need to be checked using a network trace or by looking in your network logs. See if traffic going to an AWS IP within the ‘eu-west-2’ or 'us-east-2' region is being dropped.  
3. Check to see if direct port traffic on Port 443 is being dropped.
   Traffic from this port should be going to an AWS IP within the ‘eu-west-2’ or 'us-east-2' region.  

To resolve direct port access issues, create a port forwarding rule to point traffic from Port 443 to the correct gateway.

To resolve proxy server blocking issues, try using the system set proxy:

1. Open ‘application directory’\Pentana Risk\app\Pentana Performance.cfg in a text editor.
2. Add -Djava.net.useSystemProxies=true under [JVMOptions].
3. Save and try to launch the application again. 

If this doesn't resolve the problem, try manually configuring the proxy settings in the application:

1. Open ‘application directory’\Pentana Risk\app\Pentana Performance.cfg in a text editor.
2. Remove any edits made for the previous solution.
3. Add the following lines with your proxy settings replacing the null values:  
   • Dhttps.proxyHost=0.0.0.0  
   • Dhttps.proxyPort=0.0.0.0
4. Save and try to launch the application.

2. ‘java.io.FileNotFoundException’ error

This means the User doesn’t have write permission in the installation directory and is not able to update the application files in this directory following a version update/release.

By default, the directories are: 

• Local admin - C:\Program Files (x86)\Pentana Risk\app 
• Local user - C:\Users\user.name\AppData\Local\VirtualStore\Program Files (x86)\Ideagen Risk Management\app 
• Virtual Machine - Virtual store

To resolve this error, ensure the User has the correct permissions to write in the above directories.

3. ‘java.lang.ClassNotFoundException' error

A Windows 10 update released in August-September 2019 appears to temporarily break some users' Classic .exe.

This seems to happen when Windows is installing the update in the background, making the application show the following error:

java.lang.ClassNotFoundException: com.covalent.client.bootstrap.CovalentBootstrap
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at com.covalent.executable.ExecutableBootstrapper.main(ExecutableBootstrapper.java:180)

There is likely a registry value that is changed during this background install.

To resolve this error, make sure you have applied all the latest system updates.

In addition to this, the .exe package may need uninstalling and reinstalling on the machine. When uninstalling the .exe package, ensure all the files have been removed from the directories before reinstalling it.

By default the directories are:

• Admin (local) - C:\Program Files (x86)\Pentana Risk\app 
• User (local) - C:\Users\user.name\AppData\Local\VirtualStore\Program Files (x86)\Ideagen Risk Management\app 
• Virtual Machine - Virtual store

If required, we can resupply the Classic .exe download link to you. If you continue to experience issues, please contact our Support Team.