When the SAS® Stored Process Server needs a resource that is not 
available, errors occur because the request could not be completed. 
 
If the SAS WORK library for the SAS Stored Process Server becomes 
unavailable after you have successfully started the server, the 
following error message occurs when you submit a request to the server 
using SAS® Enterprise Guide®: 
 
[ SAS Enterprise Guide ] 
 
 An error occurred executing the stored process job "&ltstp name here>" 
 The stored process library failed to provide a data set event interface 
 [ERROR] The IOM call failed 
 [ERROR] STP: The STP MVA scope for context cannot be accessed. 
 
A very similar error message occurs if you attempt to execute a stored 
process using the Stored Process Web Application or using SAS® Add-in 
for Microsoft Office. 
 
You would receive the following error message if you were running SAS 
Add-in for Microsoft Office: 
 
 Unable to execute the stored process "&ltstp name here>" 
 The stored process server [SASMain] is inaccessible. 
 [ERROR] The IOM call failed 
 [ERROR] STP: The STP MVA scope for context cannot be accessed. 
 [ERROR] Command successfully completed. 
 
For example, if the SAS WORK library for the SAS Stored Process Server 
uses temporary disk space and an administrative utility deletes old 
files from that disk space while the server is running, the error 
message will occur. 
 
As another example, perhaps the SAS WORK library is on a network drive 
that became disconnected. 
 
You can avoid this problem by using a SAS WORK library location that 
will always be available to the SAS Stored Process Server. 
 
Note: There might be additional situations that will also result in 
      the "The STP MVA scope for context cannot be accessed" error 
      message. 
 
The problem should go away if you do the following: 
 
 1. Stop your object spawner. 
 
 2. Make sure that all of your SAS Stored Process Server processes 
    have stopped.  Look for SAS processes that are running under the 
    "sassrv" (SAS general server) account.  If there are any such 
    processes running, then you can stop these unresponsive SAS 
    Stored Process Server processes by "killing" the processes.  On 
    Windows, you can use the Windows Task Manager. On UNIX, you can use 
    the "ps -ef | grep sassrv" command and the "kill" command. 
 
 3. Restart your object spawner 

Operating System and Release Information