Getting the same problem here, after upgrading Ignition version from 8.0.15 to 8.0.16 (b2020082513)
Unfortunately I followed Kevin suggestion with no success.
Very urgent: cannot work any longer!!
Same error here on 8.0.16.
Is there a preventative measure we can take to ensure this doesn’t happen again until there is a fix?
Like maybe always deleting the jre-win folder if it exists?
Will it re-create itself and cause the issue again, or does deleting the folder fix the problem permanently for that one particular user’s profile (directory)?
Sorry for all of the questions–we have deployed to a lot of computers with a lot of users and we’re trying to be proactive.
Deleting the jre-win dir if it exists before launching a client would help if there is a prior failure. The JRE is only dowloaded once per version so after it succeeds there should be no issue from there on out so simply launching a client or designer on a machine should allow you to get a cached runtime (assuming you don’t hit this issue, which the previously mentioned workaround should fix)
It should also be noted that a fix for this is currently submitted for testing and should make it into 8.1.1 and be included in that release (and subsequently, the nightly build in the coming days once it’s merged into the codebase)
Ok, that makes sense. However now I’m wondering about something else–it appears the JRE (either 11.0.7 or jre-win folder) exists in every users’ .ignition/cache/resources/runtimes folder in Windows. I thought the launcher would use the /jre folder next to the visionclientlauncher.exe file? But now I’m wondering if it uses the JRE in each users’ .ignition/cache/resources/runtimes folder? Some of our computers will have 15+ people logging into them would could mean 15+ copies of the JRE, right?
Yes this is the cache directory. Not only is the JRE stored there, but also all of the jars required for launching etc.
You could place a redirect.txt file in that directory to tell the launchers etc to use a different directory if you want to share it across multiple users. There is a post about it here
It should be noted that the configuration of the launcher would be there as well meaning all users’ launchers would rely on the same configuration which may or may not be desired.
Just tried the redirect.txt file and that’s awesome! This should be much easier to manage if we ever have to delete/rename some contents of the cache. And it gives us the flexibility for “certain” users to have custom vision-client-launcher.json files by excluding the redirect.txt files in those users’ .ignition directory. And it reduces users’ Profile folder size.
