On Ignition 8.0.17 and Windows 10 I have several working production lines all working normally except one of them out of the blue is recently getting this Java NoSuchAlgorithmException: (algorithm: Default, provider: SunjSSE, class: sun.security.ssl.SSLContext.... yada yada yada) when trying to launch a client application.
I renamed the C:\Program Files\Inductive Automation/Ignition folder but that did not solve the problem. Not sure what else to look at or why this happened all of a sudden.
Hello @wpmccormick,
Did you ever find a solution to this issue? I just had the same error at a client site this morning and I too am at a loss. Any insight is greatly appreciated.
Thanks.
Pretty much a non-issue with modern Ignition when using the java supplied with the client launcher.
So, old Ignition? And/or overridden java executable?
@pturmel it's 8.0.11, so yeah old Ignition. I have been trying to get the customer to upgrade and they have been dragging their feet. Looks like I have some more ammunition to make my case.
As for the java executable getting overwritten, I'm not sure at this point. The customer shut the client down over the weekend and when they restarted, they got the error. I will keep digging.
Thanks for the help!
You can always try clearing out the ~/.ignition folder on the client machine having issues and then try launching again.
@Kevin.Herron I will get the customer IT team to give that a shot.
Thanks!
I tell my clients that if they want to stay with an unsupported version of Ignition, they need to be prepared to roll back any OS updates they do, and then stop updating the OS if breakage continues.
That's obviously dangerous on networked systems (less dangerous if not Windows), so generally serves as a premium motivator.
I don't exactly recall which client/site this issue was at, but as others have suggested here, it was likely an issue with outdated client launcher.
On a side note, I may go look for other unanswered posts from last year and ask myself if I ever found a solution.