When you run a program in SAS Enterprise Guide, the following errors might appear in the program log:
SDS Failed to provide the decoder for the data set. Call to GetMetadataObjects failed
A workaround is to enable the KEEPALIVE option in SAS® Metadata Server.
Enabling KEEPALIVE on the SAS Metadata Server
You can set the KEEPALIVE option within a configuration file for SAS Metadata Server by completing these steps:
1. Go to the directory where the SAS Metadata Server configuration files are located:
Microsoft Windows:
\SAS-configuration-directory\LevN\SASMeta\MetadataServer\
UNIX:
/SAS-configuration-directory/LevN/SASMeta/MetadataServer/
2. Open the sasv9.cfg file and find the line that begins with this text:
-objectserverparms
3. Copy the entire -objectserverparms line.
4. Open the sasv9_usermods.cfg file from the same directory.
5. Add the entire -objectserverparms line that you copied from the sasv9.cfg file to the sasv9_usermods.cfg file.
6. On the -objectserverparms line in the sasv9_usermods.cfg file, specify keepalive=value between two of the existing parameters.
Note: When you specify value, use the time (in seconds) when you want the packet to be sent to your firewall.
Here is an example:
-objectserverparms "cel=credentials protocol=bridge port=8561 keepalive=30 classfactory=0217E202-B560-11DB-AD91-001083FF6836 trustsaspeer='Path\to\trustedPeers.xml' hostknownby='machinename'"
7. Close the sasv9_usermods.cfg file and save your changes.
8. Restart both the Metadata Server service and Object Spawner service.
9. If you have additional SAS services, restart them.
Note: You must stop and start all of your SAS services.
For guidance about starting services in the correct order, see Starting Servers in the Correct Order.
Hot Fix
If enabling the KEEPALIVE option for SAS Metadata Server does not resolve the issue, you need to install the hot fix in this SAS Note.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| SAS System | SAS Enterprise Guide | Microsoft® Windows® for x64 | 8.4 | | 9.4 TS1M8 | |
| Microsoft Windows 8 Enterprise 32-bit | 8.4 | | 9.4 TS1M8 | |
| Microsoft Windows 8 Enterprise x64 | 8.4 | | 9.4 TS1M8 | |
| Microsoft Windows 8 Pro 32-bit | 8.4 | | 9.4 TS1M8 | |
| Microsoft Windows 8 Pro x64 | 8.4 | | 9.4 TS1M8 | |
| Microsoft Windows 8.1 Enterprise 32-bit | 8.4 | | 9.4 TS1M8 | |
| Microsoft Windows 8.1 Enterprise x64 | 8.4 | | 9.4 TS1M8 | |
| Microsoft Windows 8.1 Pro 32-bit | 8.4 | | 9.4 TS1M8 | |
| Microsoft Windows 8.1 Pro x64 | 8.4 | | 9.4 TS1M8 | |
| Microsoft Windows 10 | 8.4 | | 9.4 TS1M8 | |
| Microsoft Windows 11 | 8.4 | | 9.4 TS1M8 | |
| Microsoft Windows Server 2008 | 8.4 | | 9.4 TS1M8 | |
| Microsoft Windows Server 2008 R2 | 8.4 | | 9.4 TS1M8 | |
| Microsoft Windows Server 2008 for x64 | 8.4 | | 9.4 TS1M8 | |
| Microsoft Windows Server 2012 Datacenter | 8.4 | | 9.4 TS1M8 | |
| Microsoft Windows Server 2012 R2 Datacenter | 8.4 | | 9.4 TS1M8 | |
| Microsoft Windows Server 2012 R2 Std | 8.4 | | 9.4 TS1M8 | |
| Microsoft Windows Server 2012 Std | 8.4 | | 9.4 TS1M8 | |
| Microsoft Windows Server 2016 | 8.4 | | 9.4 TS1M8 | |
| Microsoft Windows Server 2019 | 8.4 | | 9.4 TS1M8 | |
| Microsoft Windows Server 2022 | 8.4 | | 9.4 TS1M8 | |
| Windows 7 Enterprise 32 bit | 8.4 | | 9.4 TS1M8 | |
| Windows 7 Enterprise x64 | 8.4 | | 9.4 TS1M8 | |
| Windows 7 Home Premium 32 bit | 8.4 | | 9.4 TS1M8 | |
| Windows 7 Home Premium x64 | 8.4 | | 9.4 TS1M8 | |
| Windows 7 Professional 32 bit | 8.4 | | 9.4 TS1M8 | |
| Windows 7 Professional x64 | 8.4 | | 9.4 TS1M8 | |
| Windows 7 Ultimate 32 bit | 8.4 | | 9.4 TS1M8 | |
| Windows 7 Ultimate x64 | 8.4 | | 9.4 TS1M8 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.