When the SAS Object Spawner attempts to start the SAS^® Stored Process Server, the following error message appears in the object-spawner log file if the launch time exceeds the SAS Stored Process Server Launch Timeout value:

Objspawn was unable to launch the server SASApp - Stored Process Server (xxxxxxxx.xxxxxxxx)
due to the server launch exceeding the specified wait time.

If you encounter this problem, try these troubleshooting solutions:

1. Increase the Launch Timeout value for the SAS Stored Process Server, as follows:
1. Under Server Manager in SAS^® Management Console, select SASApp - Stored Process Server ► Properties ► Options ► Advanced Options ► Load Balancing.
2. On the Load Balancing tab, increase the value for Launch timeout (sec). The default value is 60 seconds. For troubleshooting, increase the value to at least 300 seconds (5 minutes).
3. Restart the SAS Object Spawner to activate the change.
2. Turn on more logging for your SAS Stored Process Server.
   1. Follow the steps in SAS Note 34114, "Creating a detailed SAS^® Stored Process Server log by default" to create your server log. When you modify the logconfig.track.xml file In step 2, be sure to change the value for App.Program logger from Fatal to Info, as described in the note.
   2. Restart the SAS Object Spawner to activate the change.
3. After making the changes in the previous steps, submit a SAS Stored Process request.
4. Examine the SAS Stored Process Server log file. Especially note the time stamps in the log and the elapsed time that occurs as the SAS Stored Process Server starts up. In addition, look for steps that execute slowly.

When you examine the time stamps in the SAS Stored Process Server log file, you should be able to identify the cause of the slow startup time. The SAS Stored Process Server can start slowly as a result of any of the following scenarios:

• A problem with one or more pre-assigned libraries might cause the libraries to be allocated slowly.

  If there is a problem with a library, the allocation might fail after an extended period of time.

  You can define pre-assigned libraries in metadata or in the SAS Stored Process Server autoexec file.

• A slow-running autoexec for the SAS Stored Process Server can cause problems.

  If the SAS Stored Process Server autoexec file has a problem executing code (or if the code executes slowly) the stored-process server can start slowly.

After you solve the problem, you might want to change the Launch Timeout back to a lower value. Then, modify the logconfig.trace.xml file and change the App.Program logger from Info to Fatal.

Operating System and Release Information