Here are error messages that clients may receive and explanations to
correct their cause.
If you are still unable to correct the error, you may want the spawner to begin tracing its activity. See the administrator command section or the sasVerbose and sasLogFile options for details on how to
have the spawner trace its activity.
- ERROR: Unable to allocate cmd memory
- The spawner has exhausted its resources. Review the list of
started object servers (see the
listl and kill administrator commands) to determine if there are any orphaned object servers. If so, kill the orphaned object servers.
- ERROR: Unable to CreateThread
- The spawner has exhausted its resources. Review the list of
started object servers (see the
listl and kill administrator commands) to determine if there are any orphaned object servers. If so, kill the orphaned servers.
- ERROR: Unable to launch SAS ObjectServer (AddToDefault failure)
- The spawner has exhausted its resources. Review the list of
started object servers (see the
listl and kill administrator commands) to determine if there are any orphaned object servers. If so, kill the orphaned servers.
- ERROR: Unable to launch SAS ObjectServer (AddToDesktop failure)
- The spawner has exhausted its resources. Review the list of
started object servers (see the
listl and kill administrator commands) to determine if there are any orphaned object servers. If so, kill the orphaned servers.
- ERROR: Unable to launch SAS ObjectServer (Allocation of Environment block
failure)
- The spawner exhausted its resources. Review the list of
started object servers (see the
listl and kill administrator commands) to determine if there are any orphaned object servers. If so, kill the orphaned object servers.
- ERROR: Unable to launch SAS ObjectServer (Child allocation failure)
- The spawner has exhausted its resources. Review the list of
started object servers (see the
listl and kill administrator commands) to determine if there are any
orphaned object servers. If so, kill the orphaned object servers.
- ERROR: Unable to launch SAS ObjectServer (Child CreateEvent failure)
- The spawner has exhausted its resources. Review the list of
started object servers (see the
listl and kill administrator commands) to determine if there are any
orphaned object servers. If so, kill the orphaned object servers.
- ERROR: Unable to launch SAS ObjectServer (Child DuplicateHandle failure)
- The spawner has exhausted its resources. Review the list of
started object servers (see the
listl and kill administrator commands) to determine if there are any
orphaned object servers. If so, kill the orphaned object servers.
- ERROR: Unable to launch SAS ObjectServer (Child username allocation
failure)
- The spawner has exhausted its resources. Review the list of
started object servers (see the
listl and kill administrator commands) to determine if there are any orphaned object servers. If so, kill the orphaned object servers.
- ERROR: Unable to launch SAS ObjectServer (Conversion of environment block
failure)
- The spawner has exhausted its resources. Review the list of
started object servers (see the
listl and kill administrator commands) to determine if there are any orphaned object servers. If so, kill the orphaned object servers.
- ERROR: Unable to launch SAS ObjectServer (CreateEnvironmentBlock failure)
- The spawner has exhausted its resources. Review the list of
started object servers (see the
listl and kill administrator commands) to determine if there are any
orphaned object servers. If so, kill the orphaned object servers.
- ERROR: Unable to launch SAS ObjectServer (CreateProcess failure)
- The spawner has exhausted its resources. Review the list of
started object servers (see the
listl and kill administrator commands) to determine if there are any
orphaned object servers. If so, kill the orphaned object servers.
- ERROR: Unable to launch SAS ObjectServer (CreateProcessAsUser failure)
- The spawner has exhausted its resources. Review the list of
started object servers (see the
listl and kill administrator commands) to determine if there are any
orphaned object servers. If so, kill the orphaned object servers.
- ERROR: Unable to launch SAS ObjectServer (exec failure)
- Ensure that the
sasCommand value that is specified is correct. Log on to the host in which the spawner is executing. Issue the
sasCommand to determine if it is correct.
- ERROR: Unable to launch SAS ObjectServer (fork failure)
- Ensure that the host in which spawner is executing has not
overflowed the process table. If so, you may want to stop the spawner
and restart it to clean up possible orphaned processes.
- ERROR: Unable to launch SAS ObjectServer (GetUserProfilePathDirectory
failure)
- The spawner has exhausted its resources. Review the list of
started object servers (see the
listl and kill administrator commands) to determine if there are any
orphaned object servers. If so, kill the orphaned object servers.
- ERROR: Unable to launch SAS ObjectServer (LoadUserProfileA failure)
- The spawner has exhausted its resources. Review the list of
started object servers (see the
listl and kill administrator commands) to determine if there are any
orphaned object servers. If so, kill the orphaned object servers.
- ERROR: Unable to launch SAS ObjectServer (putenv conv)
- Ensure that the spawner is executing in a process that is
large enough to support the number of servers defined and executing.
- ERROR: Unable to launch SAS ObjectServer (putenv sid)
- Ensure that the spawner is executing in a process that is
large enough to support the number of servers defined and executing.
- ERROR: Unable to launch SAS ObjectServer (putenv sock)
- Ensure that the spawner is executing in a process that is
large enough to support the number of servers defined and executing.
- ERROR: Unable to launch SAS ObjectServer (too many tokens in command)
- Place your
sasCommand in an executable shell. Then update
your sasCommand to invoke the shell. Note: The
shell must accept arguments and pass the arguments received onto the object server.
- ERROR: Unable to launch SAS ObjectServer (unable to allocate command
token)
- Ensure that the spawner is executing in a process that is
large enough to support the number of servers defined and executing.
- ERROR: User does not have authority
- Ensure that the user name and password specified are correct and have not
expired. If the user name and password are correct, ensure that the spawner is executing with the privileges that are specified in the appropriate
host setup section in this document.
- OBJSPAWN(E): ATBALC2 returned %d, ATBEES3 (%*.*s)
- Ensure that the
sasPLUName and sasTPName that are
provided in the sasServer definition are correct.
- OBJSPAWN(E): ATBRCVW returned %d, ATBEES3 (%*.*s)
- The spawner encountered an APPC error. Have your systems
administrator verify that APPC is operating correctly. Also, ensure that the
object server configuration and definition is correct.
- OBJSPAWN(E): ATBRCVW statRcvd not correct - %d
- The spawner encountered an APPC error. Request that your systems
administrator verify that APPC is operating correctly. Also, ensure that the
object server configuration and definition is correct.
- OBJSPAWN(E): ATBRCVW(2) returned %d, ATBEES3 (%*.*s)
- The spawner encountered an APPC error. Request that your systems
administrator verify that APPC is operating correctly. Also, ensure that the
object server configuration and definition is correct.
- OBJSPAWN(E): ATBRCVW(2) statRcvd not correct - %d
- The spawner encountered an APPC error. Request that your systems
administrator verify that APPC is operating correctly. Also, ensure that the
object server configuration and definition is correct.
- OBJSPAWN(E): ATBRTS returned %d, ATBEES3 (%*.*s)
- The spawner encountered an APPC error. Request that systems
administrator verify that APPC is operating correctly. Also, ensure that the
object server configuration and definition is correct.
- OBJSPAWN(E): ATBRTS(2) returned %d, ATBEES3 (%*.*s)
- The spawner encountered an APPC error. Request that your systems
administrator verify that APPC is operating correctly. Also, ensure that the
object server configuration and definition is correct.
- OBJSPAWN(E): ATBSEND returned %d, ATBEES3 (%*.*s)
- The spawner encountered an APPC error. Request that your systems
administrator verify that APPC is operating correctly. Also, ensure that the
object server configuration and definition is correct.
- OBJSPAWN(E): ATBSEND(2) returned %d, ATBEES3 (%*.*s)
- The spawner encountered an APPC error. Request that your systems
administrator verify that APPC is operating correctly. Also, ensure that the
object server configuration and definition is correct.
- OBJSPAWN(E): givesocket() returned %d
- The spawner failed to hand off the client connection socket.
Ensure that TCP/IP is operational.
