SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 19742: An error occurs when attempting to connect to the SAS® Metadata Server and the METAUSER= system option contains an embedded space

DetailsHotfixAboutRate It

The following error occurs in a SAS session when the METAUSER= system option contains an embedded space and an Integrated Object Model (IOM) connection attempts to connect to the SAS Metadata Server:

ERROR: Missing value for outcall option XXXX.

In this message, XXXX is the string that follows a space in a user ID that contains embedded spaces. For example, metauser=<mydomain\><test userid> generates the following error message:

ERROR: Missing value for outcall option USERID.

This error occurs under the following conditions:

  • The system option METAUSER=<space-embedded-userid> is set or the user ID option or parameter is passed within a statement or procedure.
  • You assign a library in SAS® Enterprise Guide® when the authenticated user ID contains an embedded space.
  • The option is set or passed, which also causes failure of the METAOPERATE and METADATA procedures, the metadata DATA step function, and the META LIBNAME statements.
  • The ObjectSpawnerOMRConfig.xml file <Login> element contains a userID attribute with an embedded space. The ObjectSpawner will fail to start with the same error.

To circumvent this problem, do not set the METAUSER= system option with an embedded space. Instead, use pre-assigned libraries with the OBJECTSERVERPARM option METAAUTOINIT= or the system option METAAUTORESOURCES=.

You can use a META LIBNAME statement in an autoexec file, as long as the USERID= option is not specified or the METAUSER= system option is not set with user ID that contains embedded spaces. Note that this method only works when the TRUSTSASPEER functionality is in effect. TRUSTSASPEER enables peer servers that are used by a SAS metadata client to connect to the metadata server using the credentials of the connecting client. SAS applications that require this support will state the requirement in their documentation.

For more information, see "Setting up Trusted Peer Connections for SAS Sessions" in the SAS® 9.1.3 Integration Technologies Server Administrator's Guide.

Select the Hot Fix tab in this note for information on how to obtain the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemSAS Release
ReportedFixed*
SAS SystemSAS Metadata ServerMicrosoft Windows XP Professional9.1 TS1M3 SP49.2 TS2M0
Microsoft Windows NT Workstation9.1 TS1M3 SP4
Microsoft® Windows® for 64-Bit Itanium-based Systems9.1 TS1M3 SP49.2 TS2M0
Microsoft Windows XP 64-bit Edition9.1 TS1M3 SP49.2 TS2M0
Microsoft Windows Server 2003 Standard Edition9.1 TS1M3 SP49.2 TS2M0
Microsoft Windows Server 2003 Enterprise Edition9.1 TS1M3 SP49.2 TS2M0
Microsoft Windows Server 2003 Datacenter Edition9.1 TS1M3 SP49.2 TS2M0
Microsoft Windows 2000 Server9.1 TS1M3 SP49.2 TS2M0
Microsoft Windows 2000 Datacenter Server9.1 TS1M3 SP49.2 TS2M0
Microsoft Windows 2000 Professional9.1 TS1M3 SP49.2 TS2M0
Microsoft Windows 2000 Advanced Server9.1 TS1M3 SP49.2 TS2M0
Solaris for x649.1 TS1M3 SP49.2 TS2M0
64-bit Enabled Solaris9.1 TS1M3 SP49.2 TS2M0
z/OS9.1 TS1M3 SP49.2 TS2M0
Linux9.1 TS1M3 SP49.2 TS2M0
Linux on Itanium9.1 TS1M3 SP49.2 TS2M0
HP-UX IPF9.1 TS1M3 SP49.2 TS2M0
64-bit Enabled HP-UX9.1 TS1M3 SP49.2 TS2M0
OpenVMS Alpha9.1 TS1M3 SP49.2 TS2M0
64-bit Enabled AIX9.1 TS1M3 SP49.2 TS2M0
Tru64 UNIX9.1 TS1M3 SP49.2 TS2M0
* 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.