Ignition OPC UA Server faulted after VM migration to new ESXi cluster

Ignition
1

We migrated our Ignition server VM from an old ESXi cluster to a new one today and when we powered the server back on after the migration, the Ignition OPC UA Server is in a faulted state.

We have migrated other VMs to the new cluster and they have been working fine for a few weeks. We didn't change any settings on the Ignition server before/after the migration and everything was working correctly before the migration.

We are mainly seeing two error messages:

**UaServiceFaultException: status=Bad_UserAccessDenied, message=User does not have permission to perform the requested operation.**
**	at org.eclipse.milo.opcua.stack.client.UaStackClient.lambda$deliverResponse$5(UaStackClient.java:337)**
**	at org.eclipse.milo.opcua.stack.core.util.ExecutionQueue$Task.run(ExecutionQueue.java:119)**
**	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)**
**	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)**
**	at java.base/java.lang.Thread.run(Unknown Source)**

and

**UaServiceFaultException: status=Bad_TooManySessions, message=The server has reached its maximum number of sessions.**
**	at org.eclipse.milo.opcua.stack.client.UaStackClient.lambda$deliverResponse$5(UaStackClient.java:337)**
**	at org.eclipse.milo.opcua.stack.core.util.ExecutionQueue$Task.run(ExecutionQueue.java:119)**
**	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)**
**	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)**
**	at java.base/java.lang.Thread.run(Unknown Source)**

I have checked that the OPC UA module is running and activated (restarted it just to see if that helped) and no user information was changed.

Not sure how to proceed. Anyone have any ideas?

2

Hello,

Has anything changed with the opc ua user group?

Have a look at this.

Thanks,

Frank