Hi,
I keep getting the following message when I start up ProM 1.2:
Exception in thread "main" java.lang.Exception: Cannot find release package defined in ProM.ini file: LitePackages. Continuing to load ProM.
at org.processmining.contexts.uitopia.UI.main(UI.java:66)
Is there something I can configure? I'm loading the software from a PC at work but I do have admin rights so it shouldn't have too many problems.
Any ideas?
Regards
Bobnottm
Comments
Thank you for your reply. The above has all been done but the packages are still not loading on initial start-up.
I've spoken to IT at work and there's no software or firewall that should block the packages. However, when I click the default link the following message appears:
"A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
So it could be something your end? I don't know.
On my home PC I had to extend some memory through settings but can't find the link anymore. Maybe it's related to that, I'm at a loss for options.
Thanks
Stuart
The URL you mention shows the problem. The server prom.win.tue.nl ceased to exist years ago. Which version of ProM are you actually using? Given the URL, I guess it should be a Nightly Build, but then an old one.
Please change the line with the PACKAGE_URL in the ProM.ini file to the following:
This will cause ProM to use the package repository for the Nightly Build, which contains the most recent releases of the packages.
Kind regards,
Eric.
That URL is different to the one above. It still doesn't load the packages.
Looks like I'll be doing process mining in the NHS off of my home lap top.
Regards
Stuart
The following is now showing for most, if not all, packages in the command line. Any ideas?
Thanks for any help / ideas!
This is not an error message. When starting up, ProM needs to create an inventory of which plug-ins are available. For this reason, when started for the first time, ProM needs to scan all installed jars for plug-ins. To speed up this phase in later runs, this information is cached in the Windows registry (on WIndows machines). If found in the cache, ProM will skip scanning the jar file, which is shown in the output.
If you experience problems with plug-ins not being available although the corresponding package is installed, then please have a look at the section "Installing packages" on http://www.promtools.org/doku.php?id=troubleshooting:start. This also shows how you can removed the cached data. Doing so, will cause ProM to scan all jar files again during the next run.
Kind regards,
Eric.