SUPPORT / SAMPLES & SAS NOTES
 

Support

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

DetailsHotfixAboutRate It

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

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS StudioMicrosoft® Windows® for x643.53.79.4 TS1M39.4 TS1M5
Microsoft Windows 8 Enterprise 32-bit3.53.79.4 TS1M39.4 TS1M5
Microsoft Windows 8 Enterprise x643.53.79.4 TS1M39.4 TS1M5
Microsoft Windows 8 Pro 32-bit3.53.79.4 TS1M39.4 TS1M5
Microsoft Windows 8 Pro x643.53.79.4 TS1M39.4 TS1M5
Microsoft Windows 8.1 Enterprise 32-bit3.53.79.4 TS1M39.4 TS1M5
Microsoft Windows 8.1 Enterprise x643.53.79.4 TS1M39.4 TS1M5
Microsoft Windows 8.1 Pro 32-bit3.53.79.4 TS1M39.4 TS1M5
Microsoft Windows 8.1 Pro x643.53.79.4 TS1M39.4 TS1M5
Microsoft Windows 103.53.79.4 TS1M39.4 TS1M5
Microsoft Windows Server 20083.59.4 TS1M3
Microsoft Windows Server 2008 R23.59.4 TS1M3
Microsoft Windows Server 2008 for x643.59.4 TS1M3
Microsoft Windows Server 2012 Datacenter3.53.79.4 TS1M39.4 TS1M5
Microsoft Windows Server 2012 R2 Datacenter3.53.79.4 TS1M39.4 TS1M5
Microsoft Windows Server 2012 R2 Std3.53.79.4 TS1M39.4 TS1M5
Microsoft Windows Server 2012 Std3.53.79.4 TS1M39.4 TS1M5
Windows 7 Enterprise 32 bit3.53.79.4 TS1M39.4 TS1M5
Windows 7 Enterprise x643.53.79.4 TS1M39.4 TS1M5
Windows 7 Home Premium 32 bit3.53.79.4 TS1M39.4 TS1M5
Windows 7 Home Premium x643.53.79.4 TS1M39.4 TS1M5
Windows 7 Professional 32 bit3.53.79.4 TS1M39.4 TS1M5
Windows 7 Professional x643.53.79.4 TS1M39.4 TS1M5
Windows 7 Ultimate 32 bit3.53.79.4 TS1M39.4 TS1M5
Windows 7 Ultimate x643.53.79.4 TS1M39.4 TS1M5
64-bit Enabled AIX3.53.79.4 TS1M39.4 TS1M5
64-bit Enabled Solaris3.53.79.4 TS1M39.4 TS1M5
HP-UX IPF3.53.79.4 TS1M39.4 TS1M5
Linux for x643.53.79.4 TS1M39.4 TS1M5
Solaris for x643.53.79.4 TS1M39.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.