13:16, EEST
January 30, 2014
Hi,
I found the thread from 2015 1st q where the same error is described:
http://forum.prosysopc.com/for…..tesession/
Below is what we get in log when our client (prosys SDK 2.2.0-552) is trying to connect to SINUMERIK OPCUA server.
With UaExpert connection is possible. The strange is that we don’t have problem with B&R which is described in mentioned thread.
Till now we didn’t experienced this problem with other servers only with SINUMERIK.
What was the final conclusion about this problem? Iinteroperability problems?
Do you have suggestion how to overwhelm this?
Best regards!
09.06.2016 11:22:32,458 ERROR Client.createSession – Requested endpoint is not found on the server: Endpoint=EndpointDescription: EndpointDescription
EndpointUrl=opc.tcp://10.150.55.240:4840
Server=ApplicationDescription
ApplicationUri=urn:SINUMERIKNCU:miniweb
ProductUri=http://automation.siemens.com
ApplicationName=(en_us) Sinumerik OPC UA OEM
ApplicationType=ApplicationType
name=Server
ordinal=0
GatewayServerUri=null
DiscoveryProfileUri=null
DiscoveryUrls=class java.lang.String[1]
[0]=opc.tcp://10.150.55.240:4840
ServerCertificate=[864] 0x3082035c308202c5a003020102020467458b6b300d06092a864886f70d010105050030818b310b30090603550406160244453110300e06035504081607426176617269613111300f0603550407160845726c616e67656e31133011060355040a160a5369656d656e732041473111300f060355040b1608496e6475737472793120301e06092a864886f70d01090116116f70637561407369656d656e732e636f6d310d300b060355040316046e637531301e170d3934303130373232343030345a170d3234303130373232343030345a30818b310b30090603550406160244453110300e06035504081607426176617269613111300f0603550407160845726c616e67656e31133011060355040a160a5369656d656e732041473111300f060355040b1608496e6475737472793120301e06092a864886f70d01090116116f70637561407369656d656e732e636f6d310d300b060355040316046e63753130819f300d06092a864886f70d010101050003818d0030818902818100eea5bf3e731a3e6024de651d1729029f8788f023520430f4f8e908e4c1b4731ffea766917a4acf5e8312f567c411109d076eecb856bee066ec2ae42441d8baf9f5188a90741a2ffb307d2770f1efb37840a82a158965238af768811222907828638a45f528c9ad755fbbd1c55ef3942285e792b4b6de22a8c982b7d0f099ad590203010001a381ca3081c730280603551d23010100041e301c8014ef6fbf4e3f2ce486859855656cabcfa3843893a8820467458b6b30200603551d0e01010004160414ef6fbf4e3f2ce486859855656cabcfa3843893a8300f0603551d130101ff040530030101ff300e0603551d0f0101ff0404030201f630200603551d250101ff0416301406082b0601050507030206082b0601050507030130360603551d11010100042c302a820d31302e3135302e3130392e3634861975726e3a31302e3135302e3130392e36343a6d696e69776562300d06092a864886f70d01010505000381810031d884ac81d800db1d272e78a35cadd96ccf2d36c5535b45c7ba0cac0e711e4f6dc62c1606744ea22611d4fa3566d1ccf17d761fb514f9e76ae59fa7f1a6ee74f24b34bd0f3ea4777d84d13676b606d485b891318bf1b8187baab8cfc5bce6c65d0c6cd3dd28e103535b94f1d097a30b0ad034343aa8dbb302c7a7aa95f54026
SecurityMode=MessageSecurityMode
name=None
ordinal=1
SecurityPolicyUri=http://opcfoundation.org/UA/SecurityPolicy#None
UserIdentityTokens=class org.opcfoundation.ua.core.UserTokenPolicy[2]
[0]=UserTokenPolicy
PolicyId=Anonymous
TokenType=UserTokenType
name=Anonymous
ordinal=0
IssuedTokenType=null
IssuerEndpointUrl=null
SecurityPolicyUri=http://opcfoundation.org/UA/SecurityPolicy#None
[1]=UserTokenPolicy
PolicyId=http://opcfoundation.org/UA/SecurityPolicy#Basic128Rsa15
TokenType=UserTokenType
name=UserName
ordinal=1
IssuedTokenType=null
IssuerEndpointUrl=null
SecurityPolicyUri=http://opcfoundation.org/UA/SecurityPolicy#Basic128Rsa15
TransportProfileUri=http://opcfoundation.org/UA-Profile/Transport/uatcp-uasc-uabinary
SecurityLevel=0
09.06.2016 11:22:32,460 ERROR OpcUaServerBrowser.connectUaClient – 2Failed to create session channel to server: : opc.tcp://10.150.55.240:4840 [http://opcfoundation.org/UA/SecurityPolicy#None,None]
14:46, EEST
April 17, 2013
Hello,
Try setting
and let us know if this solves the issue.
By default, the endpoints are validated, but some servers provide different endpointUrls for the GetEndpoints and CreateSession service responses and may therefore fail at connection. The check is required for OPC UA compliance.
9:45, EEST
January 30, 2014
10:24, EEST
August 31, 2016
Heikki Tahvanainen said
Hello,Hi, I tried to set the value as suggested for DiscoveredEndpoints to false. However, I still get the same error.
INFO [Thread-1]: OPCClientUA thread start failed: Failed to create session channel to server : opc.tcp://xxx.xxx.xx.xxx:9999 [http://opcfoundation.org/UA/SecurityPolicy#None,None] .
However if I connect to this opc server using UAExpert client then I get no errors. The problem occurs only with Prosys Client or with Prosys Java SDK
13:21, EEST
April 17, 2013
Hi,
I’m sorry to hear that you are experiencing problems.
Can you post a larger snippet of the log that shows the createSessionChannel method call that ends up in “Failed to create session channel to server” error message? If possible, please use log level debug.
There shouldn’t be that much logging associated with this method call but if you end up with a huge log file which is impractical to post here on forum, you can also send an email to uajava-support prosysopc.com mailing list.
Most Users Ever Online: 1919
Currently Online:
19 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: 730
Moderators: 7
Admins: 1
Forum Stats:
Groups: 3
Forums: 15
Topics: 1529
Posts: 6471
Newest Members:
PromotionToold, HypromeImpupe, toneylapham544, rondawolinski7, Marypof5711, roycedelargie91, kourtneyquisenbe, ellis87832073466, zkxwilliemae, gabriellabachusModerators: Jouni Aro: 1026, Pyry: 1, Petri: 0, Bjarne Boström: 1032, Jimmy Ni: 26, Matti Siponen: 349, Lusetti: 0
Administrators: admin: 1