Log In
Register
Forum
Topic RSS
16:36, EEST
May 24, 2016
Offline
Hi,
I have a ProSys OPC UA Server running which I wrote with help of the server tutorial with version 2.2.0-552 (Java). It’s close to the SampleConsoleServer.bat
When I access the server with UAExpert or a Matlab Script, I have no problems. But when I use my Labview OPCUA-client, it does not work. I get the following response after connecting:
LabVIEW: (Hex 0xFFFA8EF2) The nonce does not appear to be a random value or is not correct in length.
Can somebody help me out here?
Thanks,
Fabian
10:03, EEST
April 17, 2013
Offline
Hello,
Based on this information, this sounds like a client side issue as other clients are able to connect succesfully.
Could you try to connect to some different server application and verify that the same error does not happen?
14:45, EEST
May 24, 2016
Offline
Hi,
Thanks for your reply! Yes, I tried with other servers and didn’t have that problem, that’s why I was hoping that the problem is with the
Could it be that the problem is with the creation of the certificate? I am using the functionality as it comes with the SampleConsoleServer.java…
Regards,
Fabian
15:46, EEST
April 17, 2013
Offline
Hi,
It seems that there’s some incompatibility and there might be something wrong in the SDK also.
Could you modify the log.properties in the application directory and send the debug level log to uajava-support@prosysopc.com for examination?
17:10, EEST
May 24, 2016
Offline
Hi,
Just sent you the log with three attempts to connect.
Thanks,
Fabian
10:21, EEST
April 17, 2013
Offline
Hello,
Thanks for the log files.
Seems that the client application is sending actual nonces also in the security policy none situation. According to OPC UA specification, this should not happen. However, it’s inconvenient that the server reports this as an exception. We now changed the SDK to allow this kind of situation and this change will most probably be included in the next release.
17:00, EEST
May 24, 2016
Offline
Solved.
Thanks for your fast support.
10:29, EEST
April 17, 2013
Offline
Hi,
Good to know that the issue was solved. The first guess about client sending actual nonces turned out to be wrong. Actually, the issue was happening because the client was sending null values as nonce and the server wasn’t expecting this.
The server application was expecting actual nonce if the clientCertificate was provided in the CreateSession request. In this case, the client application sent a null value as a nonce. We now changed the SDK to handle this situation correctly.
Most Users Ever Online: 1919
Currently Online:
65 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Heikki Tahvanainen: 402
hbrackel: 144
rocket science: 88
pramanj: 86
Francesco Zambon: 83
Ibrahim: 78
Sabari: 62
kapsl: 57
gjevremovic: 49
Xavier: 43
Member Stats:
Guest Posters: 0
Members: 793
Moderators: 7
Admins: 1
Forum Stats:
Groups: 3
Forums: 15
Topics: 1538
Posts: 6493
Newest Members:
sophiadavis, Waynegalse, Phillipbus, Oscarsat, WilliamJer, WilliamTunse, mvsjonah79, RaymondSmutt, Merlin AI pap, patlawrence98Moderators: Jouni Aro: 1027, Pyry: 1, Petri: 0, Bjarne Boström: 1037, Jimmy Ni: 26, Matti Siponen: 353, Lusetti: 0
Administrators: admin: 1
