If a client is unable to start a Workspace or Stored Process Server, you
may find the following error in the Object Spawner log:

   ERROR:  An unexpected error has prevented transfer of handles between
           processes

The Event Viewer may contain information pertaining to the errors. Under
the Application section of the Event Viewer you may see a Warning for
the SAS application for the client userid.  Open the event to find
reference to a log file that should give you a SAS error to help debug
this issue.  These logs are normally located in "C:\Documents and
Settings\userid\Application Data\SAS\LOGS".

The error above will occur for any instance in which the SAS session was
unable to start.  For example, when the client user does not have
appropriate rights or permissions on the SAS server machine. This could
be authority to write to the Work, sasuser or logs subdirectory.  Check
NTFS permissions.  It could also occur due to an invalid statement or
comment in the SASV9.CFG file.  An invalid comment can be a asterisk on
a line.  A proper comment in the SASV9.CFG file needs to be delimited by
/* */.

One technique to determine if SAS can be started by the user, is to use
the RUNAS command on Windows or the SU command on UNIX.

Example:
  runas /user:sasdemo cmd

After giving the password for the userid, a DOS window will open.  Now
run in that window, the exact SAS invocation command that you have
specified in your server startup command.

Operating System and Release Information