Students, professors, and faculty members: now is the time! Download the new ARIS 9.8!
Just one click on Product Info & Downloads and you´ll find all our free ARIS 9.8 offerings, including the free ARIS Education Package (for Faculty only) ready for download.
Please log in or register to have access to the world of business process analysis tools!
In the following post of Josèphe Blondaut, you´ll find an introduction about ARIS 9.8 highlights and features enhancements. If you want to still use your currently installed ARIS 9.7, no action is required.
Kind regards,
Your University Relations Team
Hello Christiane,
I have installed ARIS 9.8 for education and research. It worked all fine at first.
But today, after having booted the computer, I get this message when I try to start ARIS 9.8:
"Unable to find a Java Runtime Environment in the specified directory. Please
check the value of 'jvmPath' in launcher.cfg and try again."
How to solve this issue?
Regards
Chris
Hi Chris,
in the path "<aris client installation path>\client\config", there is a file named "launcher.cfg", make sure this file was not edited. Normally, it containes a line:
jvmPath="./jre"
This means, the jre is located here:
<aris client installation path>\ARIS9.7\client\jre
Make sure, that in this location, the jre is placed.
Bye,
Frank
Hi Frank,
I installed ARIS 9.8 just a few days ago. It worked fine on the first day. I have not changed the installation. The launcher.cfg has not been edited. There is a lot of files and folders in C:\SoftwareAG\ARIS9.8\client\jre - look at the screenshots I have attached. What else do I need to place in this location?
Chris
Hi,
1.) the javaw.exe should not be needed, actually. But normally it is there, which is strange. Somehow, your directory was modified.
2.) check the existance of the dll in your path like below (it is 9.7 in the screenshot, but that should not be a difference.
Bye,
Frank
Hi,
well, I cannot say what the JRE update considers to be necessary, but I would not think so. Maybe we should have an eye on that... if that happens again, we'd need to check what happened previously on your machine, e.g. an update of the JRE or something else. We haven't had this effect before. However, glad that it's working again.
Bye,
Frank