Hi, when the token is refreshing, i am getting the following error (you can see it on the image attached) "Exception TokenExpireTimer_Callback". we have setted /implemented the OnTokenRefreshed method. I think that there exception is generating on the dll

MIP
, , , ,
1

error gateway
error gateway720×288 59.1 KB

2

Please, we need to fix it. can someone help us from Software Team ???

3

the exception is generating in the ServerCommandWrapper file and my app is closing. I cannot catch the exception on my app.

4

This is a known issue. Please see this link –

https://developer.milestonesys.com/s/question/0D53X00008Mz9OESAZ/how-do-i-refresh-the-login-token-correctly

5

Hi Kito, i have my own app, i am not using the TCPViewer app. the exception is in the ServerCommandWrapper dll file. another question, how can i set a shortened token timeout??? actually it is 4 hours.

6

can you please help me today??? it is urgent. Own app is on production servers.

7

Please see this KB – MODIFY XPROTECT ADVANCED VMS TOKEN TIMEOUT VALUE TO AVOID ‘INVALID TOKEN’ ERROR

https://developer.milestonesys.com/s/article/modify-XProtect-Advanced-and-XProtect-Plus-token-timeout-value-to-avoid-Invalid-Token

8

Hi Kito, can we set the timeout indefinite (for token refresh ) ???

9

here is my respose,

Update (20/05/2019): While the theoretical maximum value of the

ClientTokenTimoutMinutes

is

2147483647

, we do not recommend setting values close to this number, as 2147483647 minutes would translated roughly to 4085 years. :slight_smile: (If you set it to 2’147’483’647 minutes, this will equal 35791394 hours = 1491308 days = 4085 years.)

Instead, if you need to use some pretty long timeout times, try with a more moderate number first, like, for example,

525600

(which will translate to 1 year exactly). And if this works fine, you can next try an even bigger number, such as

5256000

(10 years).