27.12.2013 Views

SAS® Integration Technologies: Administrator's Guide (LDAP Version)

SAS® Integration Technologies: Administrator's Guide (LDAP Version)

SAS® Integration Technologies: Administrator's Guide (LDAP Version)

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>SAS®</strong> <strong>Integration</strong> <strong>Technologies</strong>: <strong>Administrator's</strong> <strong>Guide</strong> (<strong>LDAP</strong> <strong>Version</strong>)<br />

Host: All<br />

Explanation:<br />

The spawner was unable to create a log file. A file which is not a spawner log file already exists at the<br />

named location.<br />

Resolution:<br />

Either delete the file at the named location or specify a different location for the spawner log file.<br />

The log file ([file path]) cannot be created.<br />

Host: All<br />

Explanation:<br />

The spawner was unable to create a log file at the given file path location.<br />

Resolution:<br />

Ensure the given file path is correct. Ensure that there is not a file at the specified location that is not a<br />

spawner log file.<br />

The logged−in user does not have the appropriate user permissions to invoke [Windows service name].<br />

Host: Windows<br />

Explanation:<br />

The spawner was not able to install or deinstall as a Windows service due to the launching user not<br />

having the appropriate Windows User Rights.<br />

Resolution:<br />

Ensure that the invoking user is an administrator on the Windows host and that the user holds the<br />

appropriate Windows User Rights.<br />

The multi−user login ([login identifier]) that was specified for server ([server name]) cannot be found.<br />

Host: All<br />

Explanation:<br />

The spawner was unable to locate the login definition associated with a multi−user server definition.<br />

Resolution:<br />

Correct the configuration source to properly define the missing login definition then reissue the<br />

spawner command.<br />

The old client cannot be redirected as a result of IP address issues.<br />

Host: All<br />

Explanation:<br />

The spawner cannot format the redirect IP address into a format suitable by a back level client.<br />

Resolution:<br />

Update the client IOM Bridge for COM or IOM Bridge for Java.<br />

The operator communication buffer cannot be allocated.<br />

Host: All<br />

Explanation:<br />

The spawner was unable to allocate a buffer in which to process operator conversations.<br />

Resolution:<br />

Review the spawner log file to determine if the spawner is resource constrained.<br />

The operator conversation cannot be allocated.<br />

Host: All<br />

Explanation:<br />

The spawner was unable to allocate a descriptor in which to process operator conversations.<br />

Resolution:<br />

Review the spawner log file to determine if the spawner is resource constrained.<br />

The operator conversation was terminated by peer.<br />

Host: All<br />

Explanation:<br />

The administration session was disconnected by the administrator.<br />

Resolution:<br />

Spawner Error Messages 173

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!