Novell ACCESS MANAGER 3.1 SP1 - EVENT CODES Manual page 94

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

Advertisement

Event Code
40050101205
20050101206
20050101207
20050101208
20050101209
4005010120A
4005010120B
2005010120C
94
Novell Access Manager 3.1 SP1 Event Codes
Description
Configuration file does not have
proper contents. Parsing configuration
failed. Connection Manager has bad
configuration data. Could not add new
connection
Resource allocation failed
Failed to send stunnel response
"1231" to fd "5"
Could not open the file "/opt/novell/
sslvpn/connmansocket" exiting! Could
not get File Lock for ConnMan.
Another instance may be already
running
Could not open the Unix domain
socket
Could not bind the Local socket. TCP
socket could not be opened
VCC has not been started. May be
VCC port is invalid
Failed to parse Stunnel certificate.
error code = XXXX
Remedy
Cause: The
/etc/opt/novell/sslvpn/
file is not properly formatted.
config.xml
XML data corruption could have happened
Action: Restart the sslvpn service. Apply the
changes from device manager and observe
for any other errors while applying the
changes on the device
Cause: Might be a potential issue
Action: Collect all error logs and report to
Support
Cause: Stunnel program may have been stop
or not running correctly
Action: Collect error log reports Restart the
sslvpn service
Cause: The
/opt/novell/sslvpn/
connmansocket
file may have been locked
by another instance
Action: Forcefully delete this file and restart
sslvpn service
Cause: The
/opt/novell/sslvpn/
file may have been locked
connman
Action: Forcefully delete this file and restart
sslvpn service
Cause: Invalid configuration or that particular
port may be being used by another service
Action: Check the service running on that
port. Change the port in the configuration and
restart sslvpn service
Cause: The VCC port is either invalid or some
other service is running on that port
Action: Check
/etc/opt/novell/
sslvpn/config.xml
file and verify the
VCC port is valid. If it is not, change it to the
correct value, delete the device from the
Administration Console, then restart the JCC-
proxy using the
/etc/init.d/novell-jcc
restart
command.
Cause: Stunnel Certificate is in bad format
Action: Recreate the Stunnel certificate in
device manager and apply changes to the
device

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents