Page 1 AUTHORIZED DOCUMENTATION Event Codes Novell ® Access Manager 3.1 SP1 July 15, 2009 www.novell.com Novell Access Manager 3.1 SP1 Event Codes...
Page 2 Further, Novell, Inc., reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
Page 3 Novell Trademarks For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/ trademarks/tmlist.html). Third-Party Materials All third-party trademarks are the property of their respective owners.
Page 4 Novell Access Manager 3.1 SP1 Event Codes...
Page 5: Table Of Contents
4 Linux Access Gateway Appliance(045) 5 SSL VPN Server (005) 6 J2EE Agents (006) 7 Server Communications (JCC) (007) 8 Policy Engine (008) 9 SOAP Policy Enforcement Point (011) 10 Backup and Restore (010) 11 Novell Modular Authentication Class (012) Contents...
Page 6 Novell Access Manager 3.1 SP1 Event Codes...
Page 7: About This Guide
Chapter 9, “SOAP Policy Enforcement Point (011),” on page 131 Chapter 10, “Backup and Restore (010),” on page 137 Chapter 11, “Novell Modular Authentication Class (012),” on page 143 Audience This guide is intended for Access Manager administrators. It is assumed that you have knowledge of...
Page 8 Novell Access Manager 3.1 SP1 Installation Guide Novell Access Manager 3.1 SP1 Agent Guide Documentation Conventions In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. ® A trademark symbol ( , etc.) denotes a Novell trademark.
Page 9: Event Code Overview
Chapter 8, “Policy Engine (008),” on page 125 Chapter 9, “SOAP Policy Enforcement Point (011),” on page 131 Chapter 10, “Backup and Restore (010),” on page 137 Chapter 11, “Novell Modular Authentication Class (012),” on page 143 Event Code Overview...
Page 10 Novell Access Manager 3.1 SP1 Event Codes...
Page 11: Administration Console (009)
Cause: The Administration Console was not installed correctly or has become corrupt. Action: Verify installation. 100901004 Error in Cause: Servlet error when retrieving data CertHandler.getMultipartParamValue. from a multipart form. Action: Submit log to Novell Support for analysis and resolution. Administration Console (009)
Page 12 Server or during the creation of an Identity Server Configuration. Check to make sure that there are no corrupt Identity Server configurations. If the signing keystore does exist, add or replace a certificate. Novell Access Manager 3.1 SP1 Event Codes...
Page 13 Error in init (using reflection to call a Cause: The java class is unable to locate method has failed in init). another java class through reflection. Action: Submit log to Novell Support for analysis and resolution. 700901014 Cannot add non-existent key to keystore.
Page 14 Identity Server or Access Gateway devices but the keystore cannot be found. Action: Verify that the Identity Servers and Access Gateway devices had no errors during import to the Administration Console. Try to re-import the devices. Novell Access Manager 3.1 SP1 Event Codes...
Page 15 Remedy Event Code Description 100901027 Error in Cause: The cluster keystore representation CertHandler.getNIDPDeviceKeystoreNam object was not found. e (The name of the device's keystore was Cause: The cluster keystore representation not found). did not have a device type specified. Action: Delete and recreate the Identity Server Configuration or Access Gateway Group that is causing the problem and then re-add the members.
Page 16 Action: Select a valid keystore. process. Cause: The specified source key does not exist. Action: Verify that the key you have specified to export the public certificate from exists. Novell Access Manager 3.1 SP1 Event Codes...
Page 17 Java keystore, and is not corrupted. To check its status, enter the following command: /opt/novell/java/bin/keytool -v - list -keystore devman.cacerts Otherwise, be sure the config store is running and functioning properly. Administration Console (009)
Page 18 100902011 Error - Exception reading (the given ESP) Cause: The file required during the import process could not be read. Action: Be sure the indicated file can be read by the novlwww user. Novell Access Manager 3.1 SP1 Event Codes...
Page 19 Remedy Event Code Description 100902012 Error - Could not import LDIF. Cause: The error occurred while creating the configuration for the Embedded Service Provider. Action: Go to Access Gateway Server List and click Repair Import. (The repair import functionality works for any server type.) Otherwise, submit the app_sc.0.log file...
Page 20 Error - Exception thrown in Cause: Error occurred in processing the processAGResponse method of response from an Access Gateway server. vcdn.application.sc.config.AGConfigWork Action: Ensure the server component is operating properly. Otherwise, submit the file for resolution. app_sc.0.log Novell Access Manager 3.1 SP1 Event Codes...
Page 21 Remedy Event Code Description 100902026 Error - VCDNException thrown in Cause: Error occurred while sending performConfiguration method of configuration to J2EE Agent server. vcdn.application.sc.config.AgentApplyWor Action: Ensure the server component is operating properly. Otherwise, submit the app_sc.0.log file for resolution. 100902027 Error - VCDNException thrown in Cause: Error occurred in processing the responseReceived method of...
Page 22 Otherwise, submit the file for resolution. app_sc.0.log 100902042 Error - Exception thrown in Cause: Error occurred while re-applying a removePendingFromFailedList method of server configuration. vcdn.application.sc.config.DeviceGroupCo Action: Submit the app_sc.0.log file for nfigWork resolution. Novell Access Manager 3.1 SP1 Event Codes...
Page 23 Remedy Event Code Description 100902043 Error - SchedulerException thrown in Cause: Error occurred while scheduling a scheduleMultiDeviceWorks method of group configuration. vcdn.application.sc.config.DeviceGroupCo Action: Submit the app_sc.0.log file for nfigWork resolution. 100902044 Error - Exception thrown in the execute Cause: Error occurred while scheduling a method of group configuration.
Page 24 Cause: Error occurred while sending a execute method of command to an Identity Server ESP server. vcdn.application.sc.command.IDPComma Action: Ensure the server component is ndWork functioning correctly. Otherwise, submit the file for resolution. app_sc.0.log Novell Access Manager 3.1 SP1 Event Codes...
Page 25 Remedy Event Code Description 100902059 Error - VCDNException thrown in the Cause: Error occurred while sending a sendCommand method of command to an Identity Server or ESP vcdn.application.sc.command.IDPComma server. ndWork Action: Ensure the server component is functioning correctly. Otherwise, submit the app_sc.0.log file for resolution.
Page 26 Otherwise, submit the file for resolution. app_sc.0.log 100902075 Error - JDOMException thrown in the Cause: Audit XML data could not be parsed. processDocument method of Action: Submit the app_sc.0.log file for vcdn.application.sc.core.AuditManager resolution. Novell Access Manager 3.1 SP1 Event Codes...
Page 27 100902084 Error - NullPointerException thrown in the Cause: Error logging Novell Audit event. logEvent method of Action: Ensure the Novell Audit server is vcdn.application.sc.core.AuditManager functioning properly. Otherwise, submit the app_sc.0.log file for resolution. Administration Console (009)
Page 28 Action: Non-fatal error. 100902094 Error deleting the trusted IDP entry for Cause: Error accessing config store. ESP. Action: Ensure the config store is functioning properly. Otherwise, submit the app_sc.0.log file for resolution. Novell Access Manager 3.1 SP1 Event Codes...
Page 29 Action: Verify the config store is up and that the user has rights to create objects in the following container: ou=KeyContainer,ou=Partition,ou=P artitionsContainer,ou=VCDN_root,o u=accessManagerContainer,o=novell Administration Console (009)
Page 30 Action: Verify the config store is up and that the user has rights to modify objects in the following container: ou=KeyContainer,ou=Partition,ou=P artitionsContainer,ou=VCDN_root,o u=accessManagerContainer,o=novell Novell Access Manager 3.1 SP1 Event Codes...
Page 31 Remedy Event Code Description 100902108 Error - Exception thrown in the Cause: Error creating an element in the createElement method of specified XML document. vcdn.application.sc.core.PolicyConfig Action: Submit the app_sc.0.log file for resolution. 100902109 Error - Exception thrown in the Cause: Error setting an attribute value on setLastModified method of modified elements.
Page 32 100903004 Error - DelayedResponseListener thread Cause: Error occurred while processing a failed to start. delayed response. Action: Ensure the server component is functioning correctly. Otherwise, submit the app_sc.0.log file for resolution. Novell Access Manager 3.1 SP1 Event Codes...
Page 33 Remedy Event Code Description 100903005 Error in the ResponseHandler thread of Cause: Error occurred while processing a the DelayedResponseListener. response. Action: Ensure the server component is functioning correctly. Otherwise, submit the app_sc.0.log file for resolution. 100903006 Error creating XML Element in Cause: Error occurred while editing XML.
Page 34 100904007 Error - Exception thrown in getPolicyInfo of Cause: Error occurred while getting policy WebManager. information. Action: Ensure the server component is functioning correctly. Otherwise, submit the app_sc.0.log file for resolution. Novell Access Manager 3.1 SP1 Event Codes...
Page 35 Remedy Event Code Description 100904008 Error - Exception thrown in Cause: Error occurred while getting policy getTypeSpecificationInfo of WebManager. type specification information. Action: Ensure the server component is functioning correctly. Otherwise, submit the app_sc.0.log file for resolution. 100904009 Error - Exception thrown in Cause: Error occurred while getting device getDeviceConfig of WebManager.
Page 36 100904023 Error - Exception thrown in Cause: Error occurred while applying do_deviceConfig of configuration. ConfigWorkDispatcher. Action: Ensure the server component is functioning correctly. Otherwise, submit the file for resolution. app_sc.0.log Novell Access Manager 3.1 SP1 Event Codes...
Page 37 Remedy Event Code Description 100904024 Error - Exception thrown in Cause: Error occurred while scheduling do_scheduleDeviceConfig of configuration. ConfigWorkDispatcher. Action: Ensure the server component is functioning correctly. Otherwise, submit the app_sc.0.log file for resolution. 200904025 Error - XML VALIDATION FAILED. Cause: XML created by GUI does not match PLEASE CHECK APP_SC LOG.
Page 38 100904039 Error - Could not find signing keystore for Cause: An error occurred during the import {0}. of the device. Action: Consult the documentation and re- import the device into the Administration Console. Novell Access Manager 3.1 SP1 Event Codes...
Page 39 Remedy Event Code Description 100904040 Error - Could not find encryption keystore Cause: An error occurred during the import for {0}. of the device. Action: Consult the documentation and re- import the device into the Administration Console. 100904041 Error - Could not find connector keystore Cause: An error occurred during the import for {0}.
Page 40 Error getting health info. Cause: Error occurred while getting health information for a server. Action: Ensure the server component and the config store are functioning correctly. Otherwise, submit the app_sc.0.log file for resolution. Novell Access Manager 3.1 SP1 Event Codes...
Page 41 Remedy Event Code Description 100905007 Error canceling appliance creation. Cause: Internal error. Action: Submit the app_sc.0.log file for resolution. 100905008 Error creating new CDN. Cause: Internal error. Action: Submit the app_sc.0.log file for resolution. 100905009 Error removing CDN. Cause: Internal error. Action: Submit the file for app_sc.0.log...
Page 42 Otherwise, submit the app_sc.0.log file for resolution. 100905026 Error - Exception thrown in Cause: Internal error. processRequest of GenericPipeHandler: Action: Ensure the config store is functioning correctly. Otherwise, submit the file for resolution. app_sc.0.log Novell Access Manager 3.1 SP1 Event Codes...
Page 43 Remedy Event Code Description 100905027 Error occurred while creating group {0} : Cause: Internal error. {1}. Action: Ensure the config store is functioning correctly or delete the group and recreate it. Otherwise, submit the app_sc.0.log file for resolution. 100905028 Error getting device manager in Cause: Internal error.
Page 44 Otherwise, submit the file for resolution. app_sc.0.log 100905043 Error - Exception thrown in Cause: Internal error. processRequest of SyncHandler. Action: Ensure the config store is functioning correctly. Otherwise, submit the app_sc.0.log file for resolution. Novell Access Manager 3.1 SP1 Event Codes...
Page 45 Remedy Event Code Description 100905044 Error - Exception thrown in Cause: Internal error. modifySystemSync of SyncHandler. Action: Ensure the config store is functioning correctly. Otherwise, submit the app_sc.0.log file for resolution. 100905045 Error - WSException thrown in Cause: Internal error. isAssignedUser of GroupCreateBean.
Page 46 Otherwise, submit the app_sc.0.log file for resolution. 100905063 Error - Exception thrown in clusterServers Cause: Internal error. of GroupCreateBean. Action: Ensure the config store is functioning correctly. Otherwise, submit the file for resolution. app_sc.0.log Novell Access Manager 3.1 SP1 Event Codes...
Page 47 Remedy Event Code Description 100905064 Error - VException thrown in getAdminList Cause: Internal error. of GroupCreateBean. Action: Ensure the config store is functioning correctly. Otherwise, submit the app_sc.0.log file for resolution. 100905065 Error - Exception thrown in callRestartESP Cause: Error occurred while restarting of SPConfigHandler.
Page 48 Error - Exception thrown in executeNow Cause: Error occurred while scheduling method of ScheduleHandler. work. Action: Ensure the config store and server component are functioning correctly. Otherwise, submit the file app_sc.0.log for resolution. Novell Access Manager 3.1 SP1 Event Codes...
Page 49 Action: To diagnose time synchronization issues with multiple Administration Consoles, run the following command on the primary server command-line: /opt/novell/eDirectory/bin/ ndsrepair -T This will check the overall time synchronization status. If the time is not in sync, then you might want to consider configuring NTP on each server.
Page 50 Attempting to update policy status on Cause: Informational message. devices because the policy extension Action: No action necessary. changed. 500906001 Setting update policy status for device. Cause: Informational message. Action: No action necessary. Novell Access Manager 3.1 SP1 Event Codes...
Page 51: Identity Server (001)
If you are seeing this error after changing the IP address of the Linux Access Gateway, restart Tomcat on the Identity Server. For additional help, see “Troubleshooting 100101043 and 100101044 Liberty Metadata Load Errors” in the Novell Access Manager 3.1 SP1 Identity Server Guide. Identity Server (001)
Page 52 IDP is set incorrectly. For additional help, see “Troubleshooting 100101043 and 100101044 Liberty Metadata Load Errors” in the Novell Access Manager 3.1 SP1 Identity Server Guide. 100101045 An error happened while the Type: SEVERE:NIDP:USERMSG:045 request was being sent to the Cause: The target cluster member may be unavailable.
Page 53 Type: SEVERE:NIDP:WSF:005 Secret Store. Cause: The LDAP connection between the IDP and the User Store must be secure LDAP if Novell Secret Store is to be used as the back end storage for Credential Profile. Action: Go to the associated user store and change the connection type to secure LDAP.
Page 54 Action: Create and enable a Liberty Discovery Service using the Access Manager administration utility. 100102026 Type: SEVERE:NIDP:WSF:026 100102027 Type: SEVERE:NIDP:WSF:027 100102028 Type: SEVERE:NIDP:WSF:028 100102029 Type: SEVERE:NIDP:WSF:029 100102030 Type: SEVERE:NIDP:WSF:030 100102031 Type: SEVERE:NIDP:WSF:031 Novell Access Manager 3.1 SP1 Event Codes...
Page 55 Event Code Message Remedy 100102032 Type: SEVERE:NIDP:WSF:032 100102033 Type: SEVERE:NIDP:WSF:033 100103001 Web Service Consumer XML Type: SEVERE:NIDP:WSC:001 Configuration Parse Cause: The nidsConfigXML attribute on the nidsWsf Exception. object has invalid XML. Action: Delete the nidsConfigXML attribute and reconfigure WSC. 100103002 Type: SEVERE:NIDP:WSC:002 100103003 Type: SEVERE:NIDP:WSC:003...
Page 56 This second call to the extension failed, so directory user account status may be erroneous. Action: Check with eDirectory documentation for LDAP extension with OID 2.16.840.1.113719.1.39.42.100.25 100105006 Type: SEVERE:NIDP:APP:006 100105007 Type: SEVERE:NIDP:APP:007 Novell Access Manager 3.1 SP1 Event Codes...
Page 57 Event Code Message Remedy 100105008 The audit logging system is Type: SEVERE:NIDP:APP:008 not operational. Cause: The audit logging system can, in rare circumstances, become non-operational. Action: Examine the error description supplied and take appropriate action. 100106001 Type: SEVERE:NIDP:IDFF:001 200102001 Invalid access code found for Type: ERROR:NIDP:WSF:001 web service specific user Cause: The web service definition has a service level...
Page 58 Error processing web service Type: ERROR:NIDP:WSF:013 query request. Cause: Processing web service requests may result in a number of unexpected errors. Action: Evaluate the reason given in the error message, and take appropriate action. Novell Access Manager 3.1 SP1 Event Codes...
Page 59 Event Code Message Remedy 200102014 Error processing web service Type: ERROR:NIDP:WSF:014 modify request. Cause: Processing web service requests may result in a number of unexpected errors. Action: Evaluate the reason given in the error message, and take appropriate action. 200102015 Unable to locate the user's Type: ERROR:NIDP:WSF:015 local identifier in the resource...
Page 60 Cause: The Certificate has been revoked Action: Use a valid certificate which is not revoked. 200104012 Error Parsing Certificate. Type: ERROR:NIDP:USERAUTH:012 Cause: Error Parsing Certificate when performing certificate validations Action: Use a valid X509 certificate. Novell Access Manager 3.1 SP1 Event Codes...
Page 61 Event Code Message Remedy 200104017 Error getting CRL/OCSP. Type: ERROR:NIDP:USERAUTH:017 Cause: Could not get to the CRL/OCSP URL for validations. Action: Make sure the CRL/OCSP URLs are accessible Or disable validations in administration. Additionally, can define a different CRL/OCSP URL in the administration tool which the X509Class can also use for validations.
Page 62 200104031 The server could not Type: ERROR:NIDP:USERAUTH:031 authenticate you. Cause: OCSP server could not authenticate Novell Identity server. Action: Make sure Signing of OCSP requests is enabled and NIDP signing keystore has appropriate key in it. Also, make sure the OCSP server trusts Nidp server.
Page 63 Event Code Message Remedy 200104032 Unknown OCSPResponse Type: ERROR:NIDP:USERAUTH:032 status code. Cause: OCSP server responded to the request with unknown status code. Action: Contact OCSP server administrator. 200104033 No valid OCSPResponse Type: ERROR:NIDP:USERAUTH:033 obtained. Cause: Invalid OCSP response obtained. Action: Check the OCSP server response version and contact administrator.
Page 64 If needed, add the processing of the critical extension in NDPCertPathChecker class. 200104053 Error processing CRL Type: ERROR:NIDP:USERAUTH:053 Response. Cause: Error processing CRL Response. Action: Check X509class config and user/client certificate CRL extension. Novell Access Manager 3.1 SP1 Event Codes...
Page 65 Event Code Message Remedy 200104054 Error processing certificate Type: ERROR:NIDP:USERAUTH:054 validations. Cause: Error processing CRL/OCSP validations. Action: Check X509class config and user/client certificate CRL extension. 200104055 Protocol not supported or Type: ERROR:NIDP:USERAUTH:055 none specified. Cause: Transport protocol not supported to fetch CRL. Action: Currently, CRLs can be fetched over http and LDAP protocols.
Page 66 300101004 Identity does not exist or is not Type: WARN:NIDP:USERMSG:004 specified. Cause: An action was attempted that requires a federated identity to exist. Action: Create a federated link prior to performing the action. Novell Access Manager 3.1 SP1 Event Codes...
Page 67 Event Code Message Remedy 300101005 Invalid or no provider is Type: WARN:NIDP:USERMSG:005 specified. Cause: An action was requested related to a trusted provider that does not exist. Action: Add the desired provider as a trusted entity or check for invalid access to system. 300101006 An authenticated session is Type: WARN:NIDP:USERMSG:006...
Page 68 Cause: An assertion was received that had a time validity period that is in the past. Action: Check server's clock for accuracy. Attempt to validate the clock accuracy of the computer generating the assertion. Try to authenticate again. Novell Access Manager 3.1 SP1 Event Codes...
Page 69 Liberty or SAML protocol message. Action: Turn logging/tracing on to print out the message that is problematic. It may be necessary to contact Novell Technical Services in this case. 300101023 User lookup failed. Type: WARN:NIDP:USERMSG:023 Cause: An attempt to identify a user failed while attempting to complete a federation at the server.
Page 70 Action: Try and re-authenticate. Determine if there are any network latencies that may cause the assertion not to arrive in a timely fashion. Look for misuse of the assertion. Novell Access Manager 3.1 SP1 Event Codes...
Page 71 Event Code Message Remedy 300101033 IDP return authentication Type: WARN:NIDP:USERMSG:033 failure. Cause: An IDP's attempt to authenticate the server was unsuccessful. This particular authentication came from the IDP's intersite transfer service and was not requested by the server. Action: Check at the IDP for a reason why the authentication was a failure.
Page 72 300101047 An untrusted provider is being Type: WARN:NIDP:USERMSG:047 referenced in a request or a Action: Use logs to determine the provider that is response. untrusted and then create a trusted relationship if desired. Novell Access Manager 3.1 SP1 Event Codes...
Page 73 Event Code Message Remedy 300101048 The LDAP servers are too Type: WARN:NIDP:USERMSG:048 busy to accept more users. Cause: There are too many threads waiting to get an available LDAP connection. The LDAP servers are too busy to accept more users. Action: Wait a few moments for the LDAP requests to be processed and retry the request.
Page 74 Trusted user interaction Type: WARN:NIDP:WSF:008 service failed. Cause: There are various unexpected reasons for the failure of a trusted user interaction service request to fail. Action: Evaluate the reason and take the appropriate actions. Novell Access Manager 3.1 SP1 Event Codes...
Page 75 Event Code Message Remedy 300102009 Error creating user interaction Type: WARN:NIDP:WSF:009 redirection request. Cause: There was an error converting the redirect request to an XML DOM. Action: Evaluate the reason and take the appropriate actions. 300102010 Unable to perform user Type: WARN:NIDP:WSF:010 interaction redirection Cause: There must be an interaction service on the IDP...
Page 76 Action: This waiting period may be increased by click Access Manager > Identity Servers > Edit > Liberty > Web Service Consumer, and setting the Protocol Timeout to a higher value. Novell Access Manager 3.1 SP1 Event Codes...
Page 77 Event Code Message Remedy 300103002 An unexpected error Type: WARN:NIDP:WSC:002 happened in the web service Cause: There are various reasons why a web service consumer while processing a request could fail. web service request. Action: Evaluate the reason and take appropriate actions.
Page 78 300105010 Type: WARN:NIDP:APP:010 300105011 Type: WARN:NIDP:APP:011 300105012 Type: WARN:NIDP:APP:012 300105013 Type: WARN:NIDP:APP:013 300105014 Type: WARN:NIDP:APP:014 300105015 Type: WARN:NIDP:APP:015 300105016 Type: WARN:NIDP:APP:016 300105017 Type: WARN:NIDP:APP:017 300105018 Type: WARN:NIDP:APP:018 300105019 Type: WARN:NIDP:APP:019 300105020 Type: WARN:NIDP:APP:020 Novell Access Manager 3.1 SP1 Event Codes...
Page 79 Event Code Message Remedy 300105021 Unable to delete unneeded Type: WARN:NIDP:APP:21 Image Pool Image File. Cause: On startup, the NIDP Image Pool is synchronized from eDirectory to the file system. This allows HTML pages to access images from a well known file system structure.
Page 80 Cause: The java.lang.Class.forName() method call failed to load the LDAP Store Plugin class. Action: Ensure a valid Java class file is available in Access Manager's class path for the referenced plugin class file. Novell Access Manager 3.1 SP1 Event Codes...
Page 81 Event Code Message Remedy 300105030 Cannot instantiate a custom Type: WARN:NIDP:APP:30 LDAP Store Plugin module. Cause: The java.lang.Class.newInstance() method call failed to instantiate the LDAP Store Plugin class. Action: Ensure a valid Java class file is available in Access Manager's class path for the referenced plugin class file.
Page 82 The request indicated that a trusted user interaction service should be used to perform user interaction, so that service is being invoked using the trusted user interaction service protocol. Novell Access Manager 3.1 SP1 Event Codes...
Page 83 Event Code Message Remedy 500102011 Read Credential Profile data Type: INFO:NIDP:WSF:011 from Novell Secret Store. Scenario: A request was made to query data from a user's Credential Profile. The data was successfully read. See Also: 600102008 500102012 Read Credential Profile data...
Page 84 Successfully initialized JNDI Type: INFO:NIDP:APP:002 connections. Scenario: NIDP attempts to create JNDI connections to each user store replica during NIDP startup. In this case, NIDP was able to establish connections with the indicated host. Novell Access Manager 3.1 SP1 Event Codes...
Page 85 Event Code Message Remedy 500105003 Failed X509 authentication Type: INFO:NIDP:APP:003 due to Login Policy Check Scenario: The directory login policy for the indicated Extension Method evaluation. user denied login. 500105004 An recoverable error Type: INFO:NIDP:APP:004 happened while forwarding a Scenario: The request landed on the wrong cluster login request.
Page 86 Type: DEBUG:NIDP:WSF:001 information. Scenario: Adds verbose authentication data to the fact that the user associated with the attribute request was found in the internal databases of the web service provider. See Also: 500102001 Novell Access Manager 3.1 SP1 Event Codes...
Page 87 Event Code Message Remedy 600102002 Verbose user authentication Type: DEBUG:NIDP:WSF:002 information, attribute select Scenario: A Web Service request was made to query string, and data. user attributes. One of the data locations specified for the service is the Liberty User Profile object. The data listed in this message was successfully read for the indicated user using the indicated XPath.
Page 88 See Also: 500102011 600102009 The user successfully logged Type: DEBUG:NIDP:WSF:009 into Novell Secret Store using Scenario: To access secrets from Novell Secret Store, SAML/SASL. the user must authenticate to Novell Secret Store. 600102010 Adds verbose data to reading Type: DEBUG:NIDP:WSF:010...
Page 89 Event Code Message Remedy 600105006 Must proxy HTTP request to Type: DEBUG:NIDP:APP:006 other cluster member. Scenario: Each request must be processed on the cluster member that owns the user authentication information. It has been determined that this cluster member is not the correct cluster member to process this request, so the request must be forwarded to another cluster member.
Page 90 Novell Access Manager 3.1 SP1 Event Codes...
Page 91: Linux Access Gateway Appliance(045)
Linux Access Gateway Appliance(045) Component 045 Remedy Event Code Description [1-9]04501000 Multi-homing See the string value in the message for a description of the cause. [1-9]04502000 Service manager See the string value in the message for a description of the cause. [1-9]04503000 Browser request processing See the string value in the message...
Page 92 [1-9]04521000 Proxy start See the string value in the message for a description of the cause. [1-9]04522000 Audit event processing See the string value in the message for a description of the cause. Novell Access Manager 3.1 SP1 Event Codes...
Page 93: Ssl Vpn Server (005)
Remedy Event Code Description Server Event Codes 20050101200 Error executing sockd Cause: The /opt/novell/sslvpn/bin/sockd file may not be present, or not executable or corrupted Action: Check if the binary is present and has correct permissions. Installation may be a problem...
Page 94 2005010120C Failed to parse Stunnel certificate. Cause: Stunnel Certificate is in bad format error code = XXXX Action: Recreate the Stunnel certificate in device manager and apply changes to the device Novell Access Manager 3.1 SP1 Event Codes...
Page 95 Gateway is in bad state to sockd. Failed to send the new Action: Restart the sslvpn service and restart connection notification to sockd. Failed the novell-tomcat where sslvpn servlet is to send servlet response to fd. Failed running to send servlet init success response to fd, fd.
Page 96 Check log(/var/log/messages) invalid. Action: Check the file and config.xml correct it. 50050101409 Invalid argument Cause: The user has entered invalid arguments. Action: Use the sslvpnc –help command to discover the valid arguments. Novell Access Manager 3.1 SP1 Event Codes...
Page 97: J2Ee Agents (006)
J2EE Agents (006) Component 006 Subgroup 01: Management Subgroup 02: Authentication (JAAS) Subgroup 03: Authorization (JACC) Subgroup 99: Policy PEP Message Remedy Event Code 100601001 Could not find initial XML configuration in Cause: An initial XML configuration should classPath exists in the NidsCommonAgent.jar doesn’t when this error occurs.
Page 98 Cause: Unexpected error in WebSphere and credential Action: Submit requested logs/data. 100602009 WebSphere is not configured with global Cause: WebSphere does not have global and server security security enabled. Action: Enable WebSphere for global and server security. Novell Access Manager 3.1 SP1 Event Codes...
Page 99 Send logs to support. 100602012 An error was encountered in reflection Cause: WebLogic API has been changed. code to get moduleID from Action: Contact Novell Support. HttpServletRequest 100602013 An Error occurred decoding a soap Cause: Java is corrupt and does not support...
Page 100 200699002 Invalid input data. Invalid data has been Action: See supplementary messages in logs received which prevents policy from being for indication of specific problem. evaluated. 100 Novell Access Manager 3.1 SP1 Event Codes...
Page 101 Action: You can take any or all of the following actions: 1) Submit the log file (which includes an AM#500699030 log entry containing the policy configuration) to Novell Support to facilitate fixing the Administration Console. 2) Back up to a previous policy configuration that worked until the Administration Console has been fixed.
Page 102 Cause: A user has been granted access to a protected EJB resource. Action: None. Informational only. 500699043 J2EE Agent EJB Access Denied. Cause: A user has been denied access to a protected EJB resource. Action: None. Informational only. 102 Novell Access Manager 3.1 SP1 Event Codes...
Page 103: Server Communications (Jcc) (007)
Server Communications (JCC) (007) Component 007 Subgroup 01: Package com.novell.jcc.cert Subgroup 02: Package com.novell.jcc.client Subgroup 03: Package com.novell.jcc.handler Subgroup 04: Package com.novell.jcc.proxy Subgroup 05: Package com.novell.jcc.schedule Subgroup 06: Package com.novell.jcc.server Subgroup 07: Package com.novell.jcc.servlet Subgroup 08: Package com.novell.jcc.sockets Subgroup 09: Package com.novell.jcc.util...
Page 104 Action: Submit the jcc-0.log.0 file for resolution. 100701015 Exception - loading keystore failed Cause: The encrypted keystore_info.xml file could not be read. Action: Reinstall the server component. Otherwise, submit the file for jcc-0.log.0 resolution. 104 Novell Access Manager 3.1 SP1 Event Codes...
Page 105 Bad health URL Cause: The IP address or port setting for the administration console has been corrupted. Action: Make sure the settings.properties file contains correct information. Restart the novell- jcc service. 100702008 Error sending alert Cause: The system cannot communicate with the administration console.
Page 106 100702017 Error sending periodic health Cause: The system cannot communicate with the administration console. Action: Make sure the system can communicate with the administration console and that it is functioning properly. 106 Novell Access Manager 3.1 SP1 Event Codes...
Page 107 100702022 Error binding to RMI port Cause: The novell-jcc service is not running, or the RMI ports are already bound by some other process. Action: Make sure the installation completed successfully, and that the novell-jcc service is running.
Page 108 Description 100702025 Error sending alert to server Cause: An RMI communication error likely occurred while sending an alert to the novell- jcc service. Action: Make sure that the novell-jcc service is running. Otherwise, restart it. If the problem persists, submit the jcc-0.log.0...
Page 109 100704002 AGProxy has not initialized as client is Cause: The proxy subcomponent is not null initialized. Action: Restart the novell-jcc service. Otherwise, submit the jcc-0.log.0 file for resolution. 100704003 Command returned: [response code] Cause: The Access Gateway is processing a [response message], Retry # previous command.
Page 110 Exception - check esp status failed Cause: An RMI error occurred while communicating to the ESP component. Action: Allow the operation to retry. If it persists, submit the file for jcc-0.log.0 resolution and restart the server. 110 Novell Access Manager 3.1 SP1 Event Codes...
Page 111 Administration Console to resolve. Otherwise, submit file for resolution. jcc-0.log.0 100704022 Linux Proxy is not running Cause: The proxy novell-vmc service has stopped responding. Action: to restart the proxy service, enter the following command as root user: /etc/init.d/novell-vmc restart Server Communications (JCC) (007)
Page 112 Cause: An IO error occurred while writing the sslvpn.id file during the reimport process. Action: Restart the novell-jcc service. Click Repair Import in the Administration Console to resolve. Otherwise, submit file jcc-0.log.0 for resolution. 112 Novell Access Manager 3.1 SP1 Event Codes...
Page 113 Error getting SSLVPN stats Cause: Could not communicate with SSLVPN service to obtain statistics. Action: To restart the SSLVPN service, enter the following commands: /etc/init.d/novell-sslvpn stop /etc/init.d/novell-sslvpn start 100704032 Error getting SSLVPN health Cause: Could not communicate with SSLVPN service to obtain the health.
Page 114 Cause: An IO error occurred while saving the list of registered server components. Action: Make sure the file has write access. If the problem persists, submit the jcc- 0.log.0 file for resolution. 114 Novell Access Manager 3.1 SP1 Event Codes...
Page 115 Remedy Event Code Description 100706004 Client list cannot be restored Cause: An IO error occurred while reading the list of registered server components. Action: Make sure the file has read access. If an upgrade has been performed, make sure all components on the system have also been upgraded.
Page 116 Action: Make sure there are no other processes using this port, then restart the service. 100706021 RMI problem Cause: An error occurred during the shutdown process. Action: This is a non-fatal error. 116 Novell Access Manager 3.1 SP1 Event Codes...
Page 117 Action: This is a non-fatal error. 100706023 Server did not initialize within 60 seconds Cause: A server component initialization message could not be completed as the novell- jcc service is not finished initializing. Action: To restart the novell-jcc service, enter the following command: /etc/init.d/novell-jcc restart...
Page 118 Cause: An assigned key could not be obtained during a reimport operation. Action: Allow the operation to retry. Ensure the admin console is operational, perform the steps to re-trigger an auto-import. Otherwise, submit jcc-0.log.0 app_sc.0.log files for resolution. 118 Novell Access Manager 3.1 SP1 Event Codes...
Page 119 100706042 RMI exception Cause: A communication error occurred. Action: Make sure the server component is running properly. If the problem persists, submit the file for resolution. jcc-0.log.0 Package com.novell.jcc.servlet Server Communications (JCC) (007) 119...
Page 120 Cause: The cipher could not be initialized. Action: Try restarting the novell-jcc service. 100708002 Could not initialize the cipher Cause: The cipher could not be initialized. Action: Try restarting the novell-jcc service. 120 Novell Access Manager 3.1 SP1 Event Codes...
Page 121 100708004 Could not find keystore_info.xml Cause: The install process did not complete successfully. Action :Restart the novell-jcc service. Otherwise, submit the file for jcc-0.log.0 resolution and reinstall the server component. Package com.novell.jcc.util...
Page 122 100709016 Could not open [jcc log file] Cause: Make sure the installation succeeded. Action: Restart the server. If the problem persists, submit the file for jcc-0.log.0 resolution. 122 Novell Access Manager 3.1 SP1 Event Codes...
Page 123 Remedy Event Code Description 100709017 [path]/settings.properties file does not Cause: An install-time error occurred. exist Action: Submit the jcc-0.log.0 file for resolution, reinstall the server component. 100709018 No remote management address is set. Cause: An IP address has not been specified for the administration console.
Page 124 124 Novell Access Manager 3.1 SP1 Event Codes...
Page 125: Policy Engine (008)
200804002 Action: Take any or all of the following actions: 200805002 1. Submit the log file to Novell Support to aid 200806002 in determining and fixing the source of the problem. 2. Back up to a previously working policy configuration until the problem has been fixed.
Page 126 200804003 Action: Take any or all of the following actions: 200805003 1. Submit the log file to Novell Support to aid 200806003 in determining and fixing the source of the problem. 2. Back up to a previously working policy configuration until the problem has been fixed.
Page 127 200805072 Action: Take any or all of the following actions: 200806072 1. Submit the log file to Novell Support to aid in determining and fixing the source of the problem. 2. Back up to a previously working policy configuration until the problem has been fixed.
Page 128 Description 300801071 Evaluation Canceled: Active policy Cause: May occur during system shutdown. evaluation canceled. 300802071 Action: If not caused by system shutdown, submit log to Novell Support for analysis and 300803071 resolution. 300804071 300805071 300806071 500801000 Success: Policy operation completed Cause: Policy Evaluation.
Page 129 Cause: Policy configuration document has been corrupted. Action: Take any or all of the following actions: 1. Submit the log file to Novell Support to aid in determining and fixing the source of the problem. 2. Back up to a previously working policy configuration until the problem has been fixed.
Page 130 130 Novell Access Manager 3.1 SP1 Event Codes...
Page 131: Soap Policy Enforcement Point (011)
SOAP Policy Enforcement Point (011) The SOAP Policy Enforcement Point (PEP) interface is used by the NetWare and Linux Access Gateways for policy evaluation. Component 011 Subgroup 01: General/Configuration Subgroup 02: Authorization PEP Subgroup 03: Identity Injection PEP Subgroup 04: Form Fill PEP Messages are logged to the catalina.out for trace and application level logging when Identity Server logging is enabled.
Page 132 Action: Check the policy definitions in the Administration Console to ensure the configuration store is working properly, then reapply the configuration to the device. 132 Novell Access Manager 3.1 SP1 Event Codes...
Page 133 Event Code Description Remedy 101101031 Configure Failure The policy requested is malformed or causes an exception during the configuration process. Cause: This is accompanied with a possible reason for the failure. Action: Check the policy configuration in the administrative console and reapply the configuration to the device.
Page 134 ESP failed, the requested policy data is unavailable. Cause: This is accompanied with a possible reason for failure. Action: As the administrator, check the health status of Identity Service Provider and take appropriate action. 134 Novell Access Manager 3.1 SP1 Event Codes...
Page 135 Event Code Description Remedy 501101054 Policy Evaluation - Cluster Data Query Attempt to retrieve user session data from Error ESP cluster member failed. Cause: The Embedded Service Provider which authenticated the user may not be accessible from the Embedded Service Provider evaluating the policy.
Page 136 136 Novell Access Manager 3.1 SP1 Event Codes...
Page 137: Backup And Restore (010)
Script to run to perform a restore. Other programs used by backup and restore: ICE: This is the Novell eDirectory utility to import and export LDIF file in and out of eDirectory. ldifReverse: This is a program that reverses the order of the records in the LDIF file exported from eDirectory.
Page 138 LDIF file specified backup file (with .ldif appended to the name) is not a valid backup file. Action: Make sure to specify a backup file that was created by the Access Manager Backup utility. 138 Novell Access Manager 3.1 SP1 Event Codes...
Page 139 Enter the following command: JAVA -classpath vcdnbkup.jar:cert tool.jar com.novell.nids.bkuputil. Util - userid cn=admin,o=novell -pwd secret - vcdnUser Backup and Restore (010) 139...
Page 140 Action: Ensure that user running backup sufficient rights. 201003041 Failed to retrieve certificate Cause: A PKI or eDirectory error. names from eDirectory. Action: This error will be accompanied by an error string. 140 Novell Access Manager 3.1 SP1 Event Codes...
Page 141 Remedy Event Code Description 201003042 Failed to retrieve certificate Cause: The certtool failed to retrieve the certificate xxxx from eDirectory. identified in the error. Problems have been seen trying to export certificate with pending CSRs. Action: This error will be accompanied by an error string.
Page 142 Action: Make sure /opt/volera/roma/conf/ vcdn.conf file is present and has the correct information. To fix enter the following command in the /opt/novell/ devman/bin directory: java -jar vcdnbkup.jar -userid cn=admin,o=novell -pwd admin_password - vcdnUser 201004002 Application Error.
Page 143: Novell Modular Authentication Class (012)
Novell Modular Authentication Class (012) The Novell Modular Authentication Service (NMAS) Class provides access to a number of advanced authentication mechanisms available from Novell, Inc. and Novell partners. Component 012 Subgroup 01: General/Configuration Log file: catalina.out for trace and application level logging as enabled by the log settings (click Identity Server >...
Page 144 101201006 NMAS Authentication Class Invalid NMAS Login state. Cause: Unknown Action: Check server status. 101201007 NMAS Authentication Class NMAS Login Error. Cause: See NMAS Error codes. Action: Indicated by NMAS error code. 144 Novell Access Manager 3.1 SP1 Event Codes...

Novell ACCESS MANAGER 3.1 SP1 - EVENT CODES Manual

Quick Links

Need help?

Questions and answers

Related Manuals for Novell ACCESS MANAGER 3.1 SP1 - EVENT CODES

Summary of Contents for Novell ACCESS MANAGER 3.1 SP1 - EVENT CODES

Table of Contents