When running a SAS^® Stored Process and attempting to access a preassigned library, in some cases the library may not be available. This SAS Note provides some troubleshooting tips if you are not able to access the preassigned library when running a SAS Stored Process in SAS^® 9.13.

When running SAS^® 9.2, see SAS Usage Note 36979.

1. Verify that the Library is preassigned checkbox is selected for your library.
1. Open the SAS^® Management Console
2. Select Data Library Manager plugin
3. Select SAS Libraries
4. Right Mouse Click on the library and choose Properties
5. Select the Options Tab, then click on Advanced Options
6. Verify that the Library is preassigned checkbox is checked.
2. Verify that the METAAUTOINIT option is included on the Object Server Parameters statement for your SAS Stored Process server.
1. Open the SAS Management Console
2. Select Server Manager
3. Expand the application server (usually SASMain)
4. Expand Logical Stored Process Server
5. Select Stored Process Server
6. Right mouse click on Properties
7. Choose the OPTIONS tab
8. In the Launch Commands section verify that Object Server Parameters entry contains:
   METAAUTOINIT
9. Click OK to save the changes
3. Make sure that the library is assigned to an application context, which is SASMAIN by default.
1. Open your SAS Management Console
2. Choose Data Library Manager
3. Expand SAS Libraries
4. Right mouse click on your library name and choose Properties.
5. Select the Assign tab
6. Click on the SAS server (SASMAIN), highlight it and choose OK.

   NOTE: Make sure SASMain is highlighted in blue. Otherwise, it is not selected.

7. Make sure you have granted the correct permissions for the SAS General Servers group in the metadata for the library.
1. Open the SAS Management Console
2. Select Data Library Manager
3. Expand SAS Libraries
4. Right mouse click on library name and choose Properties.
5. Select the Authorization tab.
6. Insure that the SAS General Servers group has ReadMetadata and Read privileges (the Grant box should be checked). By default, the SAS General Servers group will be included in the PUBLIC group.
7. The sassrv account is the login account for SAS General Servers.
8. Restart your SAS^® Object Spawner so that the above changes will take effect.
9. As a test, specify the complete LIBNAME statement at the top of your SAS Stored Process code. Then, run your SAS Stored Process and check your SAS log file for ERROR messages.
4. As a test, perform the following:
1. Open SAS Management Console using the sassrv user account.
2. Access your preassigned SAS library under Data Library Manager.
3. For this test, you will need to temporarily uncheck the Library is preassigned box for your library.
4. Select Options ► Advanced Options. Then, uncheck the Library is preassigned box.
5. Under SAS Libraries, Right click on your library and select Import tables. If you cannot Import tables, then the sassrv user account may not have the privileges that it needs to import the tables. Or, perhaps your library is defined incorrectly.

   After this test, you should check the Library is preassigned box for your library (which you temporarily changed above).

5. As a test, attempt to access your preassigned libraries from a regular SAS job (outside of the SAS Stored Process Server). Follow these steps:
1. Bring up a DOS shell on Windows (or a Unix shell on Unix). Then, go to the SAS root directory (where the sas executable resides).
2. Issue the below command:
   sas -metaautoresources "SASMain"
3. You will be prompted to provide information to connect to your Metadata server. For User Name specify sassrv (or your Stored Process Server's Login user account)
4. Near the top of the log file you should see a note similar to the following (where "xxxxxx" is your libref name):
   NOTE: libref xxxxxx was successfully assigned from logical server.

Operating System and Release Information