Filter
Top Products
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 Windows NT.
ANR8284E (AIX) The Shared Memory Communications Protocol could not initialize.
Explanation: The server was unable to initialize the Shared Memory
Communications Protocol due to an error.
System Action: Server operation continues without Shared Memory
Communications.
User Response: Examine previous error messages for the cause of the failure.
ANR8284W (AS/400)
Exit type EXIT exit name cannot be accessed.
Explanation: The *PGM object with the given exit name cannot be accessed by
the server. The attempt fails because the server does not have the authority
necessary to access the designated *PGM object.
System Action: Server operation continues. The server issues additional error
messages when this condition prevents it from completing an operation.
User Response: Correct the problem with the specified exit program and use the
UPDATE EXIT command to notify the server that the exit has been changed.
ANR8284W (Windows NT)
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 to
initialize 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.
866
Version 3 Release 7