• Print  |
  • Feedback  |

SAS 9.1.3 Integration Technologies » Server Administrator's Guide


Setting up a Server and Spawner
Best Practices
Quick Start: Standard Workspace Server and Spawner
Quick Start: Load-Balancing Stored Process Server and Spawner
Summary of Setup Steps
Spawner Overview
Spawner Requirements
Planning the Configuration Metadata
Security
Standard Workspace or Stored Process Server
Standard OLAP Server
Creating the Metadata Using SAS Management Console
Defining Servers
Modifying Servers
Workspace or Stored Process Server
OLAP Server
Configuring a UUID Generator
Configuring and Starting the Object Spawner on z/OS
Administering the Server and Spawner
Creating a Metadata Configuration File in SAS
Using ITConfig
Testing Server Connections
Using Telnet
Spawner Error Messages
Reference Materials
Fields for the Server Definition
Object Server Parameters
Fields for the Spawner Definition
IOM Bridge

Spawner Error Messages

Here are error messages that might be reported by objspawn and explanations to correct their cause.

If you are still unable to correct the error, you might want the spawner to begin tracing its activity. See the administrator command section or use the -slf option to specify a log file when launching the spawner. For details, see Invoking (Starting) the Spawner.

Note: If an error occurs when the -slf option is not in effect, the spawner sends error messages to the SAS Console Log. This is a host-specific output destination. For details about the SAS Console Log, see the SAS Companion for your operating environment.

