Ignition Gateway 7.7.4 faults

I’ve had this happen a few times before, just went in, deleted the file out of the temp folder, restarted gateway and it ran. Not working this time
“”“INFO [ModuleHook ] [15:15:48,430]: JNI Library: C:\Windows\TEMP\jniwrap-3.8.38051489701252876777.Build.3.8.31017514210\jniwrap64.dll
INFO | jvm 1 | 2021/02/15 15:15:48 | ERROR [SRContext ] [15:15:48,569]: Error during context startup.
INFO | jvm 1 | 2021/02/15 15:15:48 | java.lang.ExceptionInInitializerError
INFO | jvm 1 | 2021/02/15 15:15:48 | at com.jniwrapper.win32.system.Kernel32.isUnicode(Kernel32.java:77)
INFO | jvm 1 | 2021/02/15 15:15:48 | at com.jniwrapper.win32.FunctionName.(FunctionName.java:24)
INFO | jvm 1 | 2021/02/15 15:15:48 | at com.jniwrapper.win32.MessageLoopThread.(MessageLoopThread.java:24)
INFO | jvm 1 | 2021/02/15 15:15:48 | at com.inductiveautomation.opccom.ModuleHook.setup(ModuleHook.java:176)
INFO | jvm 1 | 2021/02/15 15:15:48 | at com.inductiveautomation.ignition.gateway.modules.ModuleManagerImpl$LoadedModule.setup(ModuleManagerImpl.java:2187)
INFO | jvm 1 | 2021/02/15 15:15:48 | at com.inductiveautomation.ignition.gateway.modules.ModuleManagerImpl.setup(ModuleManagerImpl.java:263)
INFO | jvm 1 | 2021/02/15 15:15:48 | at com.inductiveautomation.ignition.gateway.SRContext.startupInternal(SRContext.java:1185)
INFO | jvm 1 | 2021/02/15 15:15:48 | at com.inductiveautomation.ignition.gateway.redundancy.RedundancyManagerImpl.startup(RedundancyManagerImpl.java:191)
INFO | jvm 1 | 2021/02/15 15:15:48 | at com.inductiveautomation.ignition.gateway.SRContext.asyncInit(SRContext.java:932)
INFO | jvm 1 | 2021/02/15 15:15:48 | at com.inductiveautomation.ignition.gateway.SRContext.access$200(SRContext.java:255)
INFO | jvm 1 | 2021/02/15 15:15:48 | at com.inductiveautomation.ignition.gateway.SRContext$2.run(SRContext.java:666)
INFO | jvm 1 | 2021/02/15 15:15:48 | at com.inductiveautomation.ignition.common.execution.impl.BasicExecutionEngine$ThrowableCatchingRunnable.run(BasicExecutionEngine.java:537)
INFO | jvm 1 | 2021/02/15 15:15:48 | at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
INFO | jvm 1 | 2021/02/15 15:15:48 | at java.util.concurrent.FutureTask.run(Unknown Source)
INFO | jvm 1 | 2021/02/15 15:15:48 | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)
INFO | jvm 1 | 2021/02/15 15:15:48 | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
INFO | jvm 1 | 2021/02/15 15:15:48 | at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
INFO | jvm 1 | 2021/02/15 15:15:48 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
INFO | jvm 1 | 2021/02/15 15:15:48 | at java.lang.Thread.run(Unknown Source)
INFO | jvm 1 | 2021/02/15 15:15:48 | Caused by: com.jniwrapper.JNIWrapperException: java.io.IOException: Access is denied
INFO | jvm 1 | 2021/02/15 15:15:48 | Caused by: java.io.IOException: Access is denied
INFO | jvm 1 | 2021/02/15 15:15:48 | INFO [SRContext ] [15:15:48,573]: Ignition[”/main", state=STARTING] ContextState = FAULTED"""

Java version is 1.8.0_60-b27…this gateway has been running for years with no problems, other than the occasional glitch with the jni file issue. Anything I’m missing, kinda been staring at the trees for a bit on this and maybe I’m missing something.

That’s as much information as Java is giving us. From the rest of the stack trace, it’s trying to load COM related native code. Did anyone recently install any other COM servers or clients? Update OPC core components? Have you restarted the server itself (not just Ignition) since this issue occurred? Are you in contact with our support department yet?

Nothing has been installed or upgraded. I have restarted the computer twice already, and checked for any jni files in the temp directory (happened before and that cured it). I created a ticket yesterday, but haven’t had a response yet.

If you didn’t call, call support on the phone. Email tickets default to low priority.

Not exactly true anymore (as I understand it, anyways):

I stand corrected. Very cool, and much appreciated improvement to support.

Restarted the computer 2 more times, it took off and ran. It’s running currently, but would will still talk to Support to see what happened. It doesn’t leave me with a warm, fuzzy feeling. This is the only gateway I’ve ever had an issue like this with, out of the many I’ve implemented.