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

WARNING: Shell escape is not valid in this SAS session.

ERROR: Physical file does not exist, [path
  and name of the xparseLOG file].

exception.server.TEXTAPIJAVA.TEXT_XPARSE_1000

To work around the problem, include -xcmd and -noxwait in the Workspace Server launch command, and modify the Object Spawner controls by adding the invocation parameter -allowxcmd to the object launch.

Edit the SAS command for the Workspace Server:

1. From within the SAS^® Management Console, expand levels under the Server Manager plugin to fully expand all three levels of SASMain.
2. Highlight the lowest level, SASMain - Workspace Server. Using the right mouse button, select Properties.
3. Select the Options tab, then evaluate the Command field to determine if the options -xcmd and -noxwait are already listed. If not, add them to the very end of the command line. E.g.

   sas -config "c:\SAS\EMiner\Lev1\SASMain\sasv9.cfg" -xcmd -noxwait

4. Select OK to save changes.

Modify the Object Spawner start-up script:

1. Stop the Object Spawner by stopping the service or canceling the script.
2. Back up the ObjectSpawner.bat file, then open it for editing using a plain text editor such as Microsoft Notepad. This file is located within the application server directory, typically "C:\SAS\EMiner\Lev1\SASMain\ObjectSpawner."
3. Evaluate the three lines beginning with the string start /b. If -allowxcmd is not listed on each of the three lines, insert it prior to the -OMRconfigfile option on any/all of the command lines.
4. Save changes to ObjectSpawner.bat
5. If you installed the Object Spawner as a Windows service (the recommended option during installation), you will need to re-install the Windows service following steps 6-8. Otherwise, skip to step 9.

   To determine if the Object Spawner is a service, look for the service name beginning SAS Lev1 OB in the Windows services listing. You can open the Windows services listing by selecting the Windows Start button, then clicking the Run button.

   Type:

   services.msc
   

   then click Ok. The service name is typically SAS Lev1 OB - EMiner, though the name might differ depending on your installation.

6. In a command window, change to the Object Spawner directory within your application server directory. E.g. C:\SAS\EMiner\Lev1\SASMain\ObjectSpawner
7. Type:

   objectspawner remove
   

   to remove the existing Object Spawner service.

8. Type:

   objectspawner install
   

   to install the Object Spawner as a service. The service will be defined with the new options you just added.

9. Start the Object Spawner by using the start command within the Windows services listing, or by the startup menu item: Start ► Programs ► SAS ► EMiner ► Start SAS Object Spawner.

Operating System and Release Information