Filter
Top Products
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 HP-UX.
ANR8191W (Solaris)
HTTP driver unable to initialize due to error in BINDing to Port port, reason
code reason code.
Explanation: While initializing HTTP 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 HTTP 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 HTTP 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.
ANR8192I (AIX) HTTPS driver ready for connection with clients on port port number.
Explanation: The server is now able to accept sessions with clients that use the
HTTPS protocol on the indicated port number.
System Action: Server operation continues.
User Response: None.
ANR8192I (HP-UX)
HTTPS driver ready for connection with clients on port port number.
Explanation: The server is now able to accept sessions with clients that use the
HTTPS protocol on the indicated port number.
System Action: Server operation continues.
User Response: None.
ANR8192I (Solaris)
HTTPS driver ready for connection with clients on port port number.
Explanation: The server is now able to accept sessions with clients that use the
HTTPS protocol on the indicated port number.
System Action: Server operation continues.
794
Version 3 Release 7