SAS® Stored Processes do not complete successfully under the following conditions:
When you encounter this problem, the execution server for the stored process (SAS Stored Process Server or SAS® Workspace Server) stops responding. You must manually terminate unresponsive stored process servers and workspace servers.
Follow these steps to identify and terminate the unresponsive servers:
SAS-configuration-directory/Lev1/ObjectSpawner/ObjectSpawner.sh
From a system prompt, change directories to where the ObjectSpawner.sh script is located and submit the following:
prompt> ObjectSpawner.sh stop
2. Search for remaining SAS processes that still persist after you terminate the object spawner:
prompt> ps -ef | grep "StoredProcessServer"
prompt> ps -ef | grep "WorkspaceServer"
3. Stop the unresponsive processes.
prompt> kill <process ID#>
4. Restart the object spawner.
SAS-configuration-directory/Lev1/ObjectSpawner/ObjectSpawner.sh
From a system prompt, change directories to where the ObjectSpawner.sh script is located and submit the following:
prompt> ObjectSpawner.sh start
5. Clean up leftover Work library files. These files accumulate as a result of abnormal termination of the stored process server and workspace server sessions.
For SAS releases earlier than SAS 9.4 TS1M2, use the SAS Disk Cleanwork Handler. For further information about this program see SAS Note 8786, "SAS® Disk Cleanup Handler replaces a SAS® 9.1 program called cleanworkpc.sas to clean work directories on Windows systems."
To avoid this problem, do not configure a stored process that uses the File Upload feature to execute in background mode.
For more information about using the File Upload feature of the SAS Stored Process Web Application, refer to the Uploading Files section of SAS® 9.4 Stored Processes: Developer's Guide, Third Edition.