Novell ACCESS MANAGER 3.1 SP1 - EVENT CODES Manual page 95

Event codes
Hide thumbs Also See for ACCESS MANAGER 3.1 SP1 - EVENT CODES:
Table of Contents

Advertisement

Event Code
Description
2005010120D
SOCKD is not running/registered...
cannot add a new connection request.
Failed to send disconnect notification
to sockd. Failed to send the new
connection notification to sockd. Failed
to send servlet response to fd. Failed
to send servlet init success response
to fd, fd. Failed to send servlet
response %x to fd %d msgType, fd.
Failed to send socks response %x to
fd %d msgType, fd
2005010120E
Restricting the number of policies for
the role %s to %d .. because of
insufficient buffer size, tmp->rolename,
numRules Restricting the number of
policies for the role
2005010120F
Error: Servlet is already registered.
Servlet_connect_connection: Servlet
is not registered. Received disconnect
from servlet. But servlet is not
registered
30050101210
Cannot add new connection.
Maximum number of connections
reached
50050101400
Failed to connect to connection
Manager
20050101401
Error in sending message to
Connection Manager
20050101402
Error in receiving message
20050101403
Failed to get the lock of the connection
Manager socket. Service cannot be
stopped
20050101404
Failed to update SSLVPN Server
Configuration
Remedy
Cause: One of the programs of SSLVPN
service is not running. And the SSLVPN
Gateway is in bad state
Action: Restart the sslvpn service and restart
the novell-tomcat where sslvpn servlet is
running
Cause: Too many number of traffic rules for
that particular role
Action: Revisit the configuration and reduce
the number of traffic rules for that particular
role
Cause: Communication channel between
servlet and connection manager have gone
bad
Action: Restart the sslvpn service and restart
the novell-tomcat where sslvpn servlet is
running
Cause: Maximum number of connections
reached. No more connections can be added
Action: Contact system administrator
Cause: Connection manager may not be
running
Action: Start the connection using the
sslvpnc –up
command.
Cause: Connection Manager socket would
have closed
Action: Make sure connection Manager
running
Cause: May be connection socket would
have closed
Action: Make sure connection Manager
running
Cause: This happens with down command
and If connmanSocket lock is not available
Action: Retry
Cause: This happens if the
not well formed
Action: Make sure that
config.xml
correct and well formed
is
config.xml
is
SSL VPN Server (005)
95

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents