When launching a workspace server session, you might receive one of the following errors:
"[Error] The launch of the server process failed because of an invalid or inaccessible SASUSER library."
"[Error] The launch of the server process failed because of an invalid or inaccessible WORK library."
If you encounter one of these error messages, you are unable to access the Operating System (OS) file system location that the specified library (SASUSER/WORK) points to.
Workarounds
To work around this issue, ask the system administrator to ensure that you have read/write/execute permissions to the OS directory location. You should also be able to connect to SASApp.
SASUSER Library Workaround
The SASUSER system option specifies the SAS library that contains a user's Profile catalog.
- To find the default value for SASUSER, go to the SAS configuration file (default location is c:\program files\SASHome\SASFoundation\9.4\nls\en\sasv9.cfg).
- Open the sasv9.cfg file and find the line similar to the following: -SASUSER "?FOLDERID_Documents\My SAS Files\9.4".
- The default value in this file points to the location on the server (C:\Users\userid\Documents\My SAS Files\9.4).
- Ensure that you have read/write/execute access to this location.
WORK Library Workaround
If the error message references the WORK library, it usually means that you do not have access to the WORK library or that the path to the WORK library is incorrect. Complete the following steps to work around this problem:
- Launch SAS locally on the server.
- Submit the following statement: libname work list;
This statement returns the properties of the WORK library, including the physical path, which will be similar to the following: Physical Name= C:\Users\userid\AppData\Local\Temp\SAS Temporary Files\_TD12088_D7B135_\Prc2.
In this example, the WORK libraries are being created under \SAS Temporary Files.
- Ensure that you have read/write/execute access to the path returned in the statement.