The following exception might be returned to the client or written to the SAS Object Spawner log when a SAS Workspace Server fails to launch:

ERROR: The child process terminated before accepting the transfer of open handles. 
The child process terminated with exit status 0x2331. The Windows Event log may 
be helpful in determining the reason that the child process terminated prematurely.

The exit status 0x2331 (Error 9009) means that the program is not recognized as an internal or external command, an operable program, or a batch file.

Common reasons for this error are as follows:

• an invalid path to the WorkspaceServer.bat file
• an invalid path to the SAS executable file that is executed by the WorkspaceServer.bat file
• lack of permissions to execute the WorkspaceServer.bat file or the SAS executable file.

To fix the problem, you need to determine the specific reason for the error. You can obtain more information about the cause of the problem by checking the Microsoft Windows Event Application log for a corresponding SAS error. Once you determine the specific cause, you can take steps to fix the problem (that is, fix the invalid paths or permissions).

Note: If Microsoft Windows security policies are in place, SAS might be prevented from writing to the Event Application log. If that happens, perform the following steps for additional troubleshooting:

1. Submit the following command from a cmd.exe session and specify a failing user ID for domain\user-name:
   runas /user:domain\user-name cmd.exe
   *Enter the password for the user ID when you are prompted. Perform remaining steps in the new cmd.exe session.
   *If the cmd.exe session cannot be opened for a failing user then start a cmd.exe session as an admin user and perform the remaining steps.  
2. Change the directories to the <SASCONFIG>\Lev1\SASApp\WorkspaceServer directory. 
3. Change @echo off to @echo on at the top of the WorkspaceServer.bat file.
4. Execute cmd /k WorkspaceServer.bat.
5. Change @echo off to @echo on in the last file sourced and complete step four again. Continue this process until all invalid paths are found, corrected, and a SAS session is successfully started.  

Operating System and Release Information