The following error message might appear in the SAS Object Spawner log file if the SAS Object Spawner is unable to start the SAS® Stored Process Server:
An error occurred while server (xxxxxx) was starting.
Now attempting a different server.
If you encounter this problem, then check to see if a SAS Stored Process Server log file was created. This file should, by default, be located in the following directory:
.../SASApp/StoredProcessServer/logs/
If a SAS Stored Process Server log file exists, then check the most recent log file for error messages. For more information about logging, see Usage Note 34114, "Creating a detailed SAS Stored Process Server log by default."
If a SAS Stored Process Server log file was not created, make sure that the SAS General Server login account (by default it is sassrv) has permission to write to the SAS Work library as well as permission on the operating system to write to the log directory. This directory is usually located at:
As a troubleshooting test, try running the SAS Stored Process Server startup script manually. Then, check the log file for error messages. The purpose of this test is not to actually start the SAS Stored Process Server. The purpose is to see whether error messages are issued when the script is executed. To run the SAS Stored Process Server manually, follow these steps:
> runas /user:sassrv cmd
3. Go to the following directory:
.../Lev1/SASApp/StoredProcessServer/
4. On the Windows operating system do the following:
> Test_StoredProcessServer.bat
5. On UNIX, execute the StoredProcessServer.sh script:
6. After you execute the script file, a log file should be created at:
Check the log file and look for error messages.
For more information, see Usage Note 18215, "Tips for troubleshooting problems when running SAS® Stored Processes using the SAS Stored Process Web Application."