Reference Client (UA.-.NETStandard-master) is BadNotConnected

Question

I have a question that I already asked on the GitHub forum. Unfortunately I didn't get an answer there and I hope that you can help me here. If I do get an answer in the GitHub forum, I'll name it here. My GitHubPost can be found under the following link:

https://github.com/OPCFoundation/UA-.NETStandard/issues/1139

I will still copy the post from the GitHub forum here if the link no longer works at some point.

I downloaded the OPC UA standard project from github (https://github.com/OPCFoundation/UA-.NETStandard). I would like to use the Reference Client there to access a Beckhoff PLC (server). To do this, I opened the project in VS2017 and set the Reference Client as the startup project. Then I started the project with F5. The following window opened:

Reference_Client

If I now specify the IP address and the port of my PLC (as shown above) and then click on "Connect", the client sometimes establishes a connection to the PLC and sometimes I get the following error message:

Error_Message

In about 80% of the cases there is this error message and the client does not connect to the server. In about 20% of the cases a connection to the server is established and I can read and write variables from the server. I didn't change the program and it seems completely arbitrary when the connection can be established and when not. Has anyone ever had a similar problem?

Many thanks in advance.

UPDATE 1: More detailed error message

The following screenshot shows the details of the error message. I have estimated some parts of the storage path.

Detailed_Error_Message

Answer 1

Please add the exception details to your post, it would be helpful to see at which place the ServiceResultException is triggered.

Answer 2

Thanks again for the many answers. I have been able to narrow down the cause of the problem now. I found the tip in the Github forum that you should comment out all security mechanisms:

You modify your code private static void CheckCertificateDomain(ConfiguredEndpoint endpoint) to return true always, and add AutoAcceptUntrustedCertificates true into config of the client. This is just for developing and troubleshooting of course.

Source: Github tip

I did exactly that and then tried to connect again. I no longer receive an error message, but the operating window for OPC UA crashes. VS2017 itself does not crash, only the operating window in which the IP address can be entered and the connection can be established. When I record the network traffic with Wireshark during the crash, it can be seen that the connection (although the operating window has crashed) was successful. Data is exchanged between the client (VS2017) and the server (Beckhoff PLC).

My new approach is now to no longer use this operating window, but to write a new program. I would like to continue using the library I have used so far. The received and sent variables should then be displayed via the console.

Since this no longer has anything to do with my original question, I will make a new post for questions about this program if necessary and then add the link here.