GeoSCADA 2021 Application Not Responding

[dahoodman]

On several occasions I have users, myself included, where if you are logged out of GeoSCADA by timeout and then log back in  everything seems normal until you try to change to a different Mimic. Then it comes up and says document not found. I don't know that I have any reports of this issue for users that just run the application logged out 24x7 or that log themselves out and don't allow GeoSCADA to force the logout due to inactivity. Additionally I have a dispatch center that stays up and logged in 24x7 with the same user. They only monitor the Alarm screen and since they are in a locked facility their 'user' never logs out and they have no reason to change screens. The issue for them shows up by GeoSCADA not providing any new alarms. The fix in both of these situations is to restart the GeoSCADA application which is a bit of a hassle. It's not like this issue shows up after a certain time, it's random and a lot of times it catches users like myself when we try to log back in. For the Dispatch user it's really bad because they are responsible for watching alarms and calling out personnel for critical alarms. When no new alarms come in, they assume all is good and have no way to tell their screen is frozen except to try and change Mimics, which is something they are not supposed to do. They also monitor a lot more than SCADA so there can be times where they are doing other duties just waiting to hear an alarm bell from SCADA rather than actually watching the screen.

Has anyone else faced this issue? I believe the two issues are related. We have GeoSCADA 2021 - Dec 2022 update running Server 2016 with clients on W10, Server2012, Server2016, Server2019

[sbeadle]

Hi. I really think you should report this through support, and provide client and server logs for the times any incident has occurred.

Thank you,

Steve

[dahoodman]

Yep we've called and left a message with support voicemail as no one seems to answer and just waiting on a call back. I was just hoping someone on here may have faced the same issue and got a resolution.