The SAS^® start-up errors "ERROR: Invalid physical name for library WORK", "ERROR: Insufficient authorization to access WORK library" and "ERROR: Library WORK does not exist" might require changing the location for the SAS Work library. Also, there are other reasons to change the SAS Work location, such as changing to a drive with more disk space available. The SAS Work library has to be defined prior to starting SAS. Once a SAS session is open, the SAS Work library cannot be reassigned within that SAS session. 

The SAS Work library contains temporary files that are used during a SAS session. To determine the physical location of the SAS Work library within a SAS session, submit one of the following statements:

View the log results that display the directory path for the SAS Work library.

You can also verify the SAS Work library location used in the SAS session by using the SAS Explorer window. Double-click Libraries. Right-click Work and select Properties. The full path is displayed under Levels.

On Microsoft Windows operating systems, the SAS Work library is set to the default value of !TEMP/SAS Temporary Files where !TEMP is a Windows environment variable. To see the value for the !TEMP environment variable on your machine, in the Windows Search box type: COMMAND PROMPT and open the COMMAND PROMPT window. Then, enter the following:

If the specified SAS Work directory path does not exist or operating system file permissions deny access to the directory, any or all of the following messages might appear when you attempt to start SAS:

How to change the location of the SAS Work library

 

To redirect the Work library to a different physical directory location might require assistance from your IT department if permissions errors occur during the steps below.  Take these steps:

1. Make a backup copy of the sasv9.cfg file.
   • The default location for this file is as follows:
     • SAS^® 9.1: C:\Program Files\SAS\SAS 9.1\nls\en
     • SAS^® 9.2: C:\Program Files\SAS\SASFoundation\9.2\nls\en
     • SAS 9.2 32-bit on an X64 operating system: C:\Program Files\SAS\SASFoundation\9.2(32-bit)\nls\en
     • SAS^® 9.3: C:\Program Files\SASHOME\SASFoundation\9.3\nls\en
     • SAS 9.3 32-bit on an X64 operating system: C:\Program Files\SASHOME\x86\SASFoundation\9.3\nls\en
     • SAS^® 9.4: C:\Program Files\SASHOME\SASFoundation\9.4\nls\en
     • SAS 9.4 32-bit on an X64 operating system: C:\Program Files\SASHOME\x86\SASFoundation\9.4\nls\en
       
       Note: If SAS 9.3 and SAS 9.4 are on the same machine, then the SAS 9.4 default location uses the SASHOME2 directory, instead of the SASHOME directory.
2. Go to the Search box on your system and enter Notepad.
   • Then, it is important to right-click Notepad and select Run as administrator.
   • In Notepad, select File ► Open. 
   • Then, change the file types in the bottom right-hand corner from Text Documents (*.txt) to All Files (*.*).
   • On the left side of the Open window, select the C:\ drive. Navigate to the file in Step 1 and open it.
3. In Notepad, locate the SAS System option setting -WORK "directory-path".
4. Modify the -WORK "directory-path" setting to point to the new drive and directory. Do not change the setting to use a drive letter only. The user account must have full control permissions to the new directory path.

• For example, to save all temporary files to the D: drive, change the -WORK option in the sasv9.cfg file to the following:
  -WORK "D:\SASWORK\SAS Temporary Files"

5. In Notepad, select File ► Save. 
   • If you receive a "Permissions Denied" message, close Notepad. 
   • Locate the sas9v.cfg file.
   • Right-click the file and choose Properties.
   • On the Security tab, add your user ID and grant full access. Then repeat Steps 2–5 again. 
6. Exit Notepad.
7. Restart the SAS session to use the new Work location.

 

SAS Work configuration tips for a SAS deployment shared by multiple user accounts

Each unique user account that launches SAS sessions on a shared machine requires its own respective Work library. One technique to separate Work libraries for multiple user accounts is to include the Windows environment variable !USERNAME in the specified directory path.    

Here is an example:

 To see the value for the environment variable !USERNAME, in the Windows Search box type: COMMAND PROMPT and open the COMMAND PROMPT window. Then, enter the following:

Restart the SAS session to use the new Work location.

 

How to redirect the SAS Work library in the SAS start-up command of the "SAS 9.x (English)" application shortcut

