Please consider registering

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
Kepware ServiceResultException due to Bad_RequestTypeInvalid fault
December 14, 2020
21:03, EET
Forum Posts: 3
Member Since:
January 31, 2014
sp_UserOfflineSmall Offline


We have been observing intermittent subscription timeouts with our Prosys Java OPC Client (v4.02) and as a workaround, have implemented a restart protocol to re-establish connectivity to Kepware.

This works as expected, but in certain situations following the reconnect attempt, we get the following error:

SecureChannelTcp – -1095008988: Error recovery = true
TcpConnection – /xxx.xxx.xxx.xxx:49320 Connecting
TcpConnection – Connected (non-reverse), handshake completed, local=/, remote=/xxx.xxx.xxx.xxx:49320
TcpConnection – /xxx.xxx.xxx.xxx:49320 Error
Bad_RequestTypeInvalid (code=0x80530000, description=”The security token request type is not valid.”)
at com.prosysopc.ua.stack.transport.tcp.io.TcpConnection$b.run(SourceFile:276)
TcpConnection – /xxx.xxx.xxx.xxx:49320 Closed
SecureChannelTcp – -1095008988: Error recovery = false
OpcUaClientSession$ – ServiceException subscribing to tag `opc.tcp://xxx.xxx.xxx.xxx:49320/ns=2;s=M364_Z4.M364_Z4.Packout.300R1MH.Count`
com.prosysopc.ua.ServiceException: Bad_RequestTypeInvalid (code=0x80530000, description=”The security token request type is not valid.”) ServiceResult=Bad_RequestTypeInvalid (0x80530000) “The security token request type is not valid.”

At this point, the connection requires a full restart of the client.

Looking online, I’ve found something similar with Ignition’s OPC client and bad responses from Kepware as well:


Is there anything that can be called explicitly in the Prosys client stack to ensure this restart is clean?

Thank you!

December 15, 2020
9:40, EET
Matti Siponen

Forum Posts: 79
Member Since:
February 11, 2020
sp_UserOfflineSmall Offline


Would it be possible for you to update the SDK version used in the Client from 4.0.2 to 4.5.0 and checking if that fixes the problem?

If prossible, could you use Wireshark to capture traffic between the applications? See https://www.prosysopc.com/blog/opc-ua-wireshark/ for instruction on how to capture OPC UA communication with Wireshark. If you’re running the applications on the same host, remember to select “Support loopback traffic” option when installing Wireshark. You can send the Wireshark and Client and Server logs to uajava-support@prosysopc.com so that we can take a look at them.

Forum Timezone: Europe/Helsinki

Most Users Ever Online: 267

Currently Online:
11 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

hbrackel: 103

pramanj: 86

ibrahim: 70

kapsl: 57

gjevremovic: 49

TimK: 41

Fransua33: 39

fred: 38

Thomas Reuther: 33

Rainer Versteeg: 32

Member Stats:

Guest Posters: 0

Members: 1186

Moderators: 15

Admins: 1

Forum Stats:

Groups: 3

Forums: 15

Topics: 1059

Posts: 4458

Newest Members:

gilbertvpj, ThoreB, Gwind, angleamohammad, steffenk41, smartin2k, peterjmf69, juliusdavidson, linettemacandie, RajiMenon

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

Administrators: admin: 1