ViewX - Session Timeouts

[GeoSco]

We've got on Geo SCADA Version 84.8379 installed on a number sites and has been running fine for at least 2 years on these sites.

We have just started experiencing ViewX is expiring sessions instantly when you log on. If I enter my password again ViewX opens but after a few seconds the session expires again, basically stuck in a loop unusable.

The only way to stop this happening is to reboot the Operating System (the physical server) and then ViewX starts working normally again, ViewX does not expire the session after a reboot.

There has been no configuration changes, for example Inactivity logout is still at 0 minutes within Server Configuration and 1 hour within user.

Why has this just started happening? And after a reboot of the Operating System I don't experience this anymore?

[geoffpatton]

I have not experienced anything like that but it sounds like a call to your region's support center needs to be made. Could be a recent windows update issue.

[tfranklin]

Yeah as Geoff suggested, I'd ping support on this one.  If I had to guess, it's not a timeout at all but rather some other sub-process.  ViewX client logs or dumps would help narrow it down.  I'd start there and reach out to support if something isn't immediately obvious.  

[BevanWeiss]

When you say you need to restart for it to stop happening, do you mean restart the ViewX client computer, or do you mean restart the GeoSCADA Expert server computer?

It's possible that this is a firewall type of issue, where the initial outbound connection is established fine, but the inbound advise connections aren't... and then ViewX is trying to fix this by throwing away and re-building the connections, at which point you get the behaviour that you're reporting.

As the others have noted, you probably want to contact your local Schneider Tech Support for this.  They're going to want to see Server / Client logs, and get information on your network setup, system architecture etc etc to identify the cause of the issue.

[GeoSco]

Thanks all, I mean reboot the actual Server.

I raised a call but Schneider, demonstrated this and provided logs but they've never seen this before either and do not have a fix.

[AdamWoodlandToo]

The only time I've seen this happen is when the time on the client keeps jumping forward. Next time watch the date and time, perhaps whatever you're using the sync the time has gone haywire and jumps forwards quickly or in big jumps causing the timer to kick in?

This happened many years ago when I was playing with the DNP3 slave setup and timezones were mismatched (local vs UTC) so the time kept jumping forwards and the server ended up in the year 5000 or something before I noticed. In theory if the client syncs it time from a Geo SCADA server then some structured text/SYSTEM call doing some time setting could do similar...

Should be event logs in Windows for any time change too (maybe event id 4616)

[sbeadle]

Thread is dormant, marking as informational. Looked to be an environmental issue.