If the Stored Process Server does not start when a request is
submitted but does create a log file, follow these tips to add extra
debug information to the Stored Process Server log file to help
diagnose your problem.

   1.)  Specify the "applevel=3" option as an "Object Server Parameter"
        for your Stored Process Server.  Here are the steps.

        a.) In your SAS Management Console, under "Server Manager"
            select:

            SASMain -> "SASMain Logical Stored Process Server"
                    -> "SASMain - Stored Process Server"

        b.) Right click on "SASMain - Stored Process Server" and
            select "Properties".  Select the "Options" tab.

            In the "Options" window, under "Object Server Parameters"
            specify:

            applevel=3

        c.) Click "OK" to save the modification.

   2.)  Modify the SAS configuration file for your Stored Process
        Server.  The file is usually called "sasv9_StorProcSrv.cfg"
        and it should be located at a path that is similar to the
        following:

 C:\SAS\<project>\Lev1\SASMain\StoredProcessServer\sasv9_StorProcSrv.cfg

        Add the following line as the last line in your
        "sasv9_StorProcSrv.cfg" file:

        -verbose

        Save your "sasv9_StorProcSrv.cfg" file changes.

   3.)  You can specify a SAS autoexec to run at start up time
        before the Stored Process Server is actually launched.
        This autoexec file can contain additional debugging
        SAS code.  Here are the steps.

        a.)  Add the following line at the end of your
             "sasv9_StorProcSrv.cfg" file (after the "-verbose"
             line that you added in the above step). This should
             be on ONE LINE (it is on two lines below for readability).

             -autoexec   C:\SAS\<project>\Lev1
                      \SASMain\StoredProcessServer\autoexec_stp.sas

             You will need to modify the above "autoexec" line to
             specify the location of your site-specific
             "autoexec_stp.sas" file.

        b.)  Create your "autoexec_stp.sas" file.  Then, add your
             debugging code.  For example, see the sample
             "autoexec_stp.sas" file at the bottom of the SAS Note.

   4.) Restart your SAS Object Spawner.  For example:

       Start -> Programs -> SAS -> <your project>
             -> Restart SAS Object Spawner

   5.) Submit a request to your Stored Process Server.

   6.) Check your Stored Process Server log file.

        This file should be located at a path that is similar to
        the following:

        C:\SAS\<your project>\Lev1\SASMain\StoredProcessServer\logs\

        This log file should contain the additional debugging
        information that you specified.

   7.) If the Stored Process Server does not create a log file,
       then (on Windows) check the "Windows Event Viewer" and look
       for error messages. Also, (on Windows) check the "Documents and
       Settings" directory for the userid under which your Stored
       Process Server is running and look for a log file that may
       contain error messages. For example, check:  C:\Documents and
       Settings\sassrv\

       Check to be sure the sassrv user account has privileges
       to write to log file directory.

NOTE:  You can use a similar approach to provide debugging information
       for your Workspace server.  By default, the Workspace server
       does not create a log file.  You can create a log by specifying
       the log file name on the "-log" option on the "Command" line for
       your Workspace Server in you SAS Management Console.  Similarly,
       add the "-autoexec" option to specify an autoexec file.

Below is a sample "autoexec_stp.sas" file.

    /* Sample "autoexec_stp.sas" file  */
   proc options group=meta;    /* Show metadata options */
   run;
      /* List Windows Environment Variables */
   %macro listenv(var);
      %let varvalue = %sysfunc(sysget(&var));
      %put &var = &varvalue;
   %mend listenv;
   %put Windows Environment Variables; %put;
   %listenv(username);

Operating System and Release Information