Bad_InvalidTimestamp - The timestamp is outside the range allowed by the server|OPC UA Implementation: Stacks, Tools, and Samples|Forum|OPC Foundation

Avatar
Search
Forum Scope


Match



Forum Options



Minimum search word length is 3 characters - maximum search word length is 84 characters
Lost password?
sp_Feed sp_PrintTopic sp_TopicIcon
Bad_InvalidTimestamp - The timestamp is outside the range allowed by the server
Avatar
Deepali Ahirrao
Member
Members
Forum Posts: 25
Member Since:
08/16/2019
sp_UserOfflineSmall Offline
1
02/25/2020 - 06:23
sp_Permalink sp_Print

When I try to connect to a discovery server I get following error. The OPC server is behind a Discovery server.

ServiceFault: Bad_InvalidTimestamp (0x80230000) "The timestamp is outside the range allowed by the server."

The discovery server is in Germany and I am trying to access using our client from India. What is the reason behind the error and how to resolve the error? We are using Java stack of OPC (opc-ua-stack-1.4.1.jar) in our client.

Avatar
Randy Armstrong
Admin
Forum Posts: 1564
Member Since:
05/30/2017
sp_UserOfflineSmall Offline
2
02/25/2020 - 12:12
sp_Permalink sp_Print

It means the system clocks are out of sync. Timezone does not matter since the comparison is done using the current UTC time.

Avatar
Deepali Ahirrao
Member
Members
Forum Posts: 25
Member Since:
08/16/2019
sp_UserOfflineSmall Offline
3
02/25/2020 - 22:56
sp_Permalink sp_Print

Thanks, will check on that front. 

I can connect using UaExpert, but get the above mentioned error from our client. Is it because of the way OPC java stack handles this?

Avatar
Randy Armstrong
Admin
Forum Posts: 1564
Member Since:
05/30/2017
sp_UserOfflineSmall Offline
4
02/26/2020 - 14:38
sp_Permalink sp_Print

Not sure how the Java stack works but it should be putting the current UTC time into the request header.

Use wireshark to verify that the time is NULL or just wrong.

Avatar
Deepali Ahirrao
Member
Members
Forum Posts: 25
Member Since:
08/16/2019
sp_UserOfflineSmall Offline
5
02/27/2020 - 22:00
sp_Permalink sp_Print

The timestamp was not set in the request header. Setting that to current time, fixed the issue. Thanks for the help.

Forum Timezone: America/Phoenix
Most Users Ever Online: 510
Currently Online:
Guest(s) 26
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Forum Stats:
Groups: 2
Forums: 10
Topics: 1435
Posts: 4855