[Service Name] is already installed as a service. Deinstall the service, then reissue the install request
Host: Windows
Explanation:
The spawner is already installed as a service.
Resolution:
Deinstall the spawner then reissue your install command.
A client that does not support redirection has connected to a server that requires redirection. The client connection will be closed.
Host: All
Explanation:
A down level IOM Bridge for Java client is attempting to connect to a server that has been defined within a load balancing cluster.
Resolution:
Upgrade the client's IOM Bridge for Java support.
A duplicate configuration option [duplicated option] was found.
Host: All
Explanation:
The displayed option was specified more than once.
Resolution:
Remove the redundant option and reissue your command.
A true socket handle cannot be obtained.
Host: All
Explanation:
The spawner was unable to retrieve the TCP/IP stack socket identifier from the runtime.
Resolution:
Contact SAS Technical Support.
A valid sasSpawner definition cannot be found.
Host: All
Explanation:
The spawner failed to find the named spawner definition. Or, if no name was given, a spawner definition that referenced the host in which the spawner is executing.
Resolution:
If a spawner name was specified at invocation, ensure the name is correct. Otherwise, correct the configuration source to define a valid spawner containing the correct host name.
Also known as:
Host: All
Explanation:
The host in which objspawn is executing is also known under the aliases listed.
Resolution:
N/A
An accepted client connection cannot be registered.
Host: All
Explanation:
The spawner was unable to place the socket associated with a connected client in a select.
Resolution:
Review the spawner log file to determine if the spawner is resource constrained. Ensure the client is still connected.
An attempt to communicate with the SAS Metadata Server failed. The error text associated with the failure is [error text describing failure].
Host: All
Explanation:
The spawner was unable to contact the SAS Metadata Server defined in the specified SAS Metadata Server configuration file.
Resolution:
Ensure that the SAS Metadata Server defined in the SAS Metadata Server configuration file is defined correctly and contains proper credentials. Also ensure that target SAS Metadata Server is running.
An error occured while server [server name] was starting. Now attempting a different server.
Host: All
Explanation:
The load balancing implementation failed to connect to the server and will attempt to connect to a different server.
Resolution:
Ensure that the server port is not already in use.
An NLS pipeline ([encoding identifier] -to- [encoding identifier]) cannot be created.
Host: All
Explanation:
The spawner was unable to initialize an internal transcoding object.
Resolution:
Ensure the SAS installation is complete and correct.
An unexpected error has prevented transfer of handles between processes.
Host: Windows
Explanation:
The SAS process failed to complete its startup.
Resolution:
Check your Windows event log for a warning for the SAS application. The warning should direct you to a log file that explains why SAS failed to start.
An unknown option ([option name]) was specified.
Host: All
Explanation:
The spawner encountered an invocation option that is invalid.
Resolution:
Remove the invalid option and reissue the spawner command.
An unsupported UUID request version ([invalid version]) was received.
Host: All
Explanation:
A connection to the UUID listen port/service specified an invalid UUID protocol version.
Resolution:
Ensure that the IOM server clients are not connecting to the wrong port/service.
Cannot install objspawn with the NOSECURITY option.
Host: Windows
Explanation:
Due to the security exposure associated with the nosecurity option, the spawner will not install as a Windows service when nosecurity is specified.
Resolution:
Remove the nosecurity option and reissue the install command.
Communication cannot be established with the launched session.
Host: All
Explanation:
The spawner was unable to forward client information to the IOM server launched on behalf of the client.
Resolution:
Contact SAS Technical Support.
Configuration source ([source]) conflicts with the previously specified configuration source ([source]).
Host: All
Explanation:
More than one configuration source was specified.
Resolution:
Determine which configuration source is correct and remove the others from your spawner invocation.
Failed to launch the server ([server name]) on behalf of load balancing.
Host: All
Explanation:
The load balancing implementation requested that the spawner launch an IOM server. The spawner was unable to launch the named server.
Resolution:
Ensure that the server start command is correct. Also ensure that there is not a port/service conflict.
Failed to locate the server ([server name]) to launch on behalf of load balancing.
Host: All
Explanation:
The load balancing implementation requested that the spawner launch an IOM server. The spawner was unable to locate the named server definition.
Resolution:
Ensure that the load balancing cluster is defined correctly.
Failed to locate the server indicated in the kill request.
Host: All
Explanation:
The load balancing implementation requested that a server be stopped. The spawner was unable to locate the server in which to stop.
Resolution:
N/A
Invalid request to authenticated server
Host: UNIX
Explanation:
The object spawner failed to launch an authenticated server.
Resolution:
If you have SAS 8 and SAS 9 on the same machine, ensure that the SAS 8 directory is not part of your system path ($PATH).
Load Balancing did not authorize server [server] to start and is disregarding the AddServer request.
Host: All
Explanation:
The spawner is using Load Balancing and started a server without Load Balancing instructing it to do so. This request is thrown out and the spawner should continue to function.
Resolution:
Review the configuration via SAS Management Console to ensure that all servers are set up correctly.
No configuration was specified.
Host: All
Explanation:
The spawner was invoked without a configuration source.
Resolution:
Reissue spawner command with a configuration source.
Objspawn cannot be deinstalled.
Host: Windows
Explanation:
The spawner was unable to deinstall as a Windows service.
Resolution:
Review the spawner log file to determine the cause of failure. Ensure the spawner is currently installed as a Windows service.
Objspawn cannot be installed.
Host: Windows
Explanation:
The spawner was unable to install as a Windows service.
Resolution:
Review the spawner log file to determine the cause of failure. Ensure the spawner is not currently installed as a Windows service.
Objspawn encountered [number of errors] error(s) during command-line processing.
Host: All
Explanation:
The spawner was unable to start.
Resolution:
Reissue the spawner invocation command with a valid log file destination. Review the contents of the generated log file to determine why the spawner failed to start.
Objspawn encountered errors during results processing.
Host: All
Explanation:
The spawner was unable to complete configuration processing.
Resolution:
Review the spawner log file to determine the configuration error details.
Objspawn encountered errors while attempting to start. To view the errors, define the DD name TKMVSJNL and restart objspawn with the sasVerbose option.
Host: z/OS
Explanation:
The spawner encountered errors and was unable to start.
Resolution:
Define the DD name TKMVSJNL and restart objspawn with the sasVerbose option to create a log file. Review the contents of the log file to determine why the spawner failed to start.
Objspawn encountered errors while attempting to start. View the application event log for the name of the log file containing the errors.
Host: Windows
Explanation:
The spawner encountered errors and was unable to start.
Resolution:
View the application event log to determine the name of the log file. Review the contents of the log file to determine why the spawner failed to start.
Objspawn failed to reinitiate multiuser server listen. Objspawn is removing server definition.
Host: All
Explanation:
The spawner was unable to restart a multi-user server listen when the previously launched multi-user server exited.
Resolution:
Ensure that there is not a port/service conflict.
Objspawn has completed initialization.
Host: All
Explanation:
The spawner is operational.
Resolution:
N/A
Objspawn has detected a bridge protocol over the operator conversation socket. Objspawn is closing the operator conversation with the peer (%s).
Host: All
Explanation:
An IOM Bridge client has connected to the operator listen port/service instead of a port/service belonging to a server definition.
Resolution:
Update the client to connect to the proper server definition port/service.
Objspawn is being terminated by the operating system.
Host: z/OS
Explanation:
The operator or operating system has requested that the spawner exit. The spawner will exit after this message is displayed.
Resolution:
N/A
Objspawn is executing on host [fully qualified host name] ([string IP address for fully qualified host name]).
Host: All
Explanation:
The host in which the spawner is executing returned the displayed fully qualified host name that resolved to the displayed IP address. These two strings plus the string "localhost", and any names/IP addresses listed after the alias message, are used by the spawner to locate the appropriate spawner and server definitions.
Resolution:
If the spawner fails to locate a spawner or server definition, ensure the spawner and/or server definitions specify one of the listed name or IP addresses.
Objspawn is exiting as a result of errors.
Host: All
Explanation:
The spawner was unable to start.
Resolution:
Reissue the spawner invocation command with a valid log file destination. Review the contents of the generated log file to determine why the spawner failed to start.
Objspawn lost connection with the launched session.
Host: All
Explanation:
The spawner was unable to complete startup of the launched IOM server.
Resolution:
If the message is identified as an error, contact SAS Technical Support.
Objspawn may not have been installed.
Host: Windows
Explanation:
The spawner was unable to deinstall as a Windows service. This might be due to the spawner not being installed as a Windows service.
Resolution:
Ensure that the spawner is installed as a Windows service.
Objspawn starting as service [service name].
Host: Windows
Explanation:
Indicates which service the spawner is starting as.
Objspawn service ([name of deinstalled spawner service]) was deinstalled successfully.
Host: Windows
Explanation:
The spawner is no longer installed as a Windows service.
Resolution:
N/A
Objspawn service ([name of installed spawner service]) was installed successfully.
Host: Windows
Explanation:
The spawner successfully installed as a Windows service. Subsequent boots of Windows will start the spawner automatically.
Resolution:
N/A
Objspawn version [major].[minor].[delta] is initializing.
Host: All
Explanation:
The version of the spawner being invoked.
Resolution:
N/A
Objspawn was unable to locate a server definition. Objspawn is exiting.
Host: All
Explanation:
The spawner was unable to find a server definition in the configuration source specified that was valid for this machine and the spawner definition's domain and logical name.
Resolution:
Ensure there is a valid server definition that meets the requirements stated. If you are using an LDIF configuration file and the configuration file contains a valid server definition, ensure that there are not two or more blank lines located before the server definition. In LDIF format, two contiguous blank lines signify the end of the definitions that will be used.
Objspawn was unable to open the configuration file ([file path]).
Host: All
Explanation:
The spawner was unable to open a configuration file at the specified location.
Resolution:
Ensure that the configuration file exists at the location specified. Ensure the configuration file is readable by the spawner.
Objspawn was unable to read data from the operator conversation socket. The returned error number is [errno], and the text associated with that error is ([errno description]).
Host: All
Explanation:
The spawner encountered a TCP/IP read error while attempting to converse with a connected operator.
Resolution:
Ensure the operator is still connected.
Objspawn was unable to send data over the operator conversation socket. The returned error number is [errno], and the text associated with that error is ([errno description]).
Host: All
Explanation:
The spawner encountered a TCP/IP write error while attempting to converse with the operator.
Resolution:
The operator might have terminated their connection.
Port [port number] will be ignored, and service [service name] will be used.
Host: All
Explanation:
The spawner encountered both port and service attributes in the current definition. The service definition takes precedence.
Resolution:
Remove the attribute that is redundant/incorrect.
The [attribute name/description] attribute is either missing or is mismatched.
Host: All
Explanation:
The spawner encountered an attribute that did not have a required value.
Resolution:
Correct the configuration.
The [attribute name] attribute requires an argument.
Host: All
Explanation:
An attribute present in the configuration requires a value.
Resolution:
Supply a value for the attribute and restart the spawner.
The [object class name] attribute [attribute name] is no longer supported and will be ignored.
Host: All
Explanation:
The spawner encountered an attribute within the specified configuration source that is no longer supported.
Resolution:
If the configuration source is not shared by earlier versions of the spawner, remove the named attribute from the configuration source.
The [option name] option requires an argument.
Host: All
Explanation:
The displayed option requires a value.
Resolution:
Reissue the spawner command specifying a value for the displayed option.
The [SAS Metadata Server method name] call of the SAS Metadata Server failed. The error ID associated with this failure is [hexadecimal error identifier].
Host: All
Explanation:
The SAS Metadata Server failed to process the spawner's request.
Resolution:
Ensure the SAS Metadata Server is still operating. Ensure the SAS Metadata Server defined in the SAS Metadata Server configuration file is the correct SAS Metadata Server in which to connect.
The [spawner utility name] service cannot be loaded.
Host: All
Explanation:
The spawner was unable to locate the specified support.
Resolution:
Ensure the SAS installation is complete/correct.
The [tracker name] resource tracker cannot be created.
Host: All
Explanation:
The spawner was unable to create an internal object repository.
Resolution:
Review the spawner log file to determine if the spawner is resource constrained.
The attribute [attribute name] will be ignored.
Host: All
Explanation:
The named attribute is not applicable to the spawner.
Resolution:
N/A
The client ([Client child process identifier]) specified by launched session could not be located.
Host: All
Explanation:
The spawner was unable to locate the connection information associated with the client definition in which an IOM server was launched.
Resolution:
Ensure that the command associated with the launched session is correct and that the IOM server is successfully launching.
The client definition cannot be created.
Host: All
Explanation:
The spawner was unable to allocate and initialize a descriptor for the connected client.
Resolution:
Review the spawner log file to determine if the spawner is resource constrained.
The configuration source [file name] is an objspawn log file. Objspawn is unable to process a log file as a configuration file.
Host: All
Explanation:
The value of the -configFile or -xmlConfigFile option specifies an objspawn log file.
Resolution:
Change the value of the configuration source option to specify a configuration file.
The connection with the UUID generator session was lost.
Host: All
Explanation:
The spawner lost contact with the UUID generator client.
Resolution:
Ensure the client did not terminate.
The duplicate [attribute name] attribute will be ignored.
Host: All
Explanation:
The named attribute was encountered more than once.
Resolution:
N/A
The entry ([object class name]) is no longer supported and will be ignored.
Host: All
Explanation:
The spawner encountered an object class within the specified configuration source that is no longer supported.
Resolution:
If the configuration source is not shared by earlier versions of the spawner, remove the named object class definition from the configuration source.
The entry ([object class name]) was defined incorrectly and will be ignored.
Host: All
Explanation:
The spawner encountered an object class within the specified configuration source that is not defined correctly.
Resolution:
Review the spawner log file to determine which values in the object class definition are invalid, then correct the object class definition.
The exit handler cannot be installed.
Host: z/OS
Explanation:
The spawner was unable to install an exit handler.
Resolution:
Contact SAS Technical Support.
The IOM run-time subsystem cannot be initialized.
Host: All
Explanation:
The spawner was unable to locate the IOM server runtime.
Resolution:
Ensure the SAS installation is complete/correct.
The IP address [string IP address] did not transcode.
Host: All
Explanation:
The load balancing implementation requested that the spawner redirect the connected client to the named IP address. The spawner was unable to transcode the IP address string to ASCII.
Resolution:
Ensure the IP address is valid in the load balancing cluster definition.
The launched session did not accept forwarded requirements. The reply is [reply error number].
Host: All
Explanation:
The launched IOM server could not process the client requirements presented.
Resolution:
Ensure that the spawner and the server being launched are compatible releases.
The load balancing instance [method name] call failed. The error text associated with the failure is [error string].
Host: All
Explanation:
The spawner was unable to communicate with its in process load balancing instance.
Resolution:
Contact SAS Technical Support.
The log file ([file path]) already exists. Please erase this file and restart.
Host: All
Explanation:
The spawner was unable to create a log file. A file, that is not a spawner log file, already exists at the named location.
Resolution:
Either delete the file at the named location or specify a different location for the spawner log file.
The log file ([file path]) cannot be created.
Host: All
Explanation:
The spawner was unable to create a log file at the given file path location.
Resolution:
Ensure the given file path is correct. Ensure that there is not a file at the specified location that is not a spawner log file.
The logged-in user does not have the appropriate user permissions to invoke [Windows service name].
Host: Windows
Explanation:
The spawner was not able to install/deinstall as a Windows service due to the launching user not having the appropriate Windows User Rights.
Resolution:
Ensure that the invoking user is an administrator on the Windows host and that the user holds the appropriate Windows User Rights.
The metadata for the SAS Metadata Server failed to process.
Host: All
Explanation:
The metadata received from the SAS Metadata Server is invalid for this spawner implementation.
Resolution:
Ensure that the spawner and SAS Metadata Server are compatible releases.
The multiuser login ([login identifier]) that was specified for the server ([server name]) cannot be found.
Host: All
Explanation:
The spawner was unable to locate the login definition associated with a multi-user server definition.
Resolution:
Correct the configuration source to properly define the missing login definition then reissue the spawner command.
The old client cannot be redirected as a result of IP address issues.
Host: All
Explanation:
The spawner cannot format the redirect IP address into a format suitable by a back level client.
Resolution:
Update the client IOM Bridge for COM or IOM Bridge for Java.
The operator communication buffer cannot be allocated.
Host: All
Explanation:
The spawner was unable to allocate a buffer in which to process operator conversations.
Resolution:
Review the spawner log file to determine if the spawner is resource constrained.
The operator conversation cannot be allocated.
Host: All
Explanation:
The spawner was unable to allocate a descriptor in which to process operator conversations.
Resolution:
Review the spawner log file to determine if the spawner is resource constrained.
The operator conversation was terminated by the peer.
Host: All
Explanation:
The administration session was disconnected by the administrator.
Resolution:
N/A
The operator listen definition cannot be allocated.
Host: All
Explanation:
The spawner was unable to allocate a descriptor in which to process the operator listen definition.
Resolution:
Review the spawner log file to determine if the spawner is resource constrained.
The operator listen socket cannot be created. The returned error number is [errno], and the text associated with that error is ([errno description]).
Host: All
Explanation:
The spawner was unable to create a TCP/IP socket for use as an operator listen socket.
Resolution:
Review the spawner log file to determine if the spawner is resource constrained.
The operator password specified by [string IP address] is invalid.
Host: All
Explanation:
The password received by a session originating from the displayed IP address was not correct.
Resolution:
Reissue operator session and specify the correct password.
The port or service for load balancing the TCP/IP definition is missing.
Host: All
Explanation:
The TCP/IP connection definition associated with the load balancing cluster did not contain a port or service definition.
Resolution:
Correct the TCP/IP connection definition.
The port or service for the UUID generator TCP/IP definition is missing.
Host: All
Explanation:
The TCP/IP connection definition associated with the UUID generation did not contain a port or service definition.
Resolution:
Correct the TCP/IP connection definition.
The process cannot be launched for client [client username].
Host: All
Explanation:
The spawner was unable to launch an IOM server on behalf of the named client.
Resolution:
Ensure the command associated with the server definition is correct. Review the spawner log file to determine the cause of failure.
The process definition cannot be tracked for the server [server name].
Host: All
Explanation:
The spawner was unable to insert a server definition object into its repository.
Resolution:
Review the spawner log file to determine if the spawner is resource constrained.
The repository information for the SAS Metadata Server failed to process.
Host: All
Explanation:
The repository metadata received from the SAS Metadata Server is invalid for this spawner implementation.
Resolution:
Ensure that the spawner and SAS Metadata Server are compatible releases.
The requested UUIDs cannot be generated.
Host: All
Explanation:
The spawner encountered an error while attempting to fulfill a UUID generator request.
Resolution:
Review the spawner log file to determine if the spawner is resource constrained.
The results extension of the SAS Metadata Server cannot be loaded.
Host: All
Explanation:
The spawner was unable to locate the SAS Metadata Server configuration support.
Resolution:
Ensure the SAS installation is complete/correct.
The SAS Metadata Server [SAS Metadata Server method name] call failed. The error text associated with the failure is [error string].
Host: All
Explanation:
The SAS Metadata Server failed to process the spawner's request.
Resolution:
Ensure the SAS Metadata Server is still operating. Ensure the SAS Metadata Server defined in the SAS Metadata Server configuration file is the correct SAS Metadata Server in which to connect.
The SAS Metadata Server configuration file failed to process.
Host: All
Explanation:
The SAS Metadata Server configuration file is invalid for this spawner implementation.
Resolution:
Review the spawner log file to determine the SAS Metadata Server configuration file error details.
The SAS Metadata Server repository [repository name] cannot be located.
Host: All
Explanation:
The response from the SAS Metadata Server did not contain the specified repository name.
Resolution:
Ensure the SAS Metadata Server configuration file identifies the correct repository name. Ensure that the SAS Metadata Server defined in the SAS Metadata Server configuration file hosts the given repository name.
The server [name of server] cannot be placed in a resource track.
Host: All
Explanation:
The spawner was unable to insert the internal server definition object in its repository.
Resolution:
Review the spawner log file to determine if the spawner is resource constrained.
The server [server name] listen cannot be registered.
Host: All
Explanation:
The spawner was unable to place the socket associated with a server listen in a select.
Resolution:
Review the spawner log file to determine if the spawner is resource constrained.
The server connection definition cannot be created.
Host: All
Explanation:
The spawner was unable to create an internal launched IOM server connection object.
Resolution:
Review the spawner log file to determine if the spawner is resource constrained.
The server name [server-name] is not unique. Therefore this server definition will not be included.
Host: All
Explanation:
The spawner was unable to process a server definition because another server definition has the same name.
Resolution:
Change the server name in the server definition.
The server definition cannot be allocated.
Host: All
Explanation:
The spawner was unable to allocate a server definition.
Resolution:
Review the spawner log file to determine if the spawner is resource constrained.
The server did not start in the specified amount of time.
Host: All
Explanation:
The spawner was unable to start the load-balanced server in the time specified by the Availability Timeout property.
Resolution:
Ensure that the SAS server can start properly. If appropriate, increase the value of the Availability Timeout property.
The server launch command cannot be allocated.
Host: All
Explanation:
The spawner was unable to allocate the server's launch command.
Resolution:
Review the spawner log file to determine if the spawner is resource constrained.
The server must define the available encryption algorithm(s) when an encryption level is set.
Host: All
Explanation:
The server definition specifies an encryption level, but does not specify which encryption algorithms are available.
Resolution:
Specify the available encryption algorithms.
The session socket for the UUID generator was not accepted.
Host: All
Explanation:
The spawner was unable to process a new UUID generator client.
Resolution:
Review the spawner log file to determine if the spawner is resource constrained.
The socket-access method handle cannot be acquired.
Host: All
Explanation:
The spawner was unable to locate the IOM protocol TCP/IP driver.
Resolution:
Ensure the SAS installation is complete/correct.
The specified [attribute name] value is invalid ([invalid attribute value]).
Host: All
Explanation:
The displayed value for the displayed attribute is not valid.
Resolution:
Correct the attribute value and reissue command.
The specified TCP/IP definition protocol is invalid.
Host: All
Explanation:
A TCP/IP connection definition specifies a protocol that is not supported by the spawner.
Resolution:
Correct the TCP/IP connection protocol attribute value.
The TCP/IP accept call failed to process the client connection.
Host: All
Explanation:
The spawner was unable to process a new client.
Resolution:
Review the spawner log file to determine if the spawner is resource constrained.
The TCP/IP accept call failed to process the operator connection. The returned error number is [errno], and the text associated with that error is ([errno description]).
Host: All
Explanation:
The spawner was unable to process a new operator.
Resolution:
Review the spawner log file to determine if the spawner is resource constrained.
The TCP/IP accept call failed to process the session conversation request.
Host: All
Explanation:
The spawner was unable to process a new IOM server connection.
Resolution:
Review the spawner log file to determine if the spawner is resource constrained.
The TCP/IP bind call for the operator listen port failed. The returned error number is [errno], and the text associated with that error is ([errno description]).
Host: All
Explanation:
The spawner was unable to establish the operator listen.
Resolution:
Ensure the port/service specified for use by the spawner is defined and not in use. If in use, ensure the spawner is not already executing.
The TCP/IP bind call for the server [server name] listen port failed. The text associated with that error is ([reason of failure]).
Host: All
Explanation:
The spawner was unable to establish the named server listen.
Resolution:
Ensure the port/service specified for use by the spawner is defined and not in use. If in use, ensure the spawner is not already executing.
The TCP/IP bind call for the session conversation port failed. The returned error number is [errno], and the text associated with that number is ([errno description]).
Host: All
Explanation:
The spawner was unable to bind to any port in order to establish a listen for use by launched IOM servers.
Resolution:
Contact SAS Technical Support.
The TCP/IP bind call for the UUID listen port failed. The returned error number is [errno], and the text associated with that error is ([errno description]).
Host: All
Explanation:
The spawner was unable to establish the UUID generator listen.
Resolution:
Ensure the port/service specified for use by the spawner is defined and not in use. If in use, ensure the spawner is not already executing.
The TCP/IP listen call for the operator listen port failed. The returned error number is [errno], and the text associated with that error is ([errno description]).
Host: All
Explanation:
The spawner was unable to establish the operator listen.
Resolution:
Ensure the port/service specified for use by the spawner is defined and not in use. If in use, ensure the spawner is not already executing.
The TCP/IP listen call for the server [server name] listen port failed. The text associated with that error is ([reason of failure]).
Host: All
Explanation:
The spawner was unable to establish the server listen.
Resolution:
Ensure the port/service specified for use by the spawner is defined and not in use. If in use, ensure the spawner is not already executing.
The TCP/IP listen call for the session conversation port failed. The returned error number is [errno], and the text associated with that error is ([errno description]).
Host: All
Explanation:
The spawner was unable to establish the launched IOM server listen.
Resolution:
Contact SAS Technical Support.
The TCP/IP listen call for the UUID listen port failed. The returned error number is [errno], and the text associated with that error is ([errno description]).
Host: All
Explanation:
The spawner was unable to establish the UUID generator listen.
Resolution:
Contact SAS Technical Support.
The URI support extension cannot be loaded.
Host: All
Explanation:
The spawner was unable to locate the URI parsing support.
Resolution:
Ensure the SAS installation is complete/correct.
The UUID listen definition cannot be created.
Host: All
Explanation:
The spawner was unable to create an internal UUID listen object.
Resolution:
Review the spawner log file to determine if the spawner is resource constrained.
The UUID service name ([service name]) cannot be resolved.
Host: All
Explanation:
The host TCP/IP stack was unable to resolve the displayed TCP/IP service name.
Resolution:
Ensure the given service name is correct and defined to the spawner host installation.
The wait event for the objspawn cannot be created.
Host: All
Explanation:
The spawner was unable to create an internal synchronization object.
Resolution:
Review the spawner log file to determine if the spawner is resource constrained.
The Windows [Windows routine name] call failed ([reason for failure]).
Host: All
Explanation:
The spawner encountered an Windows SDK error while invoking the given method.
Resolution:
Contact the system administrator to determine the meaning of the error text.
The Windows [Windows routine name] call failed. GetLastError() = [GetLastError() return value].
Host: All
Explanation:
The spawner encountered an Windows SDK error while invoking the given method.
Resolution:
Contact the system administrator to determine the meaning of the GetLastError() return code.
Unable to bind to the SAS Metadata Server because the [name of missing attribute] attribute is missing.
Host: All
Explanation:
The SAS Metadata Server configuration file did not specify the named attribute.
Resolution:
Update the SAS Metadata Server configuration file to include the missing attribute.
Unable to create the session conversation definition.
Host: All
Explanation:
The spawner was unable to create an internal launched IOM server conversation object.
Resolution:
Review the spawner log file to determine if the spawner is resource constrained.
Unable to obtain the session conversation port. The returned error number is [errno], and the text associated with that error is ([errno description]).
Host: All
Explanation:
The spawner was unable to retrieve the port associated with the session conversation listen.
Resolution:
Contact the system administrator to determine if there are issues with the TCP/IP implementation.
Unable to read the server ([server name]) client update information.
Host: All
Explanation:
The spawner encountered a TCP/IP read error while attempting to converse with a launched IOM server.
Resolution:
The server might have exited.
Unable to resolve "localhost".
Host: All
Explanation:
The spawner could not resolve the local IP address.
Resolution:
Ensure that your TCP/IP configuration settings are correct.
Unable to redirect the client request.
Host: All
Explanation:
The spawner failed to redirect the connection request to another server in the cluster.
Resolution:
Review the spawner log for more information.
You can only specify one of the following choices: install or deinstall.
Host: Windows
Explanation:
Both the install and deinstall commands were specified.
Resolution:
Remove the option that should not be specified.