ANR0454E
Session rejected by server target server name, reason: rejection reason.

Explanation

The server tried to open a session with the named server. The session was rejected for the indicated reason.

System action

The operation fails.

User response

Check both the servers for any additional messages that might further describe the reason the session was rejected. The rejection reason will be in the form of "diagnostic code - reason". The diagnostic code is only intended for use by your service representative. The following responses apply to the specified rejection reasons.
  • No Resource: Ensure that the receiving server is enabled and has sufficient database, log, and memory resource to support the server session.
  • Verifier expired: Ensure that the administrator's password is current on both servers.
  • Admin not registered: Ensure that the administrator is registered on the target server.
  • Inbound sessions disabled: Ensure that the target server has not disabled this server with the DISABLE SESSIONS SERVER command.
  • Down Level: Ensure that this server's level is current with respect to the target server's level.
  • Admin in use: Ensure that the administrator is not being updated on the target server.
  • Language not available: Ensure that required languages are installed on the target server.
  • Admin locked: Ensure that the administrator is not locked on either server.
  • License Failure: Ensure that appropriate licenses are registered.
  • Admin on client port: Use the UPDATE SERVER command to set the admin port for the target server.
  • SSL Required: Ensure that SSL is properly configured.
  • Authentication Failure: Ensure that all passwords have been set correctly on both servers. The password for the server (set by SET SERVERPASSWORD on server X) and the password in the server definition (set by DEFINE or UPDATE SERVER X SERVERPASSWORD=) are the same password.
  • Verification Failure: Use the QUERY SERVER command to determine that the HLADDRESS and LLADDRESS of the target server are correct. If they are not, correct them with the UPDATE SERVER command. If they are correct, resynchronize with the target server by issuing the UPDATE SERVER FORCESYNC=YES command.
  • Communication Failure: Ensure that the target server is available and that TCPIP is available on both servers. Use the QUERY SERVER command to determine that the HLADDRESS and LLADDRESS of the target server are correct. If they are not, correct them with the UPDATE SERVER command.
  • Node Type: Either the TYPE of the registered node on the target server is not SERVER or the NODENAME parameter of the server definition on the source server is incorrect.
  • Internal error: Use the messages on the target server to determine the problem.