The following table contains the error codes for LDAP Proxy:
|
Error Code |
Remedy |
|---|---|
|
Proxy Initialization Errors |
|
|
0x81510002 |
Cause: Insufficient memory. Action: Increase the free memory by shutting down services or increase the RAM. |
|
0x8151000D |
Cause: The evaluation copy has expired. Action:
Register the copy and insert the license key as specified in the documentation. See |
|
0x8151000E |
Cause: The proxy system was not properly initialized . Action: Internal error. |
|
0x8151000F |
Cause: The proxy server could not initialize itself because it was running as non-root, or had low system privileges . Action: Take appropriate action. |
|
0x81510100 |
Cause: The proxy server could not open the log file. Action: Check for the required permissions in the directory specified for logging. |
|
0x81510101 |
Cause: TLS initialization failed either because of the back-end server or the client. Action: Check for correct TLS/SSL certificates and their permissions and if they are present in the locations specified in the configuration. |
|
0x81510102 |
Cause: The TLS handshake failed. Action: Check for correct TLS/SSL certificates and their permissions and ensure that they are present in the locations specified in the configuration. |
|
0x81510103 |
Cause: Verification of the TLS certificate with the back-end server failed . Action: Check for correct TLS/SSL certificates and their permissions and ensure that they are present in the locations specified in the configuration. Also ensure that the back-end server is listening on TLS/SSL with the expected certificates. |
|
0x81510104 |
Cause: Another instance of proxy is already running. Action: If multiple proxy servers are configured to run on a single machine, ensure that their listening ports/interfaces and log directories are not the same. |
|
Thread Pool Errors |
|
|
0x81530102 |
Cause: The thread pool ran out of memory. Action: Increase the free memory by shutting down services or increase the RAM. |
|
Session Manager Errors |
|
|
0x81550102 |
Cause: The Session Manager ran out of memory. Action: Increase the free memory by shutting down services or increase the RAM. |
|
Socket Errors |
|
|
0x81540102 |
Cause: Socket logger initialization or SSL/TLS context initialization failed because of insufficient memory. Action: Increase free memory by shutting down services or increase the RAM. |
|
0x81570102 |
Cause: The socket monitor subsystem ran out of memory. Action: Increase free memory by shutting down services or increase the RAM. |
|
BER Errors |
|
|
0x81580002 |
Cause: Decoding/encoding because of insufficient memory. Action: Increase the free memory by shutting down services or increase the RAM. |
|
0x81580005 |
Cause: An invalid parameter was found when encoding the BER. Action: Ensure that the LDAP clients are sending proper LDAP requests. |
|
0x81580100 |
Cause: Decoding error. Action: Ensure that the LDAP clients are sending proper LDAP requests. This error might be transient. |
|
0x81580101 |
Cause: Encoding error. Action: Internal error. |
|
0x81580103 |
Cause: Fragment error while decoding. Action: Ensure that the LDAP clients are sending proper LDAP requests . |
|
LDAP Errors |
|
|
0x81590001 |
Cause: This LDAP feature is not implemented. |
|
0x81590002 |
Cause: The LDAP subsystem ran out of memory. Action: Increase free memory by shutting down services or increase the RAM. |
|
0x81590005 |
Cause: An invalid parameter was found in the LDAP request/response. |
|
0x81590006 |
Cause: An invalid LDAP request was received. |
|
0x8159000A |
Cause: The specified LDAP object was not found. |
|
0x81590100 |
Cause: An LDAP protocol error was encountered. |
|
0x81590101 |
Cause: An unsupported version of an LDAP request/response was encountered. |
|
0x81590102 |
Cause: An unsupported LDAP authentication method was encountered. |
|
0x81590103 |
Cause: The LDAP request received was too big. |
|
0x81590104 |
Cause: The LDAP response/request received was fragmented. |
|
0x81590107 |
Cause: No connection route to route this LDAP request was found. |
|
0x81590108 |
Cause: The LDAP DN received had invalid syntax. |
|
0x81590109 |
Cause: The LDAP URL received had invalid syntax. |
|
Policy Errors |
|
|
0x815B0001 |
Cause: This policy/action is not implemented. Action: Ensure that the configuration is consistent with the documentation. For more information, see Section 2.0, Configuring NetIQ LDAP Proxy . |
|
0x815B0002 |
Cause: The policy subsystem ran out of memory. Action: Increase free memory by shutting down services or increase the RAM. |
|
0x815B0100 |
Cause: The condition specified in the policy is invalid. Action: Ensure that the configuration is consistent with the documentation. For more information, see Section 2.0, Configuring NetIQ LDAP Proxy. |
|
0x815B0101 |
Cause: An unsupported policy was specified in the configuration. Action: Ensure that the configuration is consistent with the documentation. For more information, see Section 2.0, Configuring NetIQ LDAP Proxy. |
|
0x815B0102 |
Cause: A request unsupported by an action was received. Action: Internal error. |
|
0x815B0103 |
Cause: An unsupported action was specified in the policy. Action: Ensure that the configuration is consistent with the documentation. For more information, see Section 2.0, Configuring NetIQ LDAP Proxy. |
|
0x815B0104 |
Cause: Unsupported conditional operator was specified. Action: Ensure that the configuration is consistent with the documentation. For more information, see Section 2.0, Configuring NetIQ LDAP Proxy. |
|
0x815B0105 |
Cause: An unsupported conditional matching criterion was specified. Action: Ensure that the configuration is consistent with the documentation. For more information, see Section 2.0, Configuring NetIQ LDAP Proxy. |
|
0x815B0106 |
Cause: A request is denied as per policy. Action: Ensure that the connection-route policy for that particular connection/request should be denied. |
|
Back-end Errors |
|
|
0x815C0002 |
Cause: The back-end subsystem ran out of memory. Action: Increase free memory by shutting down services or increase the RAM. |
|
0x815C0100 |
Cause: A particular back-end server is not available. Action: Ensure that the configured back-end server is running and that the network settings allow the proxy server to communicate with the back-end server. |
|
0x815C0101 |
Cause: The maximum connection limit for a back-end server was exceeded. Action: The max-connections attribute specified for the particular back-end server has been exceeded. Increase the value for this attribute in the configuration or add more back-end servers. |
|
XML Errors |
|
|
0x815E0002 |
Cause: The XML Logger/XML parser ran out of memory. Action: Increase free memory by shutting down services or increase the RAM. |
|
0x815E0005 |
Cause: The XML parser encountered an invalid parameter. Action: Check the configuration for XML errors. |
|
0x815E000A |
Cause: The XML parser could not find an expected XML object . Action: Check the configuration file to see if it is consistent with the documentation. For more information, see Section 2.0, Configuring NetIQ LDAP Proxy. |
|
0x815E0100 |
Cause: The XML parser failed to parse . Action: Check the configuration file for XML errors . |
|
0x815E0101 |
Cause: The XML parser failed to parse the XML DOM. Action: Internal error. |
|
0x815E0102 |
Cause: Could not create the DOM. Action: Internal error |
|
0x815E0103 |
Cause: Could not initialize the DOM. Action: Internal error. |
|
0x815E0104 |
Cause: Could not serialize XML DOM. Action: Internal error. |
|
0x815E010A |
Cause: Multiple nodes were found when only one was expected. Action: Ensure that the configuration file is consistent with the documentation. For more information, see Section 2.0, Configuring NetIQ LDAP Proxy. |
|
Configuration Errors |
|
|
0x815F0001 |
Cause: The configuration directive is not implemented . Action: Check the documentation for the supported policy, conditions, or actions. For more information, see Section 2.0, Configuring NetIQ LDAP Proxy. |
|
0x815F0002 |
Cause: The configuration subsystem ran out of memory. Action: Increase free memory by shutting down services or increase the RAM. |
|
0x815E010A |
Cause: The configuration is incomplete. It does not specify a required configuration object. Action: Check the configuration file for errors. |
|
0x815E010C |
Cause: A policy object already exists. Action: Multiple policies must have separate IDs. |
|
0x815F0100 |
Cause: Could not read the configuration file or schema configuration file. Action: Ensure that the nlpschemaconf.xml schema configuration file is in the default location of /etc/opt/novell/ldapproxy/conf/ and that the permissions are sufficient. |
|
0x815F0101 |
Cause: The Schema configuration file is invalid . Action: Check the nlpschemaconf.xml schema configuration file for errors. |
|
0x815F0102 |
Cause: A data value specified in the configuration file is invalid. Action: Check the configuration file for XML errors or other inconsistencies . |
|
0x815F0103 |
Cause: An XML node specified in the configuration file is invalid. Action: Check the configuration file for XML errors or other inconsistencies. |
|
0x815F0104 |
Cause: Two listener nodes were found with the same ID. Action: Multiple listener configuration nodes must have different IDs. |
|
0x815F0105 |
Cause: The directory path to the log files specified in the configuration is invalid. Action: Check to see if the directory path specified is correct. |
|
0x815F0106 |
Cause: Unable to create the directory path for logging as specified in the configuration. Action: Ensure that the appropriate permissions are in place for the directory path specified. |
|
0x815F0107 |
Cause: The domain name specified in the configuration could not be resolved. Action: Check your DNS configuration or specify an IP address instead of DNS name. |
|
0x815F0108 |
Cause: Reading the network interface corresponding to the IP/Domain Name given in the configuration failed. Action: Ensure that your network settings for the IP/Domain Name are bound to a network interface as expected. |
|
0xffffe908 |
Cause: Proxy listener was started with a port which was being used by other services Action: Use a different port to start Proxy listener. |
|
0x815f000a |
Cause: The connection route policy in nlpconf.xml referred to a backend group which did not exist. Action: Change the connection route policy to use a backend group which is defined in nlpconf.xml. |
|
Audit/Event Subsystem Errors |
|
|
0x815D0001 |
Cause: An audit event was received but has not been implemented. Action: Check documentation for the supported audit events. For more information, see Configuring Audit Events. |
|
0x815D0002 |
Cause: The Audit subsystem ran out of memory . Action: Increase free memory by shutting down other services or increase the RAM. |
|
0x815D0005 |
Cause: The ID of the event object is invalid . Action: Internal error. |
|
0x815D0006 |
Cause: The audit subsystem received an invalid request. Action: Internal error. |
|
0x815D0008 |
Cause: The audit subsystem failed to register a producer event because no event data was found. Action: Internal error |
|
0x815D000A |
Cause: The specified event object was not found. Action: Internal error . |
|
0x815D000C |
Cause: An event object with the same ID is already present. Action: |
|
0x815D0100 |
Cause: Invalid event data was received. Action: Internal error . |