Problem Note 59802: SAS® Studio might become unresponsive after you log on if large tables were left open in the table viewer in a previous session
SAS Studio might be unresponsive after you log on if large data sets were left open in a previous session. This can occur if all of the following conditions existed when you logged off (or were logged off) your previous session:
- You were in Visual Programmer Perspective.
- You opened a data set from the Files and Folders section in the navigation pane rather than the Libraries section.
- The data set that you opened was large.
On your next logon, the system might be unresponsive after you enter your user name and password. You might be stuck at the Loading... icon, or SAS Studio might open but the system does not respond.
To circumvent the problem, delete your hidden .sasstudio directory after first making a copy of all of the subdirectories. If you have made modifications to Preferences or saved custom tasks or snippets, you can recopy your backup subdirectories over the newly created ones after you log on to SAS Studio again.
By default, the .sasstudio directory is found on UNIX systems in $HOME and on Windows systems in %appdata%\SAS\SASStudio (for a user name of sasdemo, that path resolves to C:\Users\sasdemo\AppData\Roaming\SAS\SASStudio).
The location might have been changed by setting the webdms.studiodataParentDirectory property in your config.properties file.
Click the Hot Fix tab in this note to access the hot fix for this issue for SAS Studio Basic and SAS Studio Mid-Tier editions. Use this Downloads & Hot Fixes page to upgrade SAS Studio Single-User Edition to the latest release, including hot fixes.
Operating System and Release Information
SAS System | SAS Studio | Microsoft® Windows® for x64 | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
Microsoft Windows 8 Enterprise 32-bit | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
Microsoft Windows 8 Enterprise x64 | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
Microsoft Windows 8 Pro 32-bit | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
Microsoft Windows 8 Pro x64 | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
Microsoft Windows 8.1 Enterprise 32-bit | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
Microsoft Windows 8.1 Enterprise x64 | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
Microsoft Windows 8.1 Pro 32-bit | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
Microsoft Windows 8.1 Pro x64 | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
Microsoft Windows 10 | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
Microsoft Windows Server 2008 | 3.5 | | 9.4 TS1M3 | |
Microsoft Windows Server 2008 R2 | 3.5 | | 9.4 TS1M3 | |
Microsoft Windows Server 2008 for x64 | 3.5 | | 9.4 TS1M3 | |
Microsoft Windows Server 2012 Datacenter | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
Microsoft Windows Server 2012 R2 Datacenter | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
Microsoft Windows Server 2012 R2 Std | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
Microsoft Windows Server 2012 Std | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
Windows 7 Enterprise 32 bit | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
Windows 7 Enterprise x64 | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
Windows 7 Home Premium 32 bit | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
Windows 7 Home Premium x64 | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
Windows 7 Professional 32 bit | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
Windows 7 Professional x64 | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
Windows 7 Ultimate 32 bit | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
Windows 7 Ultimate x64 | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
64-bit Enabled AIX | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
64-bit Enabled Solaris | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
HP-UX IPF | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
Linux for x64 | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
Solaris for x64 | 3.5 | 3.7 | 9.4 TS1M3 | 9.4 TS1M5 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2017-08-29 17:21:13 |
Date Created: | 2017-01-25 18:35:56 |