Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

If the SAS^® Stored Process Server does not start successfully on a UNIX machine when a request is submitted, follow these tips to help diagnose the problem.

1. Try running the Test Connection SAS Stored Process Server test from the SAS^® Management Console under Server Manager by following these steps.
   1. Click SASMain – Stored Process Server.
   2. In the right–hand window, right–click the Connection SASMain Stored Process Server bridge connection.
   3. Select Test Connection.
2. Check your SAS Object Spawner's log file and look for error messages that are related to your SAS Stored Process Server request. By default, this log file will be written to:
   <project path>/Lev1/SASMain/ObjectSpawner/logs/objspawn.log
3. Check your Object Spawner's "console" log file and look for error messages that are related to your SAS Stored Process Server request. By default, this log file will be written to:
   <project path>/Lev1/SASMain/ObjectSpawner/logs/objspawn_console.log
4. Check your SAS Stored Process Server's log file (if it exists) and look for error messages. The path should be similar to the following:

   <project path>/Lev1/SASMain/StoredProcessServer/logs/
   

5. The SAS Stored Process Server runs under the "sassrv" user account (the "SAS General Servers" login account). So, this account must have the proper permissions to start the SAS Stored Process Server. For example, the "sassrv" account needs permission to write to the "StoredProcessServer/logs" directory; to access the SAS configuration file; to access the SASUSER directory, to write to the SAS WORK library; and permission to execute the "sas_SPS.sh" script that is used to start the SAS Stored Process Server. The "sassrv" account also needs permission to write to the UTILLOC directory (where application utility files are stored) that is specified in the UTILLOC= system option.

6. Log on to your UNIX machine using the "sassrv" user account. Open a UNIX shell and use the CD command to change to your "SASMain/StoredProcessServer" directory. For example, this directory should be at a location similar to the following:

   <project path>/Lev1/SASMain/StoredProcessServer
   

   Then, execute the "sas_SPS.sh" script directly. This is the same script that the SAS Object Spawner uses when starting the SAS Stored Process Server. If you can successfully run the "sas_SPS.sh" script in this manner, then the SAS Object Spawner should also be able to execute it successfully.
7. Make sure you specified the correct password for your "sassrv" account in your SAS Management Console. Under User Manager, select SAS General Servers and then click the Logins tab.
8. The SAS Object Spawner will fail to start a SAS Stored Process Server on UNIX when the number of groups in which the "sassrv" user ID is a member exceeds NGROUPS_MAX. For more information, see SAS Note 17533.
9. If the SAS Object Spawner attempts to launch the SAS Stored Process Server, but cannot, you will see the below WARNING message in your SAS Object Spawner's log file:

   WARNING: An error occurred while server (xxxxxxxx.xxxxxxxx)
            was starting.  Now attempting a different server.
   

   Here are some tips for diagnosing this problem.
   1. If your SAS Stored Process Server was running successfully in the past, but fails today, then you might have a "hung" SAS Stored Process server. In this case, restart your SAS Object Spawner and try your test again. If the problem still exists, then check for "hung" SAS Stored Process servers that may still be running and "kill" them. See SAS Note 17488.
   2. See Items 5, 6, 7 and 8 above.
   3. You can set the "ELSDEBUG" environment variable for the SAS Object Spawner and this will provide more detailed information about the cause of the problem.
      1. Modify your "ObjectSpawner.sh" script. Add the following statement near the top of this file:
         export ELSDEBUG=70656e64
      2. Restart your SAS Object Spawner.
      3. Run your SAS Stored Process Server test.
      4. Check your "objspawn_console.log" file for messages.

10. Try running the Test Connection; Workspace Server test from the SAS Management Console under Server Manager plug–in by following these steps:

    1. Click SASMain – Workspace Server.
    2. In the right–hand window, right–click the Connection SASMain Workspace Server bridge connection.
    3. Select Test Connection.
    4. When you are prompted for a user ID, enter "sassrv".

       If this test fails for "sassrv", but is successful for other accounts, then "sassrv" probably does not have sufficient permissions to run the SAS Workspace Server or SAS Stored Process server.

11. Check your "sas_SPS.sh" script file (see "Item 5" above) and make sure that the first line is:
    #!/bin/sh

Operating System and Release Information