Problem Note 69898: SAS® Studio can lose its connection to the compute server when using the Microsoft Edge or Google Chrome browsers
 |  |  |  |  |
Both the Microsoft Edge browser and the Google Chrome browser have added features to suspend tabs that they assess as inactive after a configured period of time.
In Edge, this feature is called sleeping tabs, and in Chrome, it is called Memory Saver.
If you navigate away from the tab where SAS Studio is running when you are using these browsers and the session is considered inactive, the JavaScript code that keeps the SAS Studio session alive can no longer run. Eventually, the SAS Studio connection to the server is ended.
When you navigate back to the SAS Studio tab in this scenario, the following pop-up message appears:
If you select Cancel, the session appears to continue. However, the connection between the session and the server has been ended. A new connection to the server is created, but you are not notified about this.
In this scenario, all the temporary work in the previous session, such as work tables and LIBNAME statements, is lost. Unsaved changes to code are also lost. However, the code changes can be restored if Documentary Recovery is enabled, which it is by default.
Workaround
In order for your session to not be timed out prematurely, disable these browser features or add your SAS Studio URL to the exclusion list.
If you have the browser features enabled with the SAS® Viya® Stable 2022.12 release or later, time-out still occurs earlier than the specified time and a message is displayed that the session has been timed out.
Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Studio | Microsoft Windows Server 2003 Datacenter Edition | 5.1 | Viya | ||
| Microsoft Windows NT Workstation | 5.1 | Viya | ||||
| Microsoft Windows 2000 Professional | 5.1 | Viya | ||||
| Microsoft Windows 2000 Server | 5.1 | Viya | ||||
| Microsoft Windows 2000 Advanced Server | 5.1 | Viya | ||||
| Microsoft Windows 2000 Datacenter Server | 5.1 | Viya | ||||
| HP-UX IPF | 3.8 | 9.4 TS1M6 | ||||
| 64-bit Enabled Solaris | 3.8 | 9.4 TS1M6 | ||||
| 64-bit Enabled AIX | 3.8 | 9.4 TS1M6 | ||||
| Windows 7 Ultimate x64 | 3.8 | 9.4 TS1M6 | ||||
| Windows 7 Ultimate 32 bit | 3.8 | 9.4 TS1M6 | ||||
| Windows 7 Professional x64 | 3.8 | 9.4 TS1M6 | ||||
| Windows 7 Professional 32 bit | 3.8 | 9.4 TS1M6 | ||||
| Windows 7 Home Premium x64 | 3.8 | 9.4 TS1M6 | ||||
| Windows 7 Home Premium 32 bit | 3.8 | 9.4 TS1M6 | ||||
| Windows 7 Enterprise x64 | 3.8 | 9.4 TS1M6 | ||||
| Windows 7 Enterprise 32 bit | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows Server 2012 Std | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows Server 2012 R2 Std | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows Server 2012 R2 Datacenter | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows Server 2012 Datacenter | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows Server 2008 for x64 | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows Server 2008 R2 | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows Server 2008 | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows 10 | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows 8.1 Pro x64 | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows 8.1 Pro 32-bit | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows 8.1 Enterprise x64 | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows 8.1 Enterprise 32-bit | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows 8 Pro x64 | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows 8 Pro 32-bit | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows 8 Enterprise x64 | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows 8 Enterprise 32-bit | 3.8 | 9.4 TS1M6 | ||||
| Microsoft® Windows® for x64 | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows Server 2003 Enterprise Edition | 5.1 | Viya | ||||
| Microsoft Windows Server 2003 Standard Edition | 5.1 | Viya | ||||
| Microsoft Windows Server 2003 for x64 | 5.1 | Viya | ||||
| Microsoft Windows Server 2016 | 5.1 | Viya | ||||
| Microsoft Windows Server 2019 | 5.1 | Viya | ||||
| Microsoft Windows Server 2022 | 5.1 | Viya | ||||
| Microsoft Windows XP Professional | 5.1 | Viya | ||||
| Windows Vista | 5.1 | Viya | ||||
| Windows Vista for x64 | 5.1 | Viya | ||||
| Linux for x64 | 5.1 | Viya | ||||
| Microsoft Windows 95/98 | 5.1 | Viya | ||||
| Microsoft Windows 11 | 5.1 | Viya | ||||
| Solaris for x64 | 3.8 | 9.4 TS1M6 | ||||
| SAS System | SAS Studio for Viya | Linux for x64 | 2020.0.4 | Stable 2022.12 | Viya platform | Viya platform |
Viya on Windows: An update for this issue is available for SAS Viya 3.5. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.5 for Windows Deployment Guide at
http://documentation.sas.com/?softwareId=administration&softwareVersion=3.5&softwareContextId=softwareUpdatesWinViya on Linux: An update for this issue is available for SAS Viya 3.5. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.5 for Linux Deployment Guide at
http://documentation.sas.com/?softwareId=administration&softwareVersion=3.5&softwareContextId=softwareUpdates| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2024-02-07 14:06:39 |
| Date Created: | 2023-02-23 13:22:53 |