You can add the -WORK option to the SAS start-up command in the SAS 9.x (English) shortcut. After you edit the shortcut, launch SAS by selecting the application item or icon to use the new SAS Work library directory path.

For example, if you right-click the SAS 9.4 (English) shortcut icon and select Properties, the Shortcut tab might have the following Target option:

To change the SAS Work library location, add the -WORK option to this command:

Here is an example of the command-line syntax for a SAS deployment shared by multiple user accounts on a single machine:

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	Base SAS	Microsoft Windows Server 2003 Datacenter Edition			9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Enterprise Edition			9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Standard Edition			9.1 TS1M3 SP4
		Microsoft Windows NT Workstation			9.1 TS1M3 SP4
		Microsoft Windows XP Professional			9.1 TS1M3 SP4
		Microsoft Windows 2000 Professional			9.1 TS1M3 SP4
		Microsoft® Windows® for 64-Bit Itanium-based Systems	9.2		9.2 TS2M3
		Microsoft Windows Server 2003 Datacenter 64-bit Edition	9.2		9.2 TS2M3
		Microsoft Windows Server 2003 Enterprise 64-bit Edition	9.2		9.2 TS2M3
		Microsoft Windows XP 64-bit Edition	9.2		9.2 TS2M3
		Microsoft Windows Server 2003 for x64	9.2		9.2 TS2M3
		Microsoft Windows Server 2008	9.2		9.2 TS2M3
		Microsoft Windows Server 2008 R2	9.2		9.2 TS2M3
		Microsoft Windows Server 2008 for x64	9.2		9.2 TS2M3
		Windows Vista	9.2		9.2 TS2M3
		Windows Vista for x64	9.2		9.2 TS2M3
		Microsoft Windows 8 Enterprise 32-bit	9.3_M2		9.3 TS1M2
		Microsoft Windows 8 Enterprise x64	9.3_M2		9.3 TS1M2
		Microsoft Windows 8 Pro 32-bit	9.3_M2		9.3 TS1M2
		Microsoft Windows 8 Pro x64	9.3_M2		9.3 TS1M2
		Microsoft Windows 8.1 Enterprise 32-bit	9.3_M2		9.3 TS1M2
		Microsoft Windows 8.1 Enterprise x64	9.3_M2		9.3 TS1M2
		Microsoft Windows 8.1 Pro 32-bit	9.3_M2		9.3 TS1M2
		Microsoft Windows 8.1 Pro x64	9.3_M2		9.3 TS1M2
		Microsoft Windows Server 2012 Datacenter	9.3_M2		9.3 TS1M2
		Microsoft Windows Server 2012 R2 Datacenter	9.3_M2		9.3 TS1M2
		Microsoft Windows Server 2012 R2 Std	9.3_M2		9.3 TS1M2
		Microsoft Windows Server 2012 Std	9.3_M2		9.3 TS1M2
		Windows 7 Enterprise 32 bit	9.3_M2		9.3 TS1M2
		Windows 7 Enterprise x64	9.3_M2		9.3 TS1M2
		Windows 7 Home Premium 32 bit	9.3_M2		9.3 TS1M2
		Windows 7 Home Premium x64	9.3_M2		9.3 TS1M2
		Windows 7 Professional 32 bit	9.3_M2		9.3 TS1M2
		Windows 7 Professional x64	9.3_M2		9.3 TS1M2
		Windows 7 Ultimate 32 bit	9.3_M2		9.3 TS1M2
		Windows 7 Ultimate x64	9.3_M2		9.3 TS1M2
		Microsoft® Windows® for x64	9.4		9.4 TS1M0
		Microsoft Windows 10	9.4_M3		9.4 TS1M3
		Microsoft Windows Server 2016	9.4_M7		9.4 TS1M7
		Microsoft Windows Server 2019	9.4_M7		9.4 TS1M7

* 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.

---

The SAS® start-up errors "ERROR: Invalid physical name for library WORK", "ERROR: Insufficient authorization to access WORK library" and "ERROR: Library WORK does not exist" might require changing the location for the SAS® Work library.

Type:	Usage Note
Priority:

Date Modified:	2021-02-23 20:38:26
Date Created:	2007-01-01 07:28:21