Hello.

this error is generated on the client side, but indicates a problem in the server.

To help you understand what is happening, here is how the checking works. You need to understand that QuickOPC calls code in OPC Foundation UA stack, and both parts are involved in the checks.

1. OPC Foundation UA stack validates the server nonce only if security is actually in use (security policy URI does not correspond to "None" policy), AND there is non-anonymous user identity associated with the session.
2. If the conditions above are fulfilled, the OPC Foundation UA stack checks that the server nonce has at least the minimum length (default is 32), and that it is not all zeros. If there is a problem, it throws the error you are observing.
3. When it gets here, the OPC Foundation UA stack checks that the server nonce is not the same as previous one provided by the same server. If there is a problem, it would throw an BadNonceInvalid error too, but with a text saying "Server nonce is equal with previously returned nonce.".
4. QuickOPC later checks the server nonce again, but it does it regardless of the security policy URI or the usage of anonymous user identity. It does so because the OPC Foundation compliance test requires this behavior from compliant clients. The checks done in the QuickOPC layer can be turned off by the settings you have mentioned. Error codes/messages given by the QuickOPC layer are very different (they do *not* have the ServiceResult with BadNonceInvalid in them).

As you can see, in your case the problem is detected in the OPC UA stack, and therefore there is no setting to turn it off.

This has to be fixed by the server vendor.

Best regards