Hello,
I've been running a separate micro PC for nearly a year now, which, on startup, opens UI3 on 2 screens (in Chrome) . (Basically my surveillance monitor station).
Only changes to this system would be regular windows and application updates.
I noticed that after upgrading the BI Server to 5.0.6.2 (on Monday) and then even after upgrading to 5.0.6.4 (Today) I continue to get this error message:
Little background, the micro PC will occasionally go to sleep after several hours of non use, but when I wake the system backup with a simple mouse movement, I typically see a couple of red and yellow alerts in the bottom right hand corner, followed by the login page, then the UI3 typically reconnects itself without any user interaction.
However, after the recent update, I now have to get on the system and click the OK button as show in the picture on both screens and hard refresh the screens.
Is there any way to fix that issue so that it will reconnect by itself?
I've reverted back to a snapshot of my BI server that was running 5.0.5.9 where I know this issue wasn't present.
Thank you.
I've been running a separate micro PC for nearly a year now, which, on startup, opens UI3 on 2 screens (in Chrome) . (Basically my surveillance monitor station).
Only changes to this system would be regular windows and application updates.
I noticed that after upgrading the BI Server to 5.0.6.2 (on Monday) and then even after upgrading to 5.0.6.4 (Today) I continue to get this error message:
Little background, the micro PC will occasionally go to sleep after several hours of non use, but when I wake the system backup with a simple mouse movement, I typically see a couple of red and yellow alerts in the bottom right hand corner, followed by the login page, then the UI3 typically reconnects itself without any user interaction.
However, after the recent update, I now have to get on the system and click the OK button as show in the picture on both screens and hard refresh the screens.
Is there any way to fix that issue so that it will reconnect by itself?
I've reverted back to a snapshot of my BI server that was running 5.0.5.9 where I know this issue wasn't present.
Thank you.
