B.0 Error Messages
Some of the frequently encountered error messages and their explanations are given below:
4352/0x01100: Received Zero Length Data From SOCKS Client.
Possible Cause:
The SSL-enabled application crashed while performing a policy resolution.
Action:
Run the application again. If the problem persists, contact your system administrator.
4353/0x01101: Policy Resolution Request From SOCKS Client Was Not In The Correct Format (Incorrect Message Length).
Possible Cause:
The message from the SOCKS client is corrupted.
Action:
Contact your system administrator.
4354/0x01102: Unable to Reply to the Policy Resolution Request by SOCKS Client.
Possible Cause:
The SSL-enabled application that requested policy resolution crashed.
Action:
Run the application again. If the problem persists, contact your system administrator.
4355/0x01103: Policy Resolution Request From SOCKS Client Was Not In the Correct Format (Incorrect Message Type)
Possible Cause:
Possible hack by an intruder.
Action:
Restart the session. Check the list of currently running processes in the system for viruses.
4865/0x01301: Unable to Send Statistics Reply to Applet
Possible Cause:
The user closed the browser, or the applet closed without sending a disconnect.
Action:
Contact your system administrator if the problem persists.
4866/0x01302: Cookie Received From Applet Was Not in the Correct Format (Incorrect Message Length)
Possible Cause:
Polresolver to Applet communication is bad.
Action:
Disconnect the session and reconnect. Contact your system administrator if the problem persists.
4867/0x01303: Unable to Send Acknowledgment to Applet for the Cookie Received
Possible Cause:
Polresolver to Applet communication is bad.
Action:
If the problem persists, the session is disconnected automatically.
4868/0x01304: Incorrect DNS Information Message Received From Applet (Incorrect Length of Message)
Possible Cause:
Incorrect DNS message from the applet.
Action:
Disconnect the session and connect again to be able to use DNS across the protected network.
4869/0x01305: Unable to Send Acknowledgment to Applet for the DNS Message Received
Possible Cause:
Polresolver to Applet communication is bad.
Action:
If the problem persists, the session is disconnected automatically.
4870/0x01306: Disconnect Message From Applet Was Incorrect (Incorrect Message Length)
Possible Cause:
Polresolver to Applet communication is bad or the session cleanup is incomplete.
Action:
Contact your system administrator if the problem persists.
4871/0x01307: Unable to Send Acknowledgment to Applet for the Disconnect Message Received
Possible Cause:
Polresolver to Applet communication is bad or the session cleanup is incomplete.
Action:
Contact your system administrator if the problem persists.
4872/0x01308: Polresolver Received An Incomplete Message. Unable to Identify The Sender.
Possible Cause:
An intruder might be probing Polresolver with an incorrect message.
Action:
Contact your system administrator with appropriate logs.
4873/0x01309: Failed to Allocate Memory For Internal Operation.
Possible Cause:
Insufficient memory.
Action:
This error is usually accompanied by another error code, indicating which operation failed. Restart the session.
5376/0x01500: Failed to Send Statistics Request to Stunnel.
Possible Cause:
Stunnel is down. This message is sent only after trying for a specified number of times.
Action:
Restart the session. If the problem persists, contact your system administrator.
5377/0x01501: Statistics Response Message From Stunnel was Incorrect (Incorrect Message Length)
Possible Cause:
Polresolver to Stunnel communication is bad.
Action:
Contact your system administrator with appropriate logs.
5378/0x01502: Unable to Send Disconnect Message From Stunnel.
Possible Cause:
Stunnel is down.
Action:
Restart the session. Contact your system administrator if the problem persists.
5379/0x01503: Disconnect Acknowledgment Message From Stunnel Was Incorrect (Incorrect Length of Message)
Possible Cause:
Polresolver to Stunnel message is bad.
Action:
Contact your system administrator with appropriate logs.
5380/0x01504: Incorrect Message From Stunnel (Incorrect Length of Message)
Possible Cause:
Polresolver to Stunnel communication is bad.
Action:
Contact your system administrator with appropriate logs.
5381/0x01505: Invalid Message From Stunnel (Message Type Unknown)
Possible Cause:
Polresolver to Stunnel communication is bad.
Action:
Contact your system administrator with appropriate logs.
0x01506: SSL VPN Server Certificate Validation Failed. Please Log out.
Possible Cause:
Failed to validate the certificate.
Action:
Contact your system administrator with appropriate logs.
0x01507: Disconnected due to Hibernation/Standby. Please Log out.
Possible Cause:
The machine went into the hibernation or standby mode.
Action:
Log out of the SSL VPN connection, then log in again to connect.
0x01701: OpenVPN Authentication Failed. Please Log out.
Possible Cause:
Password verification failed.
Action:
Contact your system administrator with appropriate logs.
0x01702: OpenVPN Connection Error. Please Log out.
Possible Cause:
Certificate verification failed.
Action:
Contact your system administrator with appropriate logs.
0x01703: Received Fatal Error from OpenVPN. Please Log out.
Possible Cause:
TUN/TAP allocation failed.
Action:
Try disconnecting and connecting again. If the problem persists, contact the system administrator.
0x01704: Policy Initialization Failed. Please Log out.
Possible Cause:
Temporary file creation failed.
Action:
Restart the session. If the problem persists, contact your system administrator.
0x01705:Tun Interface is Down. Please Log out.
Possible Cause:
The TUN interface is down.
Action:
Contact your system administrator with appropriate logs.
0x01801: Service is not Running. Please Log out.
Possible Cause:
Failed to find a free port.
Action:
Check the system log and contact your system administrator.
Connections Threshold Exceeded. Please Try Again After Some Time.
Possible Cause:
The server has reached the limit for maximum number of connections. The low bandwidth SSL VPN, allows only 249 simultaneous SSL VPN sessions and a transfer rate of 40Mbits per second.
Action:
Try to connect again after some time. If any user has disconnected, you will be connected to the server.
If your deployment requires 250 or more concurrent SSL VPN connections, you can install the high bandwidth version of Novell SSL VPN, after getting an export clearance from the US security board.
If you cannot download the high bandwidth version of SSL VPN due to export restriction, you can set up more than one SSL VPN server in a cluster.
0x01804: Maximum Attempt to Enter Password Reached. Please Close the Browser.
Possible Cause:
You have not entered the correct credentials within the maximum tries.
Action:
Log in again with the correct credentials.
0x01805: Timeout Occurred While Entering Credentials. Please Close the Browser.
Possible Cause:
You have not entered the correct credentials within the timeout period.
Action:
Log in again with the correct credentials.
0x01000: Client Integrity Check Failed. Check Error Logs for More Information.
Possible Cause:
The connection requires software that is currently not running in the system.
Action:
Check and install the software.
0x01001: Server is not Responding.
Possible Cause:
Either the VPN server or Access Manager is down or the network is disconnected.
Action:
Check the link and reconnect.
0x01002: Client is Inactive for More Than <x> Minutes. Please Log out.
Possible Cause:
The client is not active or there was no data transfer from VPN server to the client. However, this does not log the client out of Access Manager.
Action:
Log out of the SSL VPN connection, then log in again to connect.
0x01003: Problem with One of the Underlying Components/ Connection Error. Please Logout.
Possible Cause:
One of the client components encountered a problem.
Action:
Check the log entries for more information.
0x01004: Problem with One of the Underlying Components. Please Disconnect.
Possible Cause:
One of the client components encountered a problem.
Action:
Check the log entries for more information.
0x01005: Failed to Find Free Ports on Client.
Possible Cause:
No free ports are available.
Action:
Contact your system administrator.
0x01006: Resource Not Found on the Gateway.
Possible Cause:
Improper server installation.
Action:
Reinstall the SSL VPN server build.
0x01007: Failed to Download SSL VPN Files from the Gateway.
Possible Cause:
Insufficient space on the client.
Action:
Ensure that 200 MB free space is available on the Windows drive on the client.
0x01008: Unable to Fetch the Configuration Information from the Gateway.
Possible Cause:
Improper server configuration.
Action:
Check and change the server configuration.
0x01009: Unable to Fetch the Policy Information from the Gateway.
Possible Cause:
Improper Access Gateway configuration.
Action:
Check and change the Access Gateway configuration.
0x0100A: User Denied Access. Please Contact System Administrator.
Possible Cause:
The user or the user role does not have a policy.
Action:
Contact your system administrator.
0x0100B: OpenSSL Needs to be Installed. Please Logout.
Possible Cause:
OpenSSL is not installed on the client.
Action:
Install OpenSSL 0.9.7 or later.
Possible Cause:
OpenSSL is not installed in the correct path.
Action:
Install OpenSSL 0.9.7 or later in the correct path.
0x0100C: Dependent Components not Available in this System. Please Logout.
Possible Cause:
OpenSSL is not installed on the client.
Action:
Install OpenSSL 0.9.7 or later.
Possible Cause:
OpenSSL is not installed in the correct path.
Action:
Install OpenSSL 0.9.7 or later in the correct path.
0x0100D: Another Instance of SSL VPN is Running. Please Close this Browser.
Possible Cause:
Another instance of SSL VPN is running in another browser.
Action:
Close the browser where another instance of SSL VPN is running.
Possible Cause:
The previous connection was not properly cleaned up.
Action:
Clean up the previous connection.
0x0100E Failed to Receive Keepalive. Please Logout.
Possible Cause:
The SSL VPN server is down.
Action:
Check the SSL VPN server health status and restart the server.
Possible Cause:
The Access Gateway is down.
Action:
Check the Access Gateway health status and start the gateway.
0x0100F: Gateway Internal Error.
Possible Cause:
The server is malfunctioning.
Action:
Contact your system administrator.
0x01010: Unable to Contact Gateway. Please Close this Browser.
Possible Cause:
The SSL VPN server is down.
Action:
Check the SSL VPN server health status and restart the server.
Possible Cause:
The Access Gateway is down.
Action:
Check the Access Gateway health status and start the gateway.
0x1011: This Operating System is not Supported. Please Logout.
Possible Cause:
Your operating system is not supported.
Action:
Contact your system administrator.
0x1012: User Does Not Seem to Have Enough Privilege. Please Log out.
Possible Cause:
The user does not have enough rights to start the SSL VPN client.
Action:
Contact your system administrator.
0x1014: Unable to Fetch CA Certificate from the Gateway
Possible Cause:
Either the certificate file is not present in the gateway or there is a problem with the connectivity.
Action:
Try disconnecting and reconnecting to the SSL VPN gateway. If the problem persists, contact your system administrator.
0x1016: Failed to Fetch CIC Policy from the Gateway
Possible Cause:
Either the gateway has closed the connection or there is a problem with the connectivity.
Action:
Try disconnecting and reconnecting to the SSL VPN gateway. If the problem persists, contact your system administrator.
0x1017: No Policies are Configured for this User
Possible Cause:
The administrator has not configured a policy for the user’s role.
Action:
Contact your system administrator
0x1018: Gateway Disconnected
Possible Cause:
The gateway might have gone down.
Action:
Contact your system administrator.
0x1019: Failed to Start the Client. Please Log out.
Possible Cause:
The SSL VPN components failed to start.
Action:
Try restarting the SSL VPN client. If the problem persists, contact your system administrator.
Object Does Not Support This Property or Method
Possible Cause:
ActiveX controls are not loaded into the Internet Explorer browser.
Action:
Add the Access Gateway URL to the trusted sites list in