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:

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:

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

A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

A fix for SAS 9.1.3 (9.1 TS1M3) with Asian Language Support (DBCS) for this issue is available at: