Avatar

Please consider registering
guest

sp_LogInOut Log In sp_Registration Register

Register | Lost password?
Advanced Search

— Forum Scope —




— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_Feed Topic RSS sp_TopicIcon
Issue with connecting the client
February 10, 2021
14:31, EET
Avatar
majaba
New Member
Members
Forum Posts: 2
Member Since:
February 10, 2021
sp_UserOfflineSmall Offline

Hello everyone,

I’m using Prosys Simulation Server and OPC UA Foundation ANSI C stack to connect to the server with anonymous user.
I can activate session, but when I want to read something from the node, it returns me in the responseHeader ServiceResult status code 0x80260000 (The session was closed by the client.)

Please can you give me advice about this ?

February 11, 2021
12:55, EET
Avatar
Bjarne Boström
Moderator
Moderators
Forum Posts: 620
Member Since:
April 3, 2012
sp_UserOfflineSmall Offline

Hi,

My advice is to stop using a “legacy stack”, which is pretty much discontinued completely by the OPC Foundation at this point and use a proper SDK-level library/framework for your OPC UA needs. The readme in https://github.com/OPCFoundation/UA-AnsiC-Legacy says “This repository (https://github.com/OPCFoundation/UA-AnsiC-Legacy) will be closed end of February 2021.”

Generally speaking, you are completely on your own if you use a bare “stack” level implementation. Using those requires expertise in OPC UA and even with that they usually simply lack features to deal with the every growing feature set which OPC Foundation is continously increasing.

That being said, the error code in the full form is Bad_SessionClosed, 0x80260000, “The session was closed by the client.”. You can check if the simulation server logs indicate anything, they are written by default /.prosysopc/prosys-opc-ua-simulation-server/log/.

Do you mean by “activate session”, that you made both CreateSession and ActivateSession calls with both succeeding, and you are using the authentication token returned in CreateSessionResponse in the ActivateSession and all further calls? Failing to do these would be one cause, which would been seen by the client by that error code. Typically all that is implemented by an SDK-level framework internally.

February 15, 2021
9:48, EET
Avatar
majaba
New Member
Members
Forum Posts: 2
Member Since:
February 10, 2021
sp_UserOfflineSmall Offline

Thank you Bjarne, you have right I didn’t assign everything for the Auth. token.

P.S

I’m using the stack because I want to know how stuff works not just to use some done solution.

Forum Timezone: Europe/Helsinki

Most Users Ever Online: 267

Currently Online:
10 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

hbrackel: 109

pramanj: 86

ibrahim: 71

kapsl: 57

gjevremovic: 49

TimK: 41

fred: 41

Fransua33: 39

Xavier: 34

Thomas Reuther: 33

Member Stats:

Guest Posters: 0

Members: 1221

Moderators: 15

Admins: 1

Forum Stats:

Groups: 3

Forums: 15

Topics: 1089

Posts: 4591

Newest Members:

aravindj, Deniz.Turan, DenizT, igonzalez, lavonwinters963, felicapurdy9, shoshanastopford, UlrichFM, majaba, Yash_Joshi_Pratiti

Moderators: Jouni Aro: 865, Otso Palonen: 32, Tuomas Hiltunen: 5, janimakela: 0, Pyry: 1, Terho: 0, Petri: 0, Bjarne Boström: 620, Heikki Tahvanainen: 402, Jukka Asikainen: 1, moldzh08: 0, Teppo Uimonen: 21, Markus Johansson: 30, Matti Siponen: 92, Lusetti: 0

Administrators: admin: 1