Filter
Top Products
ANR8193W (Solaris)
HTTPS driver unable to initialize due to error in BINDing to Port port, reason
code reason code.
Explanation: While initializing HTTPS communications, the server has failed to
connect to a master TCP/IP socket on which to listen for clients. The reason code is
the return code from the TCP/IP bind API.
System Action: Server operation continues, but the server cannot accept sessions
from administrative clients using HTTPS protocol.
User Response: Ensure that no other application is using the port number
specified in the server options file with the PORT option. If TCP/IP is also in use
for client sessions, ensure that the same port number is not specified for both
TCP/IP and HTTPS communications. This may be done by issuing the TCP/IP
netstat -s command. If the server is brought down and then started immediately, you
may be within the TCP/IP one minute timeout period for port reusage. Bring down
the sever, wait one minute, and then restart the server. If that does not work, it may
be necessary to restart Solaris
ANR8194W (HP-UX)
HTTPS driver unable to initialize due to error in secure data initialization,
reason code reason code.
Explanation: While initializing HTTPS communications, the server has failed
initialize of the secure data certificate information.
System Action: Server operation continues, but the server cannot accept sessions
from administrative clients using HTTPS protocol.
User Response: Ensure the keyring file name and keyring file password are
correct and that the password has not expired. Check for earlier SKIT messages
which may indicate the real problem. Replace keyring if necessary and re-start the
server.
ANR8200I (AIX) TCP/IP driver ready for connection with clients on port port number.
Explanation: The server is now able to accept sessions with clients that use the
TCP/IP protocol on the indicated port number.
System Action: Server operation continues.
User Response: None.
796
Version 3 Release 7