When you attempt to connect to SAS clients, such as SAS Enterprise Guide and SAS^® Data Integration Studio, that use grid-launched workspace servers, you might see a dialog box indicating that a connection could not be made. 

In SAS Enterprise Guide, this problem occurs when you connect to SASApp or you attempt to run your code or project. The action fails and the following message appears:

In SAS Data Integration Studio, this problem occurs when you run your job. The job fails and the following message appears:

Here are additional symptoms that you might encounter on the SAS server that you are attempting to connect to:

• On Windows operating systems, a Load Sharing Facility (LSF) job is launched, but exits with "Exited with exit code 116."
• On UNIX operating systems, no LSF job is launched, and the object spawner log shows an access violation similar to the following:

• Under UNIX, the object spawner stops responding.

The issue occurs under the following conditions:

• The same option name is present in both the default grid options and the grid option set used by the client application.
• The duplicated option requires a value, -option-name option-value. 
• Another option that requires no value is listed .

Workaround

The workaround is to remove any duplicated dafault SAS options from the Grid Server Properties and enter them into the SAS^® Workspace Server's sasv9_usermods.cfg file under SAS-configuration-directory/Lev1/SASApp/WorkspaceServer.

For example, if -NOOVP -MEMSIZE 2G is in the default SAS options, and -FULLSTIMER -MEMSIZE 16G is in the grid option set, then you would complete the following steps to address the problem:

1. Open SAS^® Management Console. 
2. Select Environment Management ► Server Manager. 
3. Locate the correct application server (in this example, it is SASApp).
4. Select SASApp - Logical Grid Server ► SASApp - Grid Server.
5. Review the properties and make any necessary changes. In this example, you would remove -MEMSIZE 2G from SAS options, and add it to sasv9_usermods.cfg file. 
6. On UNIX operating systems, there is an additional step. You must stop and start your object spawner. If the object spawner does not stop promptly, repeat the stop command twice more. No other users will be able to make connections to servers started by this object spawner until you restart it.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for Threaded Kernel IOM 9.4_M4 is available at:

A fix for this issue for Base SAS 9.4_M3 is available at: