SAS Object Spawner Messages in SAS 9.3

Here are messages that might be reported by the SAS Object Spawner and explanations to correct their cause. You will find some of these messages only in the SAS Object Spawner log. Some are error messages, and some are informational messages. For more information about changing the spawner logging level, see Configure Object Spawner Logging. If you are unable to resolve any errors, contact SAS Technical Support.

For more information or updated error messages, refer to: Object Spawner Messages.

• The object spawner is currently running in session <sessionID>.
  Explanation: The object spawner was started from a command line and is not able to launch processes because of Windows security constraints.
  Resolution: Run the spawner as a service.
• The launch of the server process failed with an unknown status code.
  Explanation: The process returned an unknown error code.
  Resolution: Contact SAS Technical Support.
• The launch of the server process failed due to an invalid or unaccessible SYSIN file.
  Explanation: The server was started with the SYSIN option, and the spawner either could not access or locate the SYSIN file.
  Resolution: Check the path to make sure that it is correct, or remove the SYSIN option.
• The launch of the server process failed due to an invalid or unaccessible AUTOEXEC file.
  Explanation: The autoexec file specified for the process is invalid or cannot be accessed.
  Resolution: Check that the autoexec file exists. Check the permissions on the file, and make sure that the server identity has access to the file.
• The launch of the server process failed due to an invalid or unaccessible LOG file.
  Explanation: The server was started with a -log option that contained a path or a file that could not be accessed by the server.
  Resolution: Check the path and make sure that it is correct and that the server identity has access to it.
• The launch of the server process failed due to a problem with the processing of the SAS logging facility configuration file (LOGCONFIGLOC).
  Explanation: The file specified for the -logconfigloc option cannot be processed. Either it is invalid, or it cannot be accessed.
  Resolution: Make sure that the server identity has access to this file, and that the filename is correct.
• The launch of the server process failed because the process ran out of memory.
  Explanation: The server has run out of memory during initialization.
  Resolution: If the server has been started with the -memsize option, either remove it, or choose a higher value.
• The launch of the server process failed because the SAS kernel could not be loaded.
  Explanation: For some reason, the SAS kernel cannot be loaded.
  Resolution: Contact SAS Technical Support.
• The launch of the server process failed due to an invalid or unaccessible PRINT file.
  Explanation: The server was started with a PRINT file that cannot be accessed.
  Resolution: Check the option to make sure that the file specified is accessible to the server identity.
• The launch of the server process failed because of a SAS kernel initialization failure.
  Explanation: For some reason, the SAS kernel cannot initialize.
  Resolution: Check the command line of the server to make sure that there are no invalid command line options. Also check any configuration files that are used to make sure that they are correct.
• The launch of the server process failed because of an invalid or unaccessible SASHELP library.
  Explanation: The SASHELP library cannot be accessed as configured.
  Resolution: Check the command line or configuration files where this library is specified and make sure that the library is accessible to the server identity.
• The launch of the server process failed because of an invalid or unaccessible SASUSER library.
  Explanation: The SASUSER library cannot be accessed as configured.
  Resolution: Check the command line or configuration files where this library is specified and make sure that the library is accessible to the server identity.
• The launch of the server process failed because of an invalid or unaccessible WORK library.
  Explanation: The WORK library cannot be accessed as configured.
  Resolution: Check the command line or config files where this library is specified and make sure that the library is accessible to the server identity.
• The launch of the server process failed because either SASUSER, SASHELP, or WORK was not defined.
  Explanation: The SASUSER, SASHELP, or WORK library was not defined.
  Resolution: Check the command line or configuration files and ensure that these libraries are defined.
• The launch of the server process failed because of the failure to load required formats.
  Explanation: SAS cannot load formats.
  Resolution: Check the configuration containing the format specification, or contact SAS Technical Support.
• The launch of the server process failed due to a site validation problem.
  Explanation: There is a problem with the server SETINIT.
  Resolution: Contact SAS Technical Support.
• The launch of the server process failed due to an invalid command line option.
  Explanation: There is an invalid command line option on the server.
  Resolution: Check the command and correct the option.
• The launch of the server process failed due to an I/O initialization failure.
  Explanation: A subsystem failed to initialize, preventing the process from handling input and output functions.
  Resolution: Contact SAS Technical Support.
• The launch of the server process failed due to the YZL subsystem failing to initialize.
  Explanation: The YZL subsystem failed to initialize.
  Resolution: Contact SAS Technical Support.
• The launch of the server process failed due to the YX subsystem failing to initialize.
  Explanation: The YX subsystem failed to initialize.
  Resolution: Contact SAS Technical Support.
• The launch of the server process failed because of an invalid or unaccessible CONFIG file.
  Explanation: The configuration file specified for the server is not accessible.
  Resolution: Make sure that the file exists and that it is accessible by the server identity.
• Spawned servers must allow for at least two threads. The specified value of 1 will be ignored, and a value of 2 will be used for THREADSMAX.
  Explanation: Servers that are spawned by the object spawner, including workspace, stored process, and pooled workspace servers must have at least two threads in order to function correctly. If the server starts with a threadsmax option of less than 2, the value will be forced to be 2.
  Resolution: Either remove the threadsmax option, or to set it to a value higher than 2.
• The version of server ServerName (MajorVersion.MinorVersion) as specified in metadata does not match the current running version (MajorVersion.MinorVersion). Some features might not be available.
  Explanation: There is a mismatch between the compiled version of the software and the major and minor values stored in the ServerName component.
  Resolution: This message does not indicate a problem, but is meant to inform you of this version mismatch. To resolve this message, update your SAS software with the latest version.
• The server ServerName (ServerOMR-ID) cannot be started with the -encryptfips option, because this version (MajorVersion.MinorVersion) does not support this option.
  Explanation: The specified server is an earlier version of SAS and does not support the -encryptfips option. The server will start, but -encryptfips is ignored. The object spawner still requires that the server use AES.
  Resolution: Update your SAS software with the latest version.
• The configuration source value conflicts with the previously specified configuration source value.
  Explanation: Multiple configuration files have been specified for the object spawner.
  Resolution: Check your configuration and ensure that only a single configuration option is used for your object spawner.
• Unable to retrieve the name definition or definitions.
  Explanation: The object or objects specified could not be found.
  Resolution: Check your configuration and command line and try again.
• The server named name is not unique to the listen port. Therefore only the first occurrence of this server will be used.
  Explanation: Two or more servers have been defined to use the same listen port. The object spawner is unable to distinguish between these two servers that are defined on the same port. Therefore, only the first server defined on this port will be used by the object spawner.
  Resolution: Check your configuration and change the port for the server listed in this message.
• Objspawn was unable to initiate the listen on port.
  Explanation: The object spawner could not listen on the specified port. In most cases this means that the port is already in use.
  Resolution: Check to see that no other application is currently using the specified port. Alternatively, update the port that the object spawner is trying to use to a port that is not currently being used.
• Port is reserved for objspawn administration and cannot be used as a server listen port.
  Explanation: The object spawner cannot use the same port for administration, also known as the operator port, and as a server listen port.
  Resolution: Check you configuration and ensure that the operator port for the object spawner and the ports for all servers are different.
• Port is reserved for objspawn to launched server communication. Therefore this server definition will not be included.
  Explanation: The specified port is being used by the object spawner for internal communication and cannot be used as a server listen port.
  Resolution: Change the specified port for this server to a different port.
• Port is reserved for UUID Generator requests. Therefore this server definition will not be included.
  Explanation: The specified port is being used by the object spawner to fulfill UUID generator requests. It cannot be used as a server listen port.
  Resolution: Update the port for the server or the UUID generator so that these services are defined on different ports.
• No configuration was specified.
  Explanation: No configuration information can be found for the object spawner.
  Resolution: Check the command line and make sure that some configuration option was specified for the object spawner.
• The SAS Metadata Server configuration file failed to process.
  Explanation: There is a problem in the object spawner's configuration file
  Resolution: Check the configuration file to make sure it is correct. Contact Tech Support for assistance.
• The metadata returned from the SAS Metadata Server was empty and failed to process. This could be due to there being no spawner definition in the metadata for this machine. Or, if the spawner name was specified, the name specified did not match any spawner definitions in the metadata. A spawner definition for this machine did not exist in the processed configuration. Objspawn cannot continue without a spawner definition. The name spawner definition did not exist in the processed configuration. Objspawn cannot continue without a spawner definition.
  Explanation: No object spawner definition can be found in the metadata.
  Resolution: Ensure that an object spawner definition exists in the metadata. If command -sasspawnercn or -sscoption is used on the command line, ensure that an object spawner definition of that name exists in the metadata.
• An unknown option name was specified
  Explanation: The specified option is unknown to the object spawner.
  Resolution: Check your command line or configuration for this option and remove it. Contact Tech Support for assistance.
• The attribute name was specified more than once. The previously specified value will be used.
  Explanation: The attribute or option was found multiple times in the configuration source. The first instance will be used.
  Resolution: Check your configuration for this attribute and only specify it once.
• The value (value) specified for the attribute name is invalid. The value must be corrected for Objspawn to initialize properly.
  Explanation: The attribute has an invalid value.
  Resolution: Correct the attribute's value and restart the object spawner.
• Objspawn encountered errors during results processing.
  Explanation: Errors occurred during the object spawner's initialization.
  Resolution: Check the object spawner's log for information about what caused the problem. Correct the problem and restart the object spawner.
• Objspawn cannot proceed with the specified Telnet administrator password. The password must be corrected for Objspawn to initialize properly. Objspawn does not allow the administrator password to be all asterisks. The password must be corrected for Objspawn to initialize properly. Objspawn does not allow the administrator password to be all asterisks. If the password is not recorded as all asterisks in the SAS Metadata Server, then the identity Objspawn used to connect to the SAS Metadata Server does not have permission to view the password value.
  Explanation: The object spawner found an operator or administrator password in its configuration that it cannot use.
  Resolution: Check the password that has been specified for the object spawner Telnet access. If this object spawner is defined in metadata, this password belongs to the user that is specified on the Initialization tab of the object spawner definition. Contact Tech Support for assistance.
• The credentials specified for the name (ID) server definition failed to authenticate. Therefore this server definition will not be included. A failure occurred during the retrieval of the authenticated credentials for the name (ID) server definition.
  Explanation: The specified credentials for the specified server cannot be authenticated. In order to avoid further errors and a possible account lockout, the object spawner will not use this definition.
  Resolution: Check the credentials that are specified for this server, and make sure that they are correct. Ensure that the user name is a valid user name for the system that you are using and that the password is valid for that user. After correcting the problem, restart your object spawner.
• The name (ID) server definition is not defined for this machine and will be ignored.
  Explanation: The server definition specified is not defined for the machine that the object spawner is currently running on. This server will not be used by the object spawner.
  Resolution: If the specified server is needed on the machine that this object spawner is running on, make sure that the server definition has this machine's name as part of its definition.
• Objspawn was unable to locate a server definition. Objspawn is exiting.
  Explanation: No valid server definition can be found by the object spawner. This might mean that some servers have configuration issues, or that the object spawner does not have any servers configured to be used.
  Resolution: Check the object spawner log and look for errors or warnings pertaining to servers that might be defined. Correct these issues and restart your object spawner. If no errors or warnings are found, make sure that your object spawner has servers associated with it.
• The cluster name (ID) is configured to use server side pooling. However, no port bank exists in this spawner to use with server side pooling.
  Explanation: The specified cluster contains a Pooled Workspace Server. For a Pooled Workspace Server to work correctly, the object spawners that are associated with the Pooled Workspace Server must contain a set of ports known as a port bank.
  Resolution: Check you object spawner definition and go to the Operator connection. From the Options tab, you will be able to add ports to the object spawner's port bank. Save your changes and restart your object spawner.
• Objspawn is unable to contact the metadata server.
  Explanation: The object spawner cannot connect to the specified metadata server in the configuration file or on the command line.
  Resolution: Make sure that the configuration file or the command line points to the correct metadata server. Also verify that the metadata server is running.
• The cluster definition name (ID) is invalid. Therefore this cluster definition will not be included.
  Explanation: Errors were found during the processing of the specified cluster.
  Resolution: Check the object spawner log for other errors related to the specified cluster. Correct these errors and restart your object spawner.
• The configuration for this spawner is invalid. Please check the configuration and try again.
  Explanation: Errors were found during the processing of the object spawner's configuration.
  Resolution: Check the object spawner log for other errors related to the spawner's configuration processing. Correct these errors and restart your object spawner.
• The machine name cannot be found. This machine will be ignored.
  Explanation: The specified machine name cannot be found. The machine might not exist, or the machine name might not be entered correctly.
  Resolution: Check the name of the machine to ensure that it is correct.
• Objspawn does not allow Telnet administrator access when the administrator password is the ASCII character specified. The Telnet administrator access will be disabled. Objspawn does not allow Telnet administrator access when the administrator password begins with the ASCII string "SASI". The Telnet administrator access will be disabled.
  Explanation: The specified password for Telnet administrative access cannot be used. The Telnet administrative interface will be disabled.
  Resolution: Change the administrative password of the object spawner, and restart the object spawner to enable Telnet access.
• The name (ID) server definition did not specify a command to use. Therefore this server definition will not be included.
  Explanation: No command was specified for the object spawner to use for this server. The server will not be used by the object spawner.
  Resolution: Specify a command for the object spawner.
• The name (ID) server definition did not contain a port or TCP/IP service name. The default port for this server class identifier will be used.
  Explanation: The specified server does not have a port or service defined. The default port for this type of server will be used.
  Resolution: Each type of server has its own default port. If a specific port is needed for this server, then specify one in the configuration.
• The name TCP/IP service name specified in the name server definition resolves to a port that differs from port specified in the name server attribute definition. Therefore this server definition will not be included.
  Explanation: There is a conflict between the port that is defined for the server and the service that is defined for the server.
  Resolution: Correct the conflict by either specifying only port or service, or by ensuring that the service resolves to the same port as defined by the port attribute.
• The name TCP/IP service name specified in the name server definition is invalid. Therefore this server definition will not be included.
  Explanation: The specified service name cannot be resolved.
  Resolution: Correct or remove the service name specification and restart your object spawner.
• The launched server definition was not found for the server with activity. The server might have completed its processing and exited. The requested server was not found. The server might have completed its processing and exited.
  Explanation: The object spawner has attempted to access a server that has already shut down.
  Resolution: None. This error might occur during the object spawner's server management. It is handled internally by the object spawner.
• Objspawn was unable to perform the requested action due to an active configuration refresh.
  Explanation: A request was made to the object spawner while it was attempting to refresh its configuration. Once the refresh is complete, requests will be allowed to be performed.
  Resolution: Once the refresh has completed, resubmit the request that received this error.
• Objspawn was unable to remove its existing configuration. The status received was status. Objspawn is terminating.
  Explanation: The object spawner was attempting to refresh itself when an error occurred. The object spawner will shut down.
  Resolution: Check the object spawner log to determine the error that caused the object spawner to shut down. It is very likely that any error that prevented the refresh from succeeding will also prevent the object spawner from restarting.
• Objspawn has lost connectivity with the server (child ID) launched on behalf of user ID.
  Explanation: A server that the object spawner has started has shut down unexpectedly.
  Resolution: This might happen sometimes due to administrative requests that are made against the servers that the object spawner has started. If these errors persist, then contact Tech Support for assistance.
• The launch of server name for user ID failed. The server failed to start. Failed to start the server.
  Explanation: The specified server failed to start. Other messages in the log might point to the cause of this failure. The typical reason for these failures is a permissions issue that is related to the server command line.
  Resolution: Depending on what operating system you are using, you might be able to find extended error information. On Windows systems, consult the Windows Event log. On z/OS systems, check the system log. On UNIX or Linux systems, messages might be written to the console, or they might exist in the objspawn_console.log. Correct the errors that are reported, and restart your object spawner if necessary.
• The peer for launched server child ID is no longer defined. The launched server will exit.
  Explanation: The peer (client) that requested the server is no longer present, and might have disconnected unexpectedly. The server that was started for this client will exit.
  Resolution: No resolution. If the message persists, there might be a problem with the client application. Contact Tech Support for assistance.
• The server definition associated with the launched server no longer exists. This might be due to an objspawn configuration refresh.
  Explanation: The object spawner is in the process of refreshing itself when it receives a request or activity for a server that it is in the process of refreshing.
  Resolution: Once the refresh has completed, the message should no longer be seen.
• The operator password specified by name is invalid.
  Explanation: An invalid password was specified to the Telnet administrative interface.
  Resolution: Use the password as defined in metadata.
• Objspawn was unable to verify that the password due to an active configuration refresh.
  Explanation: The object spawner was in the process of refreshing its configuration when a client attempted a connection to the Telnet administrative interface.
  Resolution: Once the refresh has completed, the Telnet interface will be available again.
• Objspawn was unable to generate UUIDs due to an active configuration refresh.
  Explanation: The object spawner was in the process of refreshing its configuration when a client attempted to request a UUID.
  Resolution: Once the refresh has completed, UUID generation will be available again.
• Client name does not have permission to use server name (ID).
  Explanation: The client that has connected does not have permission to use the specified server.
  Resolution: Check with your system administrator. A client must have the proper permissions on the server in order to use the server.
• Objspawn is unable to find server named name. Objspawn was unable to find the specified server name.
  Explanation: A client requested a server by name from the object spawner. The requested server is not a server that the object spawner is currently configured to use.
  Resolution: Make sure that the client application is connecting to the correct machine and is using the correct server. Also make sure that the object spawner configuration has the correct servers associated with it.
• The server requested is not configured correctly. The client request cannot be completed.
  Explanation: There was a problem with the server that the client requested, and it cannot be used by the object spawner. Check the object spawner log for errors or warnings that indicate the issue with the server.
  Resolution: Correct the server configuration and restart the object spawner. Otherwise, select a different server to use.

• There is a problem with the Negotiate Package List. Please verify that the property is set correctly. There is a problem with the Security Package. Please verify that the property is set correctly. There is a problem with the Service Principal Name. Please verify that the property is set correctly.
  Explanation: There is a problem with one of the Integrated Windows Authentication properties. These properties have certain values. Check the applicable documentation for information about these properties.
  Resolution: Correct the problems with these security properties, and restart your object spawner.
• Credentials could not be generated for user ID because spawner is not connecting to the metadata server as a trusted user. This might prevent the launched server from contacting the metadata server.
  Explanation: Servers that are launched by the object spawner attempt to connect to the metadata server in order to get further configuration information, including pre-assigned libraries and security information. In order to facilitate this, the object spawner generates credentials for the server to use to connect to the metadata server. If the object spawner is not connected to the metadata server as a trusted user, then it cannot generate credentials for other users.
  Resolution: Check the object spawner's configuration file or command line. Ensure that the user that is specified there is a trusted user. Check the security documentation for more information.

• No host credentials exist to start this server. Either the client needs to send in host credentials, or credentials need to be specified for the server. No host credentials exist to start server name (ID). Either the client needs to send in host credentials, or credentials need to be specified for the server.
  Explanation: The specified server has been configured in metadata to allow SAS Token Authentication. These servers must have credentials specified for them in metadata in order for the object spawner to use to launch them.
  Resolution: Ensure that credentials are set for the server on the Options tab. After setting the credentials, restart your object spawner.
• The spawner cannot accept a new client because it is currently in a paused state. The spawner cannot accept a new client because it is currently in a deferred shutdown state.
  Explanation: The object spawner is current in the specified state and cannot currently accept new clients.
  Resolution: If the object spawner is in a deferred shutdown state, the object spawner will soon shut down. At that time it will no longer accept clients, and must be restarted. A paused object spawner can be continued at any time. Once it is continued or resumed, it will accept clients again.
• A port could not be obtained to allow the client to be connected to this server.
  Explanation: This applies to Pooled Workspace Servers. When a client is redirected to a workspace server from a pool, the workspace server opens a port briefly for the client to use in order to connect to the server. This message indicates that at the time that a client request to the pool was made, no ports were available to have the server listen on.
  Resolution: Add more ports to the object spawner port bank.
• Objspawn encountered a failure while processing a Telnet request. The peer connection will be closed.
  Explanation: An error occurred during the processing of an administrative interface request. The interface will be closed.
  Resolution: Attempt to reconnect to the administrative interface. If the message continues, restart the object spawner, or contact Tech Support.
• Objspawn encountered a failure while processing a UUID generator request. The peer connection will be closed.
  Explanation: An error occurred during the generation of a UUID for the client.
  Resolution: Check the object spawner log for warnings or messages that can indicate the problem. Restart the object spawner if necessary. If the problem continues, contact Tech Support.
• Line line_number in the configuration file is not in LDIF format and is being skipped.
  Explanation: The specified line in the configuration file is not in the correct format and cannot be used.
  Resolution: Correct the specified line.
• The connection to the LDAP server failed.
  Explanation: The specified server in the LDAP configuration could not be accessed. The object spawner cannot obtain its configuration.
  Resolution: Check the specified LDAP server and ensure that it is running.

• The attribute_name attribute found on line line_number failed to process.
  Explanation: The specified attribute name is incorrect.
  Resolution: Correct the attribute and restart your object spawner.
• Two consecutive blank lines in an LDIF configuration file identify the logical end of the configuration. The remainder of the LDIF configuration file will be ignored.
  Explanation: The LDIF file contains two consecutive blank lines. This signifies the end of the configuration file.
  Resolution: If the rest of the file is needed, then remove one of the blank lines.
• The object class definition name contains more than one distinguished name definition. The object class definition will be ignored.
  Explanation: The specified definition contains multiple distinguished names. A definition can contain only one distinguished name.
  Resolution: Remove one of the distinguished names.
• The object class definition name contains conflicting object class identifier definitions. The object class definition will be ignored.
  Explanation: The specified definition contains multiple or incompatible class identifier definitions.
  Resolution: Correct the object class identifier in the specified definition.
• The object class definition that began on line line_number defines an unknown object class and is being ignored.
  Explanation: An unknown class identifier was used in the specified definition and must be corrected.
  Resolution: Correct the specified definition to have a known class identifier.
• The object class definition that began on line line_number contained one or more attribute resolution failures and is being ignored.
  Explanation: The specified object class definition contained one or more errors and will be ignored by the object spawner.
  Resolution: See the object spawner log and correct the errors reported. Restart the object spawner.
• Objspawn was unable to open the configuration file (name).
  Explanation: The configuration file that is specified to the object spawner cannot be located or opened.
  Resolution: Specify the correct configuration file.
• The name server definition did not specify a protocol. Therefore this server definition will not be included.
  Explanation: The server definition is missing the protocol attribute. The protocol must be set.
  Resolution: Correct the configuration by setting the protocol attribute and restart your object spawner.




Operating System and Release Information

Product Family	Product	System	SAS Release
			Reported	Fixed*
SAS System	SAS Integration Technologies	z/OS	9.3 TS1M0
		Microsoft® Windows® for x64	9.3 TS1M0
		Microsoft Windows Server 2003 Datacenter Edition	9.3 TS1M0
		Microsoft Windows Server 2003 Enterprise Edition	9.3 TS1M0
		Microsoft Windows Server 2003 Standard Edition	9.3 TS1M0
		Microsoft Windows Server 2003 for x64	9.3 TS1M0
		Microsoft Windows Server 2008	9.3 TS1M0
		Microsoft Windows Server 2008 for x64	9.3 TS1M0
		Microsoft Windows XP Professional	9.3 TS1M0
		Windows 7 Enterprise 32 bit	9.3 TS1M0
		Windows 7 Enterprise x64	9.3 TS1M0
		Windows 7 Home Premium 32 bit	9.3 TS1M0
		Windows 7 Home Premium x64	9.3 TS1M0
		Windows 7 Professional 32 bit	9.3 TS1M0
		Windows 7 Professional x64	9.3 TS1M0
		Windows 7 Ultimate 32 bit	9.3 TS1M0
		Windows 7 Ultimate x64	9.3 TS1M0
		Windows Vista	9.3 TS1M0
		Windows Vista for x64	9.3 TS1M0
		64-bit Enabled AIX	9.3 TS1M0
		64-bit Enabled HP-UX	9.3 TS1M0
		64-bit Enabled Solaris	9.3 TS1M0
		HP-UX IPF	9.3 TS1M0
		Linux	9.3 TS1M0
		Linux for x64	9.3 TS1M0
		Solaris for x64	9.3 TS1M0

* 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.