March 30, 2018
When trying to connect to the server the program seems stuck in a loop with no sign of any error messages.
I enter the server URL, it then prompts me to ‘Select Server’ – the only server available is the one I wish to connect to.
Next, when selecting the Security Settings, (None/None, which are allowed by the server, and have been used to successfully connect to the server with other OPC UA clients) after pressing OK, the program waits a few seconds before again prompting me to ‘Select Server’. It then prompts me for Security Settings, then to Select Server, and repeats this process. There is no visible error displayed.
Just to note I am also using Anonymous login, which again I have been able to connect with using other clients problem-free.
It doesn’t get to the certificate acceptance stage, so shouldn’t be a trust issue (there are also no Rejected certificates in either server/client certificate folders)
Please could you recommend how I can find the problem, or how I can solve it?
Thank you in advance for your time and any advice you can provide!
April 17, 2013
This loop situation means that the client application experiences an error when connecting to the server.
What version of the Prosys OPC UA Client are you using? The version information is available from menu “Help”->”About”. We released version 3.0.0 just last week and this new version handles connections to certain servers in a more robust way.
Furthermore, could you mention what is the server application that you’re connecting to?
March 30, 2018
Hi, thanks for your response!
Unfortunately I do not see any error notification in the Client program. It’s a OPC UA Server that I’m trying to connect to, and I have tried looking into the server logs for errors but nothing appeared abnormal.
The Prosys Client product version I’m using is: v3.0.0-256, SDK: 3.0.0-454, stack: v1.3.343-167.
Thank you for your time
March 30, 2018
ust wanted to close this thread/issue:
I managed to connect the to the server, the problem was most likely that the url/urn was not matching or not being resolved correctly. For example, I entered the URL ‘opc.tcp://chloe:…’ whereas the urn was ‘urn:localhost:…’. After ensuring they matched (i.e. ‘urn:chloe:…’) it connected okay.
It was not an issue with this client software at all – anyone experiencing a similar problem could check the server configuration to ensure everything is okay there.
I also wanted to thank Heikki for the help in this thread, as well as in the email discussion – brilliant support, really appreciated! ðŸ™‚
Most Users Ever Online: 518
Currently Browsing this Page:
Francesco Zambon: 78
rocket science: 73
Guest Posters: 0
Newest Members:anitas, fakenatty, Negansaf, rheakempton93, JPasterkamp, mattiwenell, KevinGainy, jamiescooper, lonmackellar61, charleneeller1
Moderators: Jouni Aro: 1002, Otso Palonen: 32, Tuomas Hiltunen: 5, Pyry: 1, Petri: 0, Bjarne BostrÃ¶m: 954, Heikki Tahvanainen: 402, Jukka Asikainen: 1, moldzh08: 0, Jimmy Ni: 26, Teppo Uimonen: 21, Markus Johansson: 42, Niklas Nurminen: 0, Matti Siponen: 297, Lusetti: 0, Ari-Pekka Soikkeli: 5
Administrators: admin: 1