After installing 8.1.5 I’m seeing this when opening vision client or designer.
Please advise.
Thanks,
Nick
I managed to fix this by deleting the “cache” file in the “.igntion” folder. After that both designer and client launchers worked again.
9 Likes
When this happens deleting the runtime folder should work (runtimes/11.0.10 or whatever the version is).
We’re aware of this issue but I’m not sure there’s any definitive cause or fix yet. It only happens to Windows users and may have something to do with AV software interfering when the runtime gets unzipped.
2 Likes
@Kevin.Herron We are still seeing this behavior reported from the field a few times per week.
FYI It just happened to me, just reporting in with some info in case it helps. Running Maker 8.1.18 at home, was fine yesterday. Then logged in from a different computer at work (through the firewall port) to check something, and I got this message. Both computers running Windows 10. I’m not sure I have yet run an 8.1.15 version at work. I deleted runtimes/11.0.15 and it was fine
Where can I locate runtimes/11.0.15 to delete them?
1 Like
See path in screenshot in initial post and change username to the username you are running under, something like this, substituting version number in your error message for ##.#.## below:
C:\Users\YOUR_USERNAME\.ignition\cache\resources\runtimes\##.#.##
3 Likes
Do you delete the entire file to fix this issue?
1 Like
Delete the whole ##.#.## folder:
3 Likes
Although a year past by, I got the similar error, but initially I got another error first during the runtime unpackaging process. This also happened after deleting the 11.0.xx folder and running it again.
So, just for addition reason and making the topics as complete as possible:
In my situation it happened to be that the runtime.zip wasn't unpacked completely from Temp to the 11.0.xx folder.
I unpacked it myself and copied al folders into the 11.0.xx folder. Problem solved.
We fixed this error by using perspective 
1 Like
Three years later, issue still occurs and deleting runtime files is still a solution.
Thanks nick also have worked for me
When the designer fails to launch, you usually have to look in the launcher's log file to obtain the actual designer java execution attempt's command line, and run that in a terminal. Running in a terminal shows all of that attempt's debugging information, which you would share here if it doesn't indicate a problem you know how to fix.
I need to specify the problem. I can open Ignition Designer but when I try to open any of the designers(launch them), I have this issue. Here is a screenshot.
Also I want to specify that name of my windows user typed in russian, maybe there is problem with russian letters?
Copy and paste the long command on the line the starts with "Starting Java with the following parameters: " and paste that into a command prompt and run it.