Thank you.
There are two problems there:

1. You have some incorrect bindings.
2. We have a bug in the error handling, and basically have a "crash" instead of treating the invalid bindings properly.

Resolution:

Ad 1. How to resolve the incorrect bindings:
1.1 Right-click on the TextBox you are attempting to bind, and select the "Edit Live Bindings" command. A "Binding Collection Editor" dialog appears.
1.2. The "Bindings" list contains 5 bindings. The first one is empty ("null" in out terminology). This is the one that is causing the errors. Select it, and then press the "Remove" button.
1.3. Optionally, remove other bindings that seem to be duplicate (but they are not causing the error you have reported).
1.4. Press "OK" to close the Binding Collection Editor.

Ad 2. The bug in our error handling will be fixed in the upcoming QuickOPC version (2017.2); but if you do as described above, it should go away anyway.

I hope this helps.
Best regards

Hello,
this is weird, but it appears to be something rather on our side.

Do you get the error right at the start, or when you are closing the application?

Can you please send me the project again, and, if possible, more details to the error(s) - e.g., is it possible to obtain a call stack? (this is for case if we were not able to reproduce it with you project).

Thank you

There seems to be several misunderstandings going on.

Browsing the network for computers is done using Windows functions. It is not related to OPC UA. If you get an error at the moment you try to expand a "Network" node or its domain sub-node, then it is a Windows network browsing returning the error. Similarly, even if you know the host where the OPC UA server resides, browsing for OPC UA servers on that computer is (usually, but not always) done by a separate OPC UA server, called LDS (Local Discovery Server). So in the end, you can have a perfectly functioning OPC UA server that you connect to, but if the LDS does not work, it won't be possible to discover it. But

The above, however, is just an explanation and may not have to do with your issue.

I tried to play with the Point Editor in a similar situation you described (when browsing for servers does not work), and entering the server manually. And, I have realized one case in which I can get precisely the same error as you.

The *proper* way to enter a server URL, if you cannot browse for it, is to 1. select the "Any Host" node, and then insert a node with the URL (such as "opc.tcp://192.168.0.1:4840") of your server (in the dialog, this is denoted as inserting "OPC-UA Endpoint Node". This works for me.

The *improper* way to do this is to try to insert a "Host" node. For example, if you select the root node ("Hosts"), and then manually insert a node and type in "opc.tcp://192.168.0.1:4840", you will end up with "host" node that has a name of "opc.tcp://192.168.0.1:4840". That's not right (the host name should be just "192.168.0.1", in this case). If I do this improper procedure, I end up with precisely the same error as you (The requested name is valid, but no data of the requested type was found).

Can you verify whether you have not made this mistake, buy repeating the procedure from the start, in the proper way?

I am sorry but I do not understand your answer.

The Live Binding project you have sent me *has* the slash at the end.

I found a small difference between the two projects. I am not sure if it causing the problem, but it can. Can you please test that; if it helps, I would then be interested in knowing how the difference has actually got there in the first place.

The difference is in the trailing forward slash in the server URL. The project that works OK uses

whereas the project that reports "System.Net.Sockets.SocketException: Der angeforderte Name ist gültig, es wurden jedoch keine Daten des angeforderten Typs gefunden" uses

Can you please check whether this is not the cause.

In the Live Binding project, you can edit the URL directly in the Form1.Designer.cs file.

Thank you, and best regards