If you encounter this problem, and you attempt to execute the same SAS Stored Process again, the request might fail and the SAS^® Stored Process Server log file might contain an error message that is similar to the following:

  ERROR: MEMBER lock is not available for <data set name here> , lock held by REB name length returned is zero..

A Segmentation Violation (or Access Violation) error message might also appear in your SAS Stored Process Server log file.

If you stop and restart your SAS Stored Process Server, the SAS Stored Process should execute successfully. However, if you cancel another request when PROC SQL code is executing, then in some cases the problem might reoccur.

One workaround is to replace the PROC SQL code with a SAS data step that performs similar functionality.

Another workaround is to modify the PROC SQL code so that it creates a uniquely–named data set in the SAS WORK library (to avoid causing a lock for another, subsequent request). For example:

       /* Create a Unique data set name */        
   data _null_;  
     rand = ranuni(0) * 100000000;
     ds_name = "tmp" || trim(left(put(rand,8.)));  
     call symput("ds_name", ds_name);   
   run;

   proc sql;
     create table work.&ds_name   /* <-- Note the unique name. */
       as select name, age, height, weight
       from sashelp.class;
   quit;

Operating System and Release Information

A fix for this issue for Base SAS 9.21_M3 is available at:

A fix for this issue for Base SAS 9.3_M1 is available at: