When testing the Stored Process Server from the SAS Management Console
using the "Test Connection" option, the following message may be
received if the Stored Process Server can not be started:

   sam.S251.ex.msg: A problem occurred while connecting to a load
   balancing spawner. Check the spawner log for more details.

If you receive this error message, check these items:

   1.) Check your Object Spawner's log file and look for error messages
       that are associated with your Stored Process Server.  This file
       should be at a location that is similar to the following:

  <root path>/<proj name>/Lev1/SASMain/ObjectSpawner/logs/objspawn.log

   2.) In the SAS Management Console, make sure the "Launch Command"
       is correct for your Stored Process Server by following these
       steps:

       - Under "Server Manager", go to "SASMain - Logical Stored Process
         Server."
       - Then, "drill down" to "SASMain - Stored Process Server."
       - Then, select "Properties" and click on the "Options" tab.
       - Under "Launch Commands", note the value of "Command".
         Check to make sure the path and command are correct
         for this command that is used to start your Stored
         Process Server.  If a script file is specified (for example,
         "sas_SPS.sh"), then make sure the script file exists at
         the location specified.  If a configuration file is specified
         (using the "-config" option), then make sure the configuration
         file exists at this location.

       It may be helpful to view your "Instructions.html" file
       ("My Configuration Steps") and confirm that the Stored Process
       Server's "Launch" command is the same as the command that is
       specified in your SAS Management Console.

   3.) In the SAS Management Console under "User Manager", check
       the Properties of "SAS General Servers".
       - Click the "Logins" tab
       - For the "sassrv" account, make sure the "Authentication Domain"
         matches the Authent Domain for your Stored Process Server.
       - Click "Modify" and reset the password for your "sassrv" account
       - Click the "Members" tab.  Make sure
         "SAS Trusted User" is a member of "SAS General Servers"
       - Save the changes and restart your Object Spawner.

   4.) Check to make sure that the user account under which your
       Object Spawner is running has permission to execute the
       command to start your Stored Process Server.  For example,
       if your Object Spawner was started using an account called
       "Act123", then this account must have permission to execute
       the "Launch Command" that was discussed above.

       There should be a line in your Object Spawner's log file that
       indicates the account under which your Object Spawner is running.
       For example:
          "Objspawn is running under the id Act123"

   5.) Check the Stored Process Server's log file (if this file
       was created) and look for error messages.

   6.) If a Stored Process Server log file was created, but contains
       no ERROR or WARNING messages, then do the following:

       - In the SAS Management Console: Under "Server Manager", go to
         "SASMain - Logical Stored Process Server."
       - Then, "drill down" to "SASMain - Stored Process Server."
       - Then, select "Properties" and click on the "Options" tab.
       - Under "Launch Commands", on the "Object Server Parameters"
         line, specify:
            applevel=3
       - Stop and restart your Object Spawner.
       - Rerun your Stored Process Server "Test Connection" test.
       - Check your Stored Process Server's log file for ERROR messages

   7.) Check to make sure the "sassrv" account (this is the account
       under which your Stored Process Server will be executing) has
       permission to read the SAS Configuration file (generally
       "sasv9.cfg"), the files and folders under the SAS root directory
       and privileges to execute the command to start SAS.  In addition,
       make sure the "sassrv" account has permission to write to the
       following locations:

       - Your Stored Process Server's log file.  This file should
         be at a location that is similar to the following:
     <root path>/<proj name>/Lev1/SASMain/StoredProcessServer/logs/

       - The SAS WORK library for your Stored Process Server

       One approach that you can use to test this, is:
       - Bring up a shell prompt that is running under the "sassrv"
         account.
       - Go to the location where the Stored Process Server's
         log file will be written.  Then, try to create a
         file at this location.  For example:
            >  echo "testing" > test.txt

         Then, go to the location where the Stored Process Server's
         SAS WORK library resides.  Try to create a file at
         this location.   The location of your SAS WORK library is
         specified in the  SAS configuration file that is used to
         start your Stored Process Server.  The "-work" option
         specifies the location.

   8.) If your Stored Process Server is running on UNIX, see SAS Note     
      SN-014764 "Tips for diagnosing Stored Process Server problems on UNIX".

   9.) For more information about this error message, see the
       following SAS Notes: SN-012303, SN-013810 and SN-012969.

Operating System and Release Information