Problem

When you submit a stored process from SAS Add-In for Microsoft Office or SAS Enterprise Guide, the following error might occur:

The error occurs when a disconnect from the SAS^® Metadata Server has occurred.

And when you review the Enterprise Guide diagnostic log, you see the following error:

Workaround

For SAS^® 9.3 and Earlier

If your SAS server is 9.3 or earlier, you need to identify the cause of the disconnect and prevent the disconnect from occurring. Commonly, disconnects are caused by network devices that contain a TCP time-out setting.  This setting severs network connections that are idle for a set period of time. Work with your network team to identify the cause of the disconnect.

For SAS^® 9.4

With SAS 9.4, the KEEPALIVE object server parameter should be set on the SAS Metadata Server. The KEEPALIVE parameter sends an event packet to inactive clients on a regular interval to prevent disconnection by network firewalls.

The KEEPALIVE option can be set within a configuration file for the SAS Metadata Server.

1. Navigate to the directory where the SAS Metadata Server configuration files are located.  

• On a Windows machine:  \<SASconfig>\LevN\SASMeta\MetadataServer\ 
• On a UNIX machine:   /<SASconfig>/LevN/SASMeta/MetadataServer/

2. Make a backup copy of the SAS Metadata Server sasv9.cfg file. 
3. Modify the SAS Metadata Server sasv9.cfg file. 
   1. Locate the line that begins with this text:   -objectserverparms 
   2. On the -objectserverparms line, specify keepalive=value between two of the existing parameters.

Note: Use value to specify the number of seconds that you want the packet to be sent to the SAS client.

Here is an example: 

-objectserverparms "cel=credentials protocol=bridge port=8561 keepalive=600 classfactory=0217E202-B560-11DB-AD91-001083FF6836 trustsaspeer='Path\to\trustedPeers.xml' hostknownby='machinename'"

4. Close the sasv9.cfg file and save your changes.
5. After making the change, stop and restart your SAS Metadata Server service. If you have additional SAS services, you must stop and start all of your SAS services in the correct order.  See this Starting Servers in the Correct Order section of the SAS^® 9.4 Intelligence Platform: System Administration Guide.

Operating System and Release Information