Great! I am glad it works.

And, it is useful to know that the missing permissions may cause this error as well. I will make a note of it...

Best regards

There are some used internally by Microsoft - which is a pain, because it's not quite clear which they are.

In the issue that you have identified as being similar but not identical (different error message), we point out a specific directory that had permission problems. Even though the error message is different, I suggest checking that directory is well. It is described here: kb.opclabs.com/Error_%22The_specified_network_password_is_not_correct.%22

I would also recommend that they make a back up copy of the certificate store directories, clear all files from them, and retest. Sometimes it helps.

Best regards

Hello.

Yes, it's the LocalSystem account, that looks good.

Regards

Hello.

I received the certificate directory, thank you. That, by itself, unfortunately gave me no more insight.

However, the fact that the behavior is correct with "normal" user account is, I believe, and as you do as well, a clear indication that this is a permissions problem. So I think what needs to follow is a thorough check of the file/directory permission on the certificate directory, versus the account they want to run under.

Question: Were they really running the service under LocalSystem account? Wasn't that LocalService account? (since the names are similar, people sometimes confuse them). LocalSystem has quite high privileges; LocalService (or NetworkService) has much lower privileges. So, it would be somewhat surprising if LocalSystem did not work, but not that surprising if they were using LocalService.

For a nice confusion, when checking the directory permissions, if they are running under LocalSystem, the "group" for that appears as SYSTEM. So, the permissions on C:\ProgramData\OPC Foundation and everything below should include SYSTEM where in the Permissions... box, all checkboxes under "Allow" are checked (maybe except for "Special permissions").

Regards