Novell ACCESS MANAGER Setup Guide

Novell®

www.novell.com

Event Codes

Access Manager

novdocx (en) 13 May 2009

AUTHORIZED DOCUMENTATION

3.1 SP1

July 15, 2009

Novell Access Manager 3.1 SP1 Event Codes

Legal Notices

Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and
specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time,
without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims
any express or implied warranties of merchantability or fitness for any particular purpose. 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.

Any products or technical information provided under this Agreement may be subject to U.S. export controls and the
trade laws of other countries. You agree to comply with all export control regulations and to obtain any required
licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on
the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws.
You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the

Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on

exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export
approvals.

novdocx (en) 13 May 2009

Copyright © 2008-2009 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied,
stored on a retrieval system, or transmitted without the express written consent of the publisher.

Novell, Inc., has intellectual property rights relating to technology embodied in the product that is described in this
document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S.
patents listed on the Novell Legal Patents Web page (http://www.novell.com/company/legal/patents/) and one or
more additional patents or pending patent applications in the U.S. and in other countries.

Novell, Inc.
404 Wyman Street, Suite 500
Waltham, MA 02451
U.S.A.
www.novell.com

Online Documentation: To access the latest online documentation for this and other Novell products, see

the Novell Documentation Web page (http://www.novell.com/documentation).

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.

novdocx (en) 13 May 2009

novdocx (en) 13 May 2009

4 Novell Access Manager 3.1 SP1 Event Codes

Contents

About This Guide 7

1 Event Code Overview 9

2 Administration Console (009) 11

3 Identity Server (001) 51

4 Linux Access Gateway Appliance(045) 91

5 SSL VPN Server (005) 93

novdocx (en) 13 May 2009

6 J2EE Agents (006) 97

7 Server Communications (JCC) (007) 103

8 Policy Engine (008) 125

9 SOAP Policy Enforcement Point (011) 131

10 Backup and Restore (010) 137

11 Novell Modular Authentication Class (012) 143

Contents 5

novdocx (en) 13 May 2009

6 Novell Access Manager 3.1 SP1 Event Codes

About This Guide

This guide is intended to help you understand and resolve any issues with the event codes that are
displayed on error pages or logged in files.

 Chapter 1, “Event Code Overview,” on page 9

 Chapter 2, “Administration Console (009),” on page 11

 Chapter 3, “Identity Server (001),” on page 51

 Chapter 4, “Linux Access Gateway Appliance(045),” on page 91

 Chapter 5, “SSL VPN Server (005),” on page 93

 Chapter 6, “J2EE Agents (006),” on page 97

 Chapter 7, “Server Communications (JCC) (007),” on page 103

 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

novdocx (en) 13 May 2009

 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
evolving Internet protocols, such as:

 Extensible Markup Language (XML)

 Simple Object Access Protocol (SOAP)

 Security Assertion Markup Language (SAML)

 Public Key Infrastructure (PKI) digital signature concepts and Internet security

 Secure Socket Layer/Transport Layer Security (SSL/TSL)

 Hypertext Transfer Protocol (HTTP and HTTPS)

 Uniform Resource Identifiers (URIs)

 Domain Name System (DNS)

 Web Services Description Language (WSDL)

Feedback

We want to hear your comments and suggestions about this manual and the other documentation
included with this product. Please use the User Comments feature at the bottom of each page of the
online documentation, or go to www.novell.com/documentation/feedback.html and enter your
comments there.

Documentation Updates

For the most recent version of the Access Manager Event Codes Guide, visit the Novell Access

Manager Documentation Web site (http://www.novell.com/documentation/novellaccessmanager).

About This Guide 7

Additional Documentation

 Novell Access Manager 3.1 SP1 Administration Console Guide

 Novell Access Manager 3.1 SP1 Identity Server Guide

 Novell Access Manager 3.1 SP1 Access Gateway Guide

 Novell Access Manager 3.1 SP1 Policy Management Guide

 Novell Access Manager 3.1 SP1 Setup Guide

 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 (®, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party
trademark.

novdocx (en) 13 May 2009

When a single pathname can be written with a backslash for some platforms or a forward slash for
other platforms, the pathname is presented with a backslash. Users of platforms that require a
forward slash, such as Linux or UNIX, should use forward slashes as required by your software.

8 Novell Access Manager 3.1 SP1 Event Codes

1

Event Code Overview

Event codes for Access Manager consist of 4 fields that describe the type of code and the module
that produced it:

 Severity (1 digit)

 1 = severe - Describes problems that needs to be resolved in order for the system to run

correctly.

 2 = error - Describes that a failure occurred, but the system is operational.

 3 = warn - Describes a situation that may exist that the administrator should be aware of

and may need to address. The system is currently running properly

 4 = config - Describes configuration related information.

 5 = info - Describes events that occur.

 6 = debug - Describes execution points within the software.

 9 = internal - Describes an error that is for internal use only. This error code will not be

documented in any public documentation.

 Component issuing the error code (3 digits)

 Sub-grouping for further classification within a component (2 digits)

novdocx (en) 13 May 2009

1

 Event code (three digits)

0 000 00 000

Severity Component field Sub-grouping Event Code

The following sections divide the event codes by component, then describe them:

 Chapter 1, “Event Code Overview,” on page 9

 Chapter 2, “Administration Console (009),” on page 11

 Chapter 3, “Identity Server (001),” on page 51

 Chapter 4, “Linux Access Gateway Appliance(045),” on page 91

 Chapter 5, “SSL VPN Server (005),” on page 93

 Chapter 6, “J2EE Agents (006),” on page 97

 Chapter 7, “Server Communications (JCC) (007),” on page 103

 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

9

novdocx (en) 13 May 2009

10 Novell Access Manager 3.1 SP1 Event Codes

2

Administration Console (009)

Component 009

 Subgroup 01: Certificate Manager

 Subgroup 02: Application

 Subgroup 03: Platform

 Subgroup 04: Web UI

 Subgroup 05: Roma Application

 Subgroup 06: Policy

Event Code Description Remedy

Application

novdocx (en) 13 May 2009

2

100901001 Error getting web manager. Cause: The Administration Console was not

installed correctly or has become corrupt.

Action: Verify installation.

100901002 Error in initializing the dirCerts APIs. Cause: The Administration Console was not

installed correctly or has become corrupt.
Specifically, the PKI and/or certificate
management jars may be missing or have
mismatched versions.

Action: Verify that the
contained in the

tomcat4/webapps/roma/WEB-INF/lib

directory and that PKI has been installed.

Verify that the Java command line contains
the following:

-Djava.library.path=/opt/novell/
lib

Verify that

100901003 Error in init. Cause: The Administration Console was not

installed correctly or has become corrupt.

Action: Verify installation.

npki.jar

certmgr.jar

/var/opt/novell/

is in the classpath.

file is

100901004 Error in

CertHandler.getMultipartParamValue.

Cause: Servlet error when retrieving data
from a multipart form.

Action: Submit log to Novell Support for
analysis and resolution.

Administration Console (009)

11

Event Code Description Remedy

novdocx (en) 13 May 2009

100901008 Could not remove certificate with the given

alias from the keystore.

100901010 Error In

CertHandler.doGetSigningCertDN.

Cause: The keystore that contains the
certificate might not exist or might have
become corrupt.

Action: View the configuration store and find
the keystore object and check that the
certificate is no longer in the key list. If it is
there, manually remove it.

Also, find the keystore on the file system of
the device and remove the key manually,
using the Java keytool program for JKS
keystores.

Cause: Unable to retrieve the DN of the
signing cert.

Cause: The signing cert does not exist.

Cause: The signing keystore does not exist.

Action: View the Identity Server

Configuration's Signing keystore to verify that
it exists and contains a certificate. If the
signing keystore does not exist, there has
been an error during the import of an Identity
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.

12 Novell Access Manager 3.1 SP1 Event Codes

Event Code Description Remedy

novdocx (en) 13 May 2009

100901011 Error in creating or configuring one or

more of the Identity Server Configuration
cluster keystores.

Cause: Test certificates might have been
accidentally deleted from the file system.

Cause: Error communicating with the
Identity Server(s) while pushing down the
test certificates.

Action: Use the exception stack trace to
discover a more detailed description of the
error. Go to the Certificates tab and verify
that the test-connector, test-signing, test­encryption, test-provider, test-consumer
certificates have not been deleted.

Also verify they still exist on the file system.
Go to the Trusted Roots tab and verify that
the configCA trusted root has not been
deleted and that it exists in the configuration
store. These test certificates are pushed
down to each Identity Server during the
creation of an Identity Server configuration.

You can delete the Identity Server
configuration and create a new one and add
the Identity Servers back into the new
configuration.

100901012 keystore already exists. Cause: You are trying to create a keystore

that already exists on the device.

Action: Use the existing keystore.

100901013 Error in init (using reflection to call a

method has failed in init).

Cause: The java class is unable to locate
another java class through reflection.

Action: Submit log to Novell Support for
analysis and resolution.

700901014 Cannot add non-existent key to keystore. Cause: The certificate you are trying to add

to a keystore does not exist.

Action: Specify a valid key to be added to
the keystore.

700901015 Cannot add key to non-existent keystore. Cause: The keystore does not exist.

Action: Specify a valid keystore or create
the keystore.

700901016 Could not add key to keystore because the

alias was too long.

Cause: Some platforms and keystore
formats only support a limited number of
characters in the alias name.

Action: Use a shorter alias.

Administration Console (009) 13

Event Code Description Remedy

novdocx (en) 13 May 2009

700901017 Could not add key to keystore because the

maximum number of keys has been
reached.

700901020 Cannot remove non-existent key from

keystore.

700901021 Cannot remove key from non-existent

keystore.

100901023 CertHandler.doGetCertFromServer: Could

not connect to server IP and port.

100901024 CertHandler.doGetCertFromServer:

certificate was not obtained from server IP
and port.

Cause: Many keystores allow only one key
to be contained in it because the keystore
has a specific purpose in Access Manager.

Action: Remove unused keys from the
keystore and try again.

Cause: The key no longer exists in Access
Manager.

Action: View the configuration store and
find the keystore object and manually
remove the key from the key list.

Cause: The keystore does not exist.

Action: Specify a valid keystore.

Cause: The server IP or DNS name and port

combination is not reachable.

Action: Verify that the IP address or DNS
name exists and that the port is correct. You
can try connecting to it with a web browser or
other utility.

Cause: The server IP or DNS name and port
combination had no certificate to be
presented.

Action: Verify that the IP address or DNS
name exists and that the port is correct.
Verify that the server you are attempting to
import the certificate from has a certificate.
You can try connecting to it with a web
browser or other utility.

100901025 Error in handleException. Cause: The exception reported has no

details associated with it.

Action: Scroll up in the log to see if there is a
stack trace immediately above this error,
determine what steps you had taken to
create this error condition, and submit the log
and steps to Novell Support.

100901026 The node keystore does not exist. Cannot

add cluster keys to a non-existent
keystore.

Cause: The grouping of Identity Servers
(Identity Server Configuration) or Access
Gateways is trying to locate a keystore on
one of the 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.

14 Novell Access Manager 3.1 SP1 Event Codes

Event Code Description Remedy

novdocx (en) 13 May 2009

100901027 Error in

CertHandler.getNIDPDeviceKeystoreNam
e (The name of the device's keystore was
not found).

100901028 Error in CertHandler.isTomcatCert (Unable

to determine if the specified certificate is
the one being used by Tomcat).

100901030 Error in

CertHandler.getNodeKeystoreNames
(The cluster object was not found in the
configuration store, or the cluster server
list was empty).

Cause: The cluster keystore representation
object was not found.

Cause: The cluster keystore representation
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.

Cause: The certificate representation has
missing or invalid attributes.

Action: Delete this certificate and re-import
it.

Cause: The cluster object was not found in
the configuration store, the type of the cluster
could not be determined, or the cluster
server list was empty.

Action: No action needed unless your
devices are unable to communicate. If you
are having problems with communication,
delete and recreate the Identity Server
configuration or Access Gateway cluster that
is causing the problem.

100901031 Error in

CertHandler.getClusterDisplayName (The
cluster object was not found in the
configuration store).

100901032 The device does not exist but the

certificate is in a keystore assigned to that
device.

Action: Delete and recreate the Identity
Server configuration or Access Gateway
cluster that is causing the problem and then
re-add the members.

Cause: It's possible the device is in a
partially-imported state.

Action: Delete the keystore, if possible, and
re-import the device.

100901033 The device does not exist but the keystore

is assigned to that device.

Cause: It's possible the device is in a
partially-imported state.

Action: Delete the keystore, if possible, and
re-import the device.

100901034 Unable to retrieve the primary member of

Cause: The group is corrupt.

the group.

Action: Delete the group, re-create it, and
re-add the members.

100901035 Unable to remove the node keystore

setting off the Access Gateway group
device.

Cause: Could not locate the keystore object
in the configuration store.

Action: No action required.

700901036 Unable to set the Update Servers status. Cause: Communication error.

Action: Manually restart or update the
device.

Administration Console (009) 15

Event Code Description Remedy

700901037 Unable to remove all keys from keystore. Cause: The keystore doesn't exist.

Cause: There is a corrupt key in the

keystore.

Action: Manually remove each certificate
from the keystore.

novdocx (en) 13 May 2009

700901038 Unable to reinitialize keystore contents for

a particular device in a group or
configuration.

700901039 Unable to assess whether the keystore

contains a tomcat connector certificate.

Cause: One of the device keystores does
not exist.

Action: Re-create the keystore or delete and
recreate the group or configuration and then
re-add the devices to it.

Cause: There was an error either removing
all certificates from a keystore.

Action: Manually remove all certificates from
the keystore and then remove and re-add
that device to the group/configuration.

Cause: There was an error adding the test
certificates to a keystore.

Action: Verify that the test certificates exist
(see error 1.009.01.011 for more detail).
Manually add the test certificates to the
keystore. Or remove the device from the
group/configuration and re-add it.

Cause: The cluster keystore representation
does not exist or is corrupt.

Cause: Unable to locate the devices in the
group/configuration.

700901040 Error adding a key to keystore during the

renew certificate process.

100901041 Unable to extract the public key from a key

during the auto-import public certificate
process.

16 Novell Access Manager 3.1 SP1 Event Codes

Action: Delete and recreate the group/

configuration and re-add the devices to it.

Cause: The original certIficate information
could not be located.

Action: Manually create a new certificate
and place it into all the keystores which
previously held the certificate being renewed.

Cause: The source keystore does not exist.

Action: Select a valid keystore.

Cause: The specified source key does not

exist.

Action: Verify that the key you have
specified to export the public certificate from
exists.

Event Code Description Remedy

novdocx (en) 13 May 2009

100901042 Unable to set up the initial keys for the

cluster.

100901043 The source keystore does not exist.

Cannot push keys from a non-existent
keystore.

Application

100902001 Error - Exception thrown in eventOccurred

of
vcdn.application.sc.alert.AlertEventListene
r

100902002 Error - Exception thrown in eventOccurred

of
vcdn.application.sc.alert.AlertEventListene
r.

Cause: When trying to locate the cluster
keystores so that their contents can be
initialized, one or more of those keystore
representations could not be found.

Action: Delete and recreate the Identity
Server configuration or Access Gateway
cluster.

Cause: The source keystore does not exist.

Action: Usually the source keystore is a

cluster keystore representation. Try deleting
and recreating the Identity Server
configuration or Access Gateway cluster to
ensure those cluster keystore
representations get created.

Cause: Cannot post alert to internal
subsystem.

Action: Non-fatal error. No action required.

Cause: Cannot post alert to internal

subsystem.

Action: Submit the
resolution.

app_sc.0.log

file for

100902003 Error - Exception thrown in logAlert of

vcdn.application.sc.alert.AlertLogger.

100902004 Error - Exception thrown in the execute

method of
vcdn.application.sc.alert.CertUpdateWork.

Cause: Problem occurred update the
Identity Server Alert count.

Action: Non-fatal error. May be a symptom
of a more serious condition. Submit the

app_sc.0.log

Cause: Could not update or read the list of
trusted server certificates.

Action: Be sure the

novlwww/devman.cacerts

valid Java keystore, and is not corrupted. To
check its status, enter the following
command:

file for resolution.

/var/opt/novell/

file exists, is a

/opt/novell/java/bin/keytool -v ­list -keystore devman.cacerts

Otherwise, be sure the config store is
running and functioning properly.

Administration Console (009) 17

Event Code Description Remedy

novdocx (en) 13 May 2009

100902005 Error - (The specified device) has not been

imported. Failed to start device.

100902006 Error importing device (with the specified

ID).

100902007 Error - Import failed. Retrying. Cause: Unable to communicate with the

100902008 Error auto importing. Retry. Cause: Unable to communicate with the

Cause: The Identity Server was not properly
imported.

Action: Go to Access Gateway Server List
and click Repair Import. (The repair import.
functionality works for any server type.)
Otherwise, submit the
for resolution.

Cause: The Server was not properly
imported.

Action: Go to Access Gateway Server List
and click Repair Import. (The repair import.
functionality works for any server type.) If this
fails, reinstall the server component.

Server being imported.

Action: Be sure the firewall is allowing port
1443 traffic. Otherwise allow the system to
retry for several minutes. If the server does
not appear in the Server List, click Repair
Import to resolve the issue. Otherwise,
submit the

Server being imported.

app_sc.0.log

app_sc.0.log

file for resolution.

file

Action: Be sure the firewall is allowing port
1443 traffic. Otherwise allow the system to
retry for several minutes. If the server does
not appear in the Server List, click Repair
Import. to resolve the issue. Otherwise,
submit the
resolution.

100902009 Error - Could not create subcontext:

cn=(The specified Context)

100902010 Error - (The given ESP) does not exist! Cause: There was a error during the

100902011 Error - Exception reading (the given ESP) Cause: The file required during the import

Cause: Error creating Server object in config
store during import.

Action: Go to Access Gateway Server List
and click Repair Import. (The repair import
functionality works for any server type.)
Otherwise, submit the
for resolution.

Administration Console installation.

Action: Reinstall the Administration
Console.

process could not be read.

Action: Be sure the indicated file can be
read by the novlwww user.

app_sc.0.log

app_sc.0.log

file for

file

18 Novell Access Manager 3.1 SP1 Event Codes

Event Code Description Remedy

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
for resolution.

100902013 Error - Could not find (the specified DN) Cause: Error connecting to the config store

while importing 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
for resolution. You might need to restart the
Administration Console.

app_sc.0.log

app_sc.0.log

file

file

novdocx (en) 13 May 2009

100902014 Error - ESP Configuration was not found,

so auto-import failed.

100902015 Error - Exception thrown in importDevice

of
vcdn.application.sc.alert.RegisterComman
d.

100902016 Error - ImportThread null member vars. Cause: Internal error occurred during import.

100902017 Error - Could not connect to eDir for certs. Cause: Either the primary Administration

Cause: Could not find the configuration for
the imported 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
for resolution.

Cause: Error during import of server
component.

Action: Go to Access Gateway Server List
and click Repair Import. (The repair import
functionality works for any server type.)
Otherwise, submit the
for resolution.

Action: Go to Access Gateway Server List
and click Repair Import. (The repair import
functionality works for any server type.)
Otherwise, submit the
for resolution.

Console is down (if this is a secondary
console), or the config store is down.

app_sc.0.log

app_sc.0.log

app_sc.0.log

file

file

file

Action: Be sure the config store is operating
properly and that port 554 is not blocked by a
firewall.

Administration Console (009) 19

Event Code Description Remedy

100902018 Error during execution. Cause: Error executing an external program

during import process.

Action: Go to Access Gateway Server List
and click Repair Import. (The repair import
functionality works for any server type.)
Otherwise, submit the
for resolution.

app_sc.0.log

file

novdocx (en) 13 May 2009

100902019 Error - Could not get (the given number of)

bytes of payload data.

100902020 Error - VException thrown while executing

command in
vcdn.application.sc.alert.AlertCommandH
andler.

100902021 Error - VCDNException thrown in

performConfiguration of
vcdn.application.sc.config.AGApplyWork

100902022 Error - VCDNException thrown in

responseReceived method of
vcdn.application.sc.config.AGApplyWork

100902023 Error - VCDNException thrown in

performConfiguration method of
vcdn.application.sc.config.AGConfigWork

Cause: An error occurred while trying to
read data for a command.

Action: Ensure the server component is
operating properly. Otherwise, submit the

app_sc.0.log

Cause: Problem executing a command from
a server component.

Action: Ensure the server component is
operating properly. Otherwise, submit the

app_sc.0.log

Cause: Problem occurred while sending
configuration to Access Gateway server.

Action: Ensure the server component is
operating properly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred in processing the
response from an Access Gateway server.

Action: Ensure the server component is
operating properly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while sending
configuration to Access Gateway server.

Action: Ensure the server component is
operating properly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

file for resolution.

100902024 Error - VCDNException thrown in

responseReceived method of
vcdn.application.sc.config.AGConfigWork

100902025 Error - Exception thrown in

processAGResponse method of
vcdn.application.sc.config.AGConfigWork

20 Novell Access Manager 3.1 SP1 Event Codes

Cause: Error occurred in processing the

response from an Access Gateway server.

Action: Ensure the server component is
operating properly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred in processing the
response from an Access Gateway server.

Action: Ensure the server component is
operating properly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

Event Code Description Remedy

novdocx (en) 13 May 2009

100902026 Error - VCDNException thrown in

performConfiguration method of
vcdn.application.sc.config.AgentApplyWor
k

100902027 Error - VCDNException thrown in

responseReceived method of
vcdn.application.sc.config.AgentApplyWor
k

100902028 Error - VCDNException thrown in

performConfiguration method of
vcdn.application.sc.config.AgentConfigWo
rk

100902029 Error - VCDNException thrown in

responseReceived method of
vcdn.application.sc.config.AgentConfigWo
rk

100902030 Error - VCDNException thrown in

processAgentResponse method of
vcdn.application.sc.config.AgentConfigWo
rk

Cause: Error occurred while sending
configuration to J2EE Agent server.

Action: Ensure the server component is
operating properly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred in processing the
response from an J2EE Agent server.

Action: Ensure the server component is
operating properly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while sending
configuration to J2EE Agent server.

Action: Ensure the server component is
operating properly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred in processing the
response from an J2EE Agent server.

Action: Ensure the server component is
operating properly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred in processing the
response from an J2EE Agent server.

Action: Ensure the server component is
operating properly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

file for resolution.

100902031 Error - SchedulerException thrown in

configureDeviceNow method of
vcdn.application.sc.config.ConfigManager

100902032 Error - Exception thrown in the execute

method of
vcdn.application.sc.config.ConfigWork

100902033 Error setting LDAP attribute in

performPendingActions of
vcdn.application.sc.config.ConfigWork

100902034 Error invoking method in

performPendingActions of
vcdn.application.sc.config.ConfigWork

Cause: Error occurred while scheduling an
immediate apply of the current configuration.

Action: Submit the
resolution.

Cause: Error occurred while performing
pending actions.

Action: Submit the
resolution.

Cause: Pending actions could not be
completed because of a problem
communicating with the config store.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Problem occurred while invoking a
method during a pending action.

Action: Submit the
resolution.

app_sc.0.log

app_sc.0.log

file for resolution.

app_sc.0.log

file for

file for

file for

Administration Console (009) 21

Event Code Description Remedy

novdocx (en) 13 May 2009

100902035 Error executing pending action (name) in

performPendingActions of
vcdn.application.sc.config.ConfigWork

100902036 Error - Exception thrown in getConfigXML

of vcdn.application.sc.config.ConfigWork

100902037 Error - VException thrown in saveInDB

method of
vcdn.application.sc.config.ConfigWork

100902038 Error - VException thrown in

configFinished method of
vcdn.application.sc.config.DeviceConfigA
pplyWork

Cause: Problem occurred while displaying a
pending dialog message.

Action: This is a non-fatal error. If the
problem persists, submit the
file for resolution.

Cause: Error occurred while retrieving XML
data from the config store.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while saving the
applied configuration in the config store.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while sending the
Audit event for a changed configuration.

Action: Ensure the Audit server and the
config store are functioning properly.
Otherwise, submit the
for resolution.

file for resolution.

file for resolution.

app_sc.0.log

app_sc.0.log

file

100902039 Error - VException thrown in

configFinished method of
vcdn.application.sc.config.DeviceConfigW
ork

100902040 Error - Exception thrown in

processConfigDiff method of
vcdn.application.sc.config.DeviceGroupCo
nfigWork

100902041 Error - Exception thrown in

memberConfigFinished method of
vcdn.application.sc.config.DeviceGroupCo
nfigWork

100902042 Error - Exception thrown in

removePendingFromFailedList method of
vcdn.application.sc.config.DeviceGroupCo
nfigWork

Cause: Error occurred while sending the
Audit event for a changed configuration.

Action: Ensure the Audit server and the
config store are functioning properly.
Otherwise, submit the
for resolution.

Cause: Error occurred while parsing the
XML for a group configuration.

Action: Error occurred while sending the
Audit event for a changed configuration.

Action: Submit the
resolution.

Cause: Error occurred while processing a
group member configuration apply response.

Action: Ensure the server component is
functioning properly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while re-applying a
server configuration.

Action: Submit the
resolution.

app_sc.0.log

app_sc.0.log

file for resolution.

app_sc.0.log

file

file for

file for

22 Novell Access Manager 3.1 SP1 Event Codes

Event Code Description Remedy

novdocx (en) 13 May 2009

100902043 Error - SchedulerException thrown in

scheduleMultiDeviceWorks method of
vcdn.application.sc.config.DeviceGroupCo
nfigWork

100902044 Error - Exception thrown in the execute

method of
vcdn.application.sc.config.DeviceGroupCo
nfigWork

100902045 Error - VException thrown in performWork

method of
vcdn.application.sc.config.MultiDeviceCon
figWork

100902046 Error - Exception thrown in performWork

method of
vcdn.application.sc.config.MultiDeviceCon
figWork

100902047 Error - SchedulerException thrown in

getDeviceGroupConfigWork method of
vcdn.application.sc.config.MultiDeviceCon
figWork

Cause: Error occurred while scheduling a
group configuration.

Action: Submit the
resolution.

Cause: Error occurred while scheduling a
group configuration.

Action: Submit the
resolution.

Cause: Error occurred while applying
configuration to a group member.

Action: Ensure the server component is
functioning properly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while applying
configuration to a group member.

Action: Ensure the server component is
functioning properly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while trying to get the
scheduled configuration.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

app_sc.0.log

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for

file for

100902048 Error - VException thrown in

configFinished method of
vcdn.application.sc.config.MultiDeviceCon
figWork

100902049 Error - VCDNException thrown in the

execute method of
vcdn.application.sc.command.AGComma
ndWork

100902050 Error - Exception thrown in the

sendCommand method of
vcdn.application.sc.command.AGComma
ndWork

Cause: Error occurred while importing status
from a group member.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while sending a
command to an Access Gateway server.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while sending a
command to an Access Gateway server.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

Administration Console (009) 23

Event Code Description Remedy

novdocx (en) 13 May 2009

100902051 Error - Exception thrown in the

processAGResponse method of
vcdn.application.sc.command.AGComma
ndWork

100902052 Error - VCDNException thrown in the

execute method of
vcdn.application.sc.command.AgentCom
mandWork

100902053 Error - Exception thrown in the

sendCommand method of
vcdn.application.sc.command.AgentCom
mandWork

100902054 Error - Exception thrown in the

processAgentResponse method of
vcdn.application.sc.command.AgentCom
mandWork

Cause: Error occurred while processing a
command response from an Access
Gateway server.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while sending a
command to a J2EE Agent server.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while sending a
command to a J2EE Agent server.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while processing a
command response from a J2EE Agent
server.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

100902055 Error - IOException thrown in the

addCommand method of
vcdn.application.sc.command.CertComma
nd

100902056 Error - IOException thrown in the

generateCmd method of
vcdn.application.sc.command.CertComma
nd

100902057 Error - IOException thrown in the

setCertChainData method of
vcdn.application.sc.command.CertComma
nd

100902058 Error - VCDNException thrown in the

execute method of
vcdn.application.sc.command.IDPComma
ndWork

Cause: Error generating certificate
command.

Action: Submit the
resolution.

Cause: Error generating certificate
command.

Action: Submit the
resolution.

Cause: Error generating chained certificate
command.

Action: Submit the
resolution.

Cause: Error occurred while sending a
command to an Identity Server ESP server.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

app_sc.0.log

app_sc.0.log

app_sc.0.log

file for resolution.

file for

file for

file for

24 Novell Access Manager 3.1 SP1 Event Codes

Event Code Description Remedy

novdocx (en) 13 May 2009

100902059 Error - VCDNException thrown in the

sendCommand method of
vcdn.application.sc.command.IDPComma
ndWork

100902060 Error - NamingException thrown in the

updateNIDPCommandStatus method of
vcdn.application.sc.command.IDPComma
ndWork

010090261 Error - VException thrown in the

updateNIDPCommandStatus method of
vcdn.application.sc.command.IDPComma
ndWork

100902062 Error - Exception thrown in the

processIDPResponse method of
vcdn.application.sc.command.IDPComma
ndWork

Cause: Error occurred while sending a
command to an Identity Server or ESP
server.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while processing a
command response from an Identity Server
or ESP.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while processing a
command response from an Identity Server
or ESP.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while processing a
command response from an Identity Server
or ESP.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

100902063 Error - VCDNException thrown in the

execute method of
vcdn.application.sc.command.JCCComm
andWork

100902064 Error - Exception thrown in the

sendCommand method of
vcdn.application.sc.command.JCCComm
andWork

100902065 Error - Exception thrown in the

processResponse method of
vcdn.application.sc.command.JCCComm
andWork

100902066 Error - VCDNException thrown in the

execute method of
vcdn.application.sc.command.SSLVPNCo
mmandWork

Cause: Error occurred while executing a
server command.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while sending a
server command.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while processing a
response from a server command.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while sending an
SSLVPN server command.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

Administration Console (009) 25

Event Code Description Remedy

novdocx (en) 13 May 2009

100902067 Error - Exception thrown in the

sendCommand method of
vcdn.application.sc.command.SSLVPNCo
mmandWork

100902068 Error - Exception thrown in the

processSSLVPNResponse method of
vcdn.application.sc.command.SSLVPNCo
mmandWork

300902069 Exception changing factory LocalAddress. Cause: Error occurred while changing

100902070 Error - ConverterException thrown in the

getCurrentDeviceXML method of
vcdn.application.sc.core.AGDevice

100902071 Error - NamingException thrown in the

importDevice method of
vcdn.application.sc.core.AGDevice

Cause: Error occurred while sending an
SSLVPN server command.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while processing a
command response from an SSLVPN
Server.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

factory XML during configuration import.

Action: Submit the
resolution.

Cause: Error occurred during translation of
NetWare Access Gateway configuration.

Action: Submit the
resolution.

Cause: Config store could not be accessed
or an internal error occurred.

Action: Ensure the config store is
functioning properly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

app_sc.0.log

app_sc.0.log

file for resolution.

file for

file for

100902072 Error - VException thrown in the

importDevice method of
vcdn.application.sc.core.AGDevice

100902073 Error - Exception thrown in the

importDevice method of
vcdn.application.sc.core.AGDevice

100902074 Error - NamingException thrown in the

vcdn.application.sc.core.AuditManager
constructor.

100902075 Error - JDOMException thrown in the

processDocument method of
vcdn.application.sc.core.AuditManager

Cause: Config store could not be accessed
or an internal error occurred.

Action: Ensure the config store is
functioning properly. Otherwise, submit the

app_sc.0.log

Cause: Config store could not be accessed
or an internal error occurred.

Action: Ensure the config store is
functioning properly. Otherwise, submit the

app_sc.0.log

Cause: Config store could not be accessed
or an internal error occurred.

Action: Ensure the config store is
functioning properly. Otherwise, submit the

app_sc.0.log

Cause: Audit XML data could not be parsed.

Action: Submit the

resolution.

file for resolution.

file for resolution.

file for resolution.

app_sc.0.log

file for

26 Novell Access Manager 3.1 SP1 Event Codes

Event Code Description Remedy

novdocx (en) 13 May 2009

100902076 Error - Exception thrown in the

processDocument method of
vcdn.application.sc.core.AuditManager

100902077 Error - Exception thrown in the

setDefaultServer method of
vcdn.application.sc.core.AuditManager

100902078 Error - VException thrown in the

writeConfig method of
vcdn.application.sc.core.AuditManager

100902079 Error - NamingException thrown in the

writeConfig method of
vcdn.application.sc.core.AuditManager

100902080 Error - Exception thrown in the writeConfig

method of
vcdn.application.sc.core.AuditManager

Cause: Invalid data format.

Action: Attempt the operation again.

Otherwise, submit the
for resolution.

Cause: Config store could not be accessed
or an internal error occurred.

Action: Ensure the config store is
functioning properly. Otherwise, submit the

app_sc.0.log

Cause: Config store could not be accessed
or an internal error occurred.

Action: Ensure the config store is
functioning properly. Otherwise, submit the

app_sc.0.log

Cause: Config store could not be accessed
or an internal error occurred.

Action: Ensure the config store is
functioning properly. Otherwise, submit the

app_sc.0.log

Cause: Config store could not be accessed
or an internal error occurred.

Action: Ensure the config store is
functioning properly. Otherwise, submit the

app_sc.0.log

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

file

100902081 Error - SException thrown in the

getIDPConfigObject method of
vcdn.application.sc.core.AuditManager

100902082 Error - NamingException thrown in the

getIDPConfigObject method of
vcdn.application.sc.core.AuditManager

100902083 Error - Exception thrown in the

getIDPConfigObject method of
vcdn.application.sc.core.AuditManager

100902084 Error - NullPointerException thrown in the

logEvent method of
vcdn.application.sc.core.AuditManager

Cause: Config store could not be accessed
or an internal error occurred.

Action: Ensure the config store is
functioning properly. Otherwise, submit the

app_sc.0.log

Cause: Config store could not be accessed
or an internal error occurred.

Action: Ensure the config store is
functioning properly. Otherwise, submit the

app_sc.0.log

Cause: Config store could not be accessed
or an internal error occurred.

Action: Ensure the config store is
functioning properly. Otherwise, submit the

app_sc.0.log

Cause: Error logging Novell Audit event.

Action: Ensure the Novell Audit server is

functioning properly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

Administration Console (009) 27

Event Code Description Remedy

novdocx (en) 13 May 2009

100902085 Error - Exception thrown in the

creatElement method of
vcdn.application.sc.core.DeviceConfig

100902086 Error - Exception thrown in the

setLastModified method of
vcdn.application.sc.core.DeviceConfig

300902087 Warning - Exception thrown in the

getLastScheduledWorkID method of
vcdn.application.sc.core.DeviceGroupMan
ager

100902088 Error - Could not get version from device.

Make sure it is running properly.

100902089 Error - NamingException thrown in the

importDevice method of
vcdn.application.sc.core.DeviceManager

Cause: Internal XML error.

Action: Submit the

resolution.

Cause: Internal XML error.

Action: Submit the

resolution.

Cause: The last executed command status
ID could not be read.

Action: Non-fatal error.

Cause: Could not get version from device.

Action: Make sure the server component is

running properly, then click Repair Import to
resolve the issue. Otherwise, submit the

app_sc.0.log

Cause: Error importing device.

Action: Make sure the server component is

running properly, then click Repair Import to
resolve the issue. Otherwise, submit the

app_sc.0.log

app_sc.0.log

app_sc.0.log

file for resolution.

file for resolution.

file for

file for

100902090 Error - VException thrown in the

importDevice method of
vcdn.application.sc.core.DeviceManager

100902091 Error - InvocationTargetException thrown

in the importDevice method of
vcdn.application.sc.core.DeviceManager

100902092 Error - Exception thrown in the

importDevice method of
vcdn.application.sc.core.DeviceManager

100902093 Error - Could not find esp cfg SCC to

remove in cluster container.

100902094 Error deleting the trusted IDP entry for

ESP.

Cause: Error importing device.

Action: Make sure the server component is

running properly, then click Repair Import to
resolve the issue. Otherwise, submit the

app_sc.0.log

Cause: Error importing device.

Action: Make sure the server component is

running properly, then click Repair Import to
resolve the issue. Otherwise, submit the

app_sc.0.log

Cause: Error importing device.

Action: Make sure the server component is

running properly, then click Repair Import to
resolve the issue. Otherwise, submit the

app_sc.0.log

Cause: Error deleting improperly imported
server.

Action: Non-fatal error.

Cause: Error accessing config store.

Action: Ensure the config store is

functioning properly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

28 Novell Access Manager 3.1 SP1 Event Codes

Event Code Description Remedy

novdocx (en) 13 May 2009

100902095 Error - NamingException thrown in the

setHealthCheck method of
vcdn.application.sc.core.DeviceManager

100902096 Error - Could not find the DN specified. Cause: Error saving health status in config

100902097 Error - Exception thrown in the

deleteDevice method of
vcdn.application.sc.core.DeviceManager

100902098 Error - Exception thrown in the

setHealthCheck method of
vcdn.application.sc.core.DeviceManager

Cause: Error saving health status in config
store.

Action: Ensure the config store is
functioning properly. Otherwise, submit the

app_sc.0.log

store.

Action: Ensure the server component
imported correctly and the config store is
functioning properly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while deleting the
server objects.

Action: Ensure the config store is
functioning properly. Otherwise, submit the

app_sc.0.log

Cause: Error updating the version following
an upgrade of a server component.

Action: Allow the operation to try again.
Otherwise, submit the
for resolution.

file for resolution.

file for resolution.

file for resolution.

app_sc.0.log

file

300902099 Warning - Exception thrown in the

getLastScheduledWorkID method of
vcdn.application.sc.core.DeviceManager

300902100 Device is not imported. Cause: Server component is sending health

300902101 Identity configuration not found for device. Cause: Identity server configuration not

100902102 Error - Exception thrown in the

createCertEntry method of
vcdn.application.sc.core.KeyManager

Cause: The last executed command status
ID could not be read.

Action: Non-fatal error.

to Administration console that does not
recognize the server.

Action: Click Repair Import to resolve the
issue. Otherwise, submit the

app_sc.0.log

found in config store.

Action: Non-fatal error.

Cause: The config store is not reachable or

the user doesn't have rights to modify the
config store

Action: Verify the config store is up and that
the user has rights to create objects in the
following container:

file for resolution.

ou=KeyContainer,ou=Partition,ou=P
artitionsContainer,ou=VCDN_root,o
u=accessManagerContainer,o=novell

Administration Console (009) 29

Event Code Description Remedy

novdocx (en) 13 May 2009

100902103 Error - Exception thrown in the

deleteCertEntry method of
vcdn.application.sc.core.KeyManager

100902104 Error - Exception thrown in the

modifyCertEntryXml method of
vcdn.application.sc.core.KeyManager

100902105 Error - Exception thrown in the

createKeyStoreEntry method of
vcdn.application.sc.core.KeyManager

Cause: The config store is not reachable or
the user doesn't have rights to modify the
config store

Action: Verify the config store is up and that
the user has rights to delete objects in the
following container:

ou=KeyContainer,ou=Partition,ou=P
artitionsContainer,ou=VCDN_root,o
u=accessManagerContainer,o=novell

Cause: The config store is not reachable or
the user doesn't have rights to modify the
config store

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

Cause: The config store is not reachable or
the user doesn't have rights to modify the
config store

Action: Verify the config store is up and that
the user has rights to create objects in the
following container:

100902106 Error - Exception thrown in the

deleteKeyStoreEntry method of
vcdn.application.sc.core.KeyManager

100902107 Error - Exception thrown in the

modifyKeyStoreEntryXml method of
vcdn.application.sc.core.KeyManager

ou=KeyContainer,ou=Partition,ou=P
artitionsContainer,ou=VCDN_root,o
u=accessManagerContainer,o=novell

Cause: The config store is not reachable or
the user doesn't have rights to modify the
config store

Action: Verify the config store is up and that
the user has rights to delete objects in the
following container:

ou=KeyContainer,ou=Partition,ou=P
artitionsContainer,ou=VCDN_root,o
u=accessManagerContainer,o=novell

Cause: The config store is not reachable or
the user doesn't have rights to modify the
config store

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

30 Novell Access Manager 3.1 SP1 Event Codes

Event Code Description Remedy

novdocx (en) 13 May 2009

100902108 Error - Exception thrown in the

createElement method of
vcdn.application.sc.core.PolicyConfig

100902109 Error - Exception thrown in the

setLastModified method of
vcdn.application.sc.core.PolicyConfig

100902110 Error - NamingException thrown in the

importDevice method of
vcdn.application.sc.core.SSLVPNDevice

100902111 Error - VException thrown in the

importDevice method of
vcdn.application.sc.core.SSLVPNDevice

100902112 Error - Exception thrown in the

importDevice method of
vcdn.application.sc.core.SSLVPNDevice

Cause: Error creating an element in the
specified XML document.

Action: Submit the
resolution.

Cause: Error setting an attribute value on
modified elements.

Action: Submit the
resolution.

Cause: Error importing device.

Action: Click Repair Import to resolve the

issue. Otherwise, submit the

app_sc.0.log

Cause: Error importing device.

Action: Click Repair Import to resolve the

issue. Otherwise, submit the

app_sc.0.log

Cause: Error importing device.

Action: Click Repair Import to resolve the

issue. Otherwise, submit the

app_sc.0.log

app_sc.0.log

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for

file for

100902113 Error - Exception thrown in the sendData

method of
vcdn.application.sc.core.work.DeleteDevic
eWork

100902114 Error - Exception thrown in the execute

method of
vcdn.application.sc.core.work.ReimportDe
viceWork

100902115 Error - Exception thrown in the getHealth

method of
vcdn.application.sc.health.HealthCheck

100902116 Error - Inner Exception thrown in the

execute method of
vcdn.application.sc.health.HealthCheck

Cause: Error communicating with
component.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while executing a
server command.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while executing a
server command.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while executing a
server command.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

Administration Console (009) 31

Event Code Description Remedy

novdocx (en) 13 May 2009

100902117 Error - Outer Exception thrown in the

execute method of
vcdn.application.sc.health.HealthCheck

100902118 Error - VException thrown in the

eventOccurred method of
vcdn.application.sc.health.HealthEventList
ener

100902119 Error getting Health Module or Service Cause: Error occurred while executing a

100902120 Error - Exception thrown in the execute

method of
vcdn.application.sc.health.HealthUpdateW
ork

Platform

Cause: Error occurred while executing a

server command.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while receiving/
logging a health event.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

server command.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while executing a
server command.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

100903001 Error - Unable to find a trusted client

certificate.

100903002 Error building delayed response. Cause: Error occurred while processing a

100903003 Error setting return code in

HttpServletResponse.

100903004 Error - DelayedResponseListener thread

failed to start.

Cause: There was a problem during the
import of the device.

Action: Consult the documentation to re­import the device into the Administration
Console.

request.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while processing a
request.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while processing a
delayed response.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

32 Novell Access Manager 3.1 SP1 Event Codes

Event Code Description Remedy

novdocx (en) 13 May 2009

100903005 Error in the ResponseHandler thread of

the DelayedResponseListener.

100903006 Error creating XML Element in

ResponseBuilder.

100903007 Error waiting on mutex in

RequestDispatcher.

100903008 Error notifying mutex in

RequestDispatcher.

100903009 Error receiving in SendInternal of

VConnection.

Cause: Error occurred while processing a
response.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while editing XML.

Action: Ensure the server component is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while getting
responses.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while receiving a
response.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while receiving an
internal response.

file for resolution.

file for resolution.

file for resolution.

file for resolution.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

100903010 Error getting response code in

VConnection.

Cause: Error occurred while getting the
code.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

100903011 Error in stopScheduledResponses of

VConnection.

Cause: Error occurred while attempting to
stop scheduled responses.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

100903012 Error in ConsumeData of VConnection. Cause: Error occurred while reading data.

Action: Ensure the server component is

functioning correctly. Otherwise, submit the

app_sc.0.log

100903013 Error in sendData of VConnection. Cause: Error occurred while sending data.

Action: Ensure the server component is

functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

file for resolution.

Administration Console (009) 33

Event Code Description Remedy

100903014 Error in getHeaders of VConnection. Cause: Error occurred while getting

headers.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

100903015 Error in receive of VConnection. Cause: Error occurred while receiving a

response.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Web UI

100904001 Error reading manager data in UIManager. Cause: Error occurred while reading data.

Action: Ensure the server component is

functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

novdocx (en) 13 May 2009

100904002 Error during auto authentication in

WebApplicaitonFilter.

100904003 Error - Exception thrown in doFilter of

WebApplicationFilter.

100904004 Error - Exception thrown in logout of

WebApplicationFilter.

100904005 Error - VException thrown in getUserInfo

of WebManager.

100904006 Error - Exception thrown in getDeviceInfo

of WebManager.

Cause: Error occurred while authenticating.

Action: Ensure the server component is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error getting panel data.

Action: Ensure the server component is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while logging out.

Action: Ensure the server component is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while getting user
information.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while getting device
information.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

file for resolution.

100904007 Error - Exception thrown in getPolicyInfo of

WebManager.

34 Novell Access Manager 3.1 SP1 Event Codes

Cause: Error occurred while getting policy

information.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

Event Code Description Remedy

novdocx (en) 13 May 2009

100904008 Error - Exception thrown in

getTypeSpecificationInfo of WebManager.

100904009 Error - Exception thrown in

getDeviceConfig of WebManager.

100904010 Error - Exception thrown in

getPolicyConfig of WebManager.

100904011 Error - Exception thrown in

getTypeSpecificationConfig of
WebManager.

100904012 Error - Exception thrown in

parameterMapToString of WebManager.

Cause: Error occurred while getting policy
type specification information.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while getting device
configuration.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while getting device
configuration.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while getting policy
type specification configuration.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while getting
parameter information.

file for resolution.

file for resolution.

file for resolution.

file for resolution.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

100904013 Error while logging out user {0}. Cause: Error occurred while logging out

NDS user object.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

100904014 Error - Exception thrown in

getSelectionCriteria of WebPanel.

Cause: Error occurred while getting
selection criteria.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

100904015 Error - Exception thrown in

getPanelVersion of WebPanel.

Cause: Error occurred while getting panel
version.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

Administration Console (009) 35

Event Code Description Remedy

100904016 Error - Group Config failed. Cause: Error occurred while applying group

configuration.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

100904017 Error - Schedule Group Config failed. Cause: Error occurred while scheduling

group configuration.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

novdocx (en) 13 May 2009

100904018 Error - Update XML and Device Config

failed.

100904019 Error - Unlock Config failed. Cause: Error occurred while unlocking the

100904020 Error - Exception thrown in

do_cancelPendingConfig of
ConfigWorkDispatcher.

100904021 Error - Exception thrown in

do_cancelPendingConfig of
ConfigWorkDispatcher.

100904022 Error - Exception thrown in

do_reapplyPendingConfig of
ConfigWorkDispatcher.

Cause: Error occurred while updating
configuration.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

configuration.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while canceling a
pending configuration.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while canceling a
pending configuration.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while reapplying a
pending configuration.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

file for resolution.

100904023 Error - Exception thrown in

do_deviceConfig of
ConfigWorkDispatcher.

36 Novell Access Manager 3.1 SP1 Event Codes

Cause: Error occurred while applying

configuration.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

Event Code Description Remedy

novdocx (en) 13 May 2009

100904024 Error - Exception thrown in

do_scheduleDeviceConfig of
ConfigWorkDispatcher.

200904025 Error - XML VALIDATION FAILED.

PLEASE CHECK APP_SC LOG.

100904026 Error applying settings in

ConfigXmlUpdateDispatcher.

100904027 Error - Exception thrown in do_save of

ConfigXmlUpdateDispatcher.

100904028 Error - Exception thrown in do_cancel of

ConfigXmlUpdateDispatcher.

Cause: Error occurred while scheduling
configuration.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: XML created by GUI does not match
the XML schema and fails validation.

Action: Cancel the changes that were made
and try again. In any case, submit the

app_sc.0.log

Cause: Error occurred while applying
configuration.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while saving
configuration.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while canceling
configuration changes.

file for resolution.

file for resolution.

file for resolution.

file for resolution.

100904029 Error - Exception thrown in

do_refreshConfig of
ConfigXmlUpdateDispatcher.

100904030 Error - Exception thrown in

setLastModParams of
ConfigXmlUpdateDispatcher.

100904031 Error - IOException thrown in

getXPathMap of
ConfigXmlUpdateDispatcher.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while refreshing
configuration manager panel.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while setting an XML
attribute.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while xpath mapping
on the current panel.

Action: Ensure the server component is
functioning correctly. Cancel changes on the
current panel, return, and try again.
Otherwise, submit the
for resolution.

file for resolution.

file for resolution.

file for resolution.

app_sc.0.log

file

Administration Console (009) 37

Event Code Description Remedy

100904032 Error decoding: {0}. Cause: Error occurred while xpath mapping

on the current panel.

Action: Ensure the server component is
functioning correctly. Cancel changes on the
current panel, return, and try again.
Otherwise, submit the
for resolution.

app_sc.0.log

file

novdocx (en) 13 May 2009

100904033 Error - Exception thrown in

processRequest of ExceptionDispatcher.

100904034 Error - Exception thrown in the service

method of ServletDispatcher.

100904035 Error - Exception thrown in

ServletDispatcher.

100904036 Error - Exception thrown in

processRequest of
DeviceCommandHandler.

100904037 Error - VException thrown in

setNIDPCommandState of
DeviceCommandHandler.

Cause: Error occurred while processing
request.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while processing
request.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while inserting
dispatchers.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while processing
request.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while accessing data
store.

Action: Ensure the data store is functioning
correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

file for resolution.

100904038 Error - NamingException thrown in

setNIDPCommandState of
DeviceCommandHandler.

100904039 Error - Could not find signing keystore for

{0}.

38 Novell Access Manager 3.1 SP1 Event Codes

Cause: Error occurred while accessing data

store.

Action: Ensure the data store is functioning
correctly. Otherwise, submit the

app_sc.0.log

Cause: An error occurred during the import
of the device.

Action: Consult the documentation and re­import the device into the Administration
Console.

file for resolution.

Event Code Description Remedy

novdocx (en) 13 May 2009

100904040 Error - Could not find encryption keystore

for {0}.

100904041 Error - Could not find connector keystore

for {0}.

100904042 Error - Could not find trust keystore for {0}. Cause: An error occurred during the import

100904043 Error - Could not find OCSP trust keystore

for {0}.

100904044 Error - No keys were assigned to keystore:

{0}.

Cause: An error occurred during the import
of the device.

Action: Consult the documentation and re­import the device into the Administration
Console.

Cause: An error occurred during the import
of the device.

Action: Consult the documentation and re­import the device into the Administration
Console.

of the device.

Action: Consult the documentation and re­import the device into the Administration
Console.

Cause: An error occurred during the import
of the device.

Action: Consult the documentation and re­import the device into the Administration
Console.

Cause: The keystore does not have any
certificates in it. This may or may not be a
bad condition. For instance, the OCSP trust
store can be empty and that should not
cause a problem. The signing, encryption,
connector, provider, and consumer keystores
should have one certificate in them. If it is
empty, either the device import failed or the
user manually removed the certificate from
the keystore.

100904045 Error - Exception thrown in

processRequest of
UpgradeDeviceGroupHandler.

Action: Check the keystore using the UI. If
the keystore shows that it has a certificate,
then the device import probably failed.
Consult the documentation and re-import the
device and also try deleting and re-creating
the NIDP configuration. Also, try replacing
the certificate in the keystore through the UI.

Cause: Error occurred while processing
request.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

Administration Console (009) 39

Event Code Description Remedy

novdocx (en) 13 May 2009

100904046 Error - Exception thrown in

processRequest of
UpgradeDeviceHandler.

100904047 Error - Exception thrown in

getUpgradeInfo of
UpgradeDeviceHandler.

Application Handlers

100905001 Error during repair import. Cause: Error occurred while attempting to

100905002 Error - Failed to remove server. Cause: Error occurred while attempting to

Cause: Error occurred while processing
request.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while getting update
information.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

repair import.

Action: Delete the server from the list and
reinstall. Otherwise, submit the

app_sc.0.log

remove server.

Action: Submit the
resolution.

file for resolution.

file for resolution.

file for resolution.

app_sc.0.log

file for

100905003 Error setting device groups. Cause: Error occurred while attempting to

mark a server as a member of a group.

Action: Delete the server from the group
and retry or delete the group and recreate.
Otherwise, submit the
for resolution.

100905004 Error setting device admin. Cause: Error occurred while attempting to

give an Administrator access to a server.

Action: Submit the
resolution.

100905005 Error - Exception thrown while importing

appliance.

Cause: Error occurred while importing a
server.

Action: Delete the server from the list and
reinstall. Otherwise, submit the

app_sc.0.log

100905006 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
for resolution.

app_sc.0.log

app_sc.0.log

file for resolution.

app_sc.0.log

file

file for

file

40 Novell Access Manager 3.1 SP1 Event Codes

Event Code Description Remedy

100905007 Error canceling appliance creation. Cause: Internal error.

novdocx (en) 13 May 2009

Action: Submit the
resolution.

100905008 Error creating new CDN. Cause: Internal error.

Action: Submit the
resolution.

100905009 Error removing CDN. Cause: Internal error.

Action: Submit the
resolution.

100905010 Error creating new Admin. Cause: Internal error.

Action: Submit the
resolution.

100905011 Error while changing the cached device

port.

100905012 Error while changing the cached device

password.

Cause: Internal error while processing
request.

Action: Ensure the Management IP Address
is correct or edit as needed. Otherwise,
submit the

Cause: Internal error while processing
request.

Action: Ensure the Management Password
is correct or edit as needed. Otherwise,
submit the

app_sc.0.log

app_sc.0.log

app_sc.0.log

app_sc.0.log

app_sc.0.log

app_sc.0.log

file for

file for

file for

file for

file for resolution.

file for resolution.

100905013 Error - Exception thrown while processing

request in EditApplianceHandler

100905014 Error - Exception thrown while modifying

device handler in EditDeviceHandler.

100905015 Error - Exception thrown while changing

password in EditDeviceHandler.

200905016 Error - Exception thrown while editing

CDN in EditPublisherHandler.

Cause: Internal error while processing
request.

Action: Ensure all values on the Server
Details Edit page are correct and edit as
needed. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while processing a
request.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while processing a
request.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

Administration Console (009) 41

Event Code Description Remedy

novdocx (en) 13 May 2009

200905017 Error - Exception thrown while updating

CDN in EditPublisherHandler.

200905018 Error - Failed to update the device groups

for this user.

200905019 Error - Failed to update the devices for this

user.

200905020 Error - Failed to update the cdns for this

user.

200905021 Error - Failed to update user data. Cause: Internal error.

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

file for resolution.

100905022 Error processing client certs in

GenericPipeHandler.

200905023 Error accessing XML data item in generic

pipe: {0}

200905024 Error parsing XML data item in generic

pipe: {0}

200905025 Error processing XML data item in generic

pipe: {0}

100905026 Error - Exception thrown in

processRequest of GenericPipeHandler:
{0}

Cause: Internal error while processing
request.

Action: Ensure the server component is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

file for resolution.

42 Novell Access Manager 3.1 SP1 Event Codes

Event Code Description Remedy

novdocx (en) 13 May 2009

100905027 Error occurred while creating group {0} :

{1}.

100905028 Error getting device manager in

doGroupRemove of GroupCreateHandler.

100905029 Error occurred while removing group {0} :

{1}.

100905030 Error occurred while getting device

manager in doGroupAlertStatus of
GroupCreateHandler.

100905031 Error occurred while setting alert status for

group {0} : {1}.

Cause: Internal error.

Action: Ensure the config store is

functioning correctly or delete the group and
recreate it. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly or delete the group
again. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly or delete the group
again. Otherwise, submit the

app_sc.0.log

Cause: Unable to get alert status for the
group.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Unable to set alert status for the
group.

file for resolution.

file for resolution.

file for resolution.

file for resolution.

100905032 Error occurred while updating group {0} :

{1}.

100905033 Error occurred while removing devices

from group {0} : {1}.

100905034 Error - Naming Exception thrown in

removeDeviceFromCluster of
GroupCreateHandler.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Unable to make updates to the
group.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Unable to remove servers from the
group.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Unable to remove servers from the
cluster.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

Administration Console (009) 43

Event Code Description Remedy

novdocx (en) 13 May 2009

100905035 Error - Exception thrown in

removeDeviceFromCluster of
GroupCreateHandler.

100905036 Error - Exception thrown in

removeDeviceFromCluster of
GroupCreateHandler.

100905037 Error occurred while adding devices to

group {0} : {1}.

100905038 Error - Naming Exception thrown in

addDeviceToCluster of
GroupCreateHandler.

100905039 Error - Exception thrown in

addDeviceToCluster of
GroupCreateHandler.

Cause: Error occurred while removing
servers from the cluster.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while removing
servers from the cluster.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while adding servers
to the group.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while adding servers
to the cluster.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while adding servers
to the cluster.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

file for resolution.

100905040 Error - Exception thrown in

addDeviceToCluster of
GroupCreateHandler.

100905041 Error occurred while adding devices to

group {0} : {1}.

100905042 Error - VCDNException thrown in

processRequest of SyncHandler.

100905043 Error - Exception thrown in

processRequest of SyncHandler.

Cause: Error occurred while adding servers
to the cluster.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while adding servers
to the cluster.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

44 Novell Access Manager 3.1 SP1 Event Codes

Event Code Description Remedy

novdocx (en) 13 May 2009

100905044 Error - Exception thrown in

modifySystemSync of SyncHandler.

100905045 Error - WSException thrown in

isAssignedUser of GroupCreateBean.

100905046 Error - WSException thrown in

isAssignedDevice of GroupCreateBean.

100905047 Error - WSException thrown in

getApplianceByUrl of GroupCreateBean.

100905048 Error - WSException thrown in

generateMembershipList of
GroupCreateBean.

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

file for resolution.

100905049 Error - WSException thrown in

getAppGroupByName of
GroupCreateBean.

100905050 Error - WSException thrown in

getDescForThisGroup of
GroupCreateBean.

100905051 Error - Exception thrown in

getDescForThisGroup of
GroupCreateBean.

100905052 Error - WSException thrown in

getLastModifiedDate of
GroupCreateBean.

100905053 Error - Get appliance groups failed in

GroupCreateBean.

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly or delete group and
recreate it. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

file for resolution.

Administration Console (009) 45

Event Code Description Remedy

novdocx (en) 13 May 2009

100905054 Error - WSException thrown in

hasAMembershipIn of GroupCreateBean.

100905055 Error - Get appliances failed in

GroupCreateBean.

100905056 Error - Get admins failed in

GroupCreateBean.

100905057 Error - WSException thrown in

getPerDeviceProperties of
GroupCreateBean.

100905058 Error - WSException thrown in

getPerUserProperties of
GroupCreateBean.

Cause: Internal error.

Action: Ensure the config store is

functioning correctly or delete group and
recreate it. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly or delete group and
recreate it. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

file for resolution.

100905059 Error - WSException thrown in

getDeviceGroupProperties of
GroupCreateBean.

100905060 Error - NamingException thrown in

setDeviceClusterConfig of
GroupCreateBean.

100905061 Error - Exception thrown in

setDeviceClusterConfig of
GroupCreateBean.

100905062 Error - VException thrown in

clusterServers of GroupCreateBean.

100905063 Error - Exception thrown in clusterServers

of GroupCreateBean.

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

file for resolution.

46 Novell Access Manager 3.1 SP1 Event Codes

Event Code Description Remedy

novdocx (en) 13 May 2009

100905064 Error - VException thrown in getAdminList

of GroupCreateBean.

100905065 Error - Exception thrown in callRestartESP

of SPConfigHandler.

100905066 Error restarting {0}. Cause: Error occurred while restarting

100905067 Error - Could not lookup {0}. Cause: Error occurred while looking up DN

Cause: Internal error.

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while restarting
Embedded Service Provider.

Action: Ensure the server component and
ESP are functioning correctly or restart ESP
again. Otherwise, submit the

app_sc.0.log

Embedded Service Provider.

Action: Ensure the server component and
ESP are functioning correctly or restart ESP
again. Otherwise, submit the

app_sc.0.log

in config store.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

100905068 {0}. Cause: Error occurred while accessing

config store.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

100905069 Error - Exception thrown in

createTrustedIDP of SPConfigHandler.

Cause: Error occurred while accessing
config store.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

100905070 Error getting the esp trusted IDP. Cause: Error occurred while accessing

config store.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

100905071 espTrustAccessDN not set. Cause: Error occurred while accessing

config store.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

file for resolution.

file for resolution.

file for resolution.

Administration Console (009) 47

Event Code Description Remedy

100905072 Error deleting trusted IDP config. Cause: Error occurred while accessing

config store.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

file for resolution.

novdocx (en) 13 May 2009

100905073 Error - VCDNException thrown in

processRequest of ScheduleHandler.

100905074 Error - Exception thrown in

processRequest of ScheduleHandler.

100905075 Error - Exception thrown in setEnable of

ScheduleHandler.

100905076 Error - Exception thrown while removing

scheduled work in ScheduleHandler.

100905077 Error - Exception thrown while releasing

config lock in ScheduleHandler.

Cause: Error occurred while processing
request.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while processing
request.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while processing
request.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while processing
request.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while unlocking
configuration.

file for resolution.

file for resolution.

file for resolution.

file for resolution.

100905078 Error - Exception thrown in modify method

of ScheduleHandler.

100905079 Error - Exception thrown in executeNow

method of ScheduleHandler.

48 Novell Access Manager 3.1 SP1 Event Codes

Action: Ensure the config store is

functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while modifying
scheduled work.

Action: Ensure the config store is
functioning correctly. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while scheduling
work.

Action: Ensure the config store and server
component are functioning correctly.
Otherwise, submit the
for resolution.

file for resolution.

file for resolution.

app_sc.0.log

file

Event Code Description Remedy

novdocx (en) 13 May 2009

100905080 Error - ParamNotFoundException thrown

in createSchedule method of
ScheduleHandler.

100905081 Error - Can not forward the request to

return page. Nothing can be done.

100905082 Error - Exception thrown in create method

of ScheduleHandler.

100905083 Config store Error Cause: The connection to the config store is

Cause: Error occurred while scheduling
work.

Action: Ensure the config store and server
component are functioning correctly.
Otherwise, submit the
for resolution.

Cause: Internal error.

Action: Ensure server component is

functioning correctly and attempt to navigate
to desired panels. Otherwise, submit the

app_sc.0.log

Cause: Error occurred while scheduling
work.

Action: Ensure the config store and server
component are functioning correctly.
Otherwise, submit the
for resolution.

experiencing problems.

Action: To diagnose time synchronization
issues with multiple Administration Consoles,
run the following command on the primary
server command-line:

app_sc.0.log

file for resolution.

app_sc.0.log

file

file

Policy

100906000 Cannot set update status for NULL policy

extension.

100906001 Cannot retrieve policy collection info

object for the extension.

/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.

Cause: The composite ID of the extension
specified cannot be resolved to an extension
ID.

Action: On the device that is not receiving
an Update status, make a configuration
change to force the Update link to become
active.

Cause: The extension ID specified cannot
be found in the configuration store.

Action: If you see a problem with your
extensions, note this error in the log and call
support.

Administration Console (009) 49

Event Code Description Remedy

novdocx (en) 13 May 2009

100906002 Cannot retrieve device info object for a

device

Cause: When trying to set the Update status
on devices which use an extension, the
device info was unable to be located in the
configuration store.

Action: On the device that is not receiving
an Update status, make a configuration
change to force the Update link to become
active.

500906000 Attempting to update policy status on

Cause: Informational message.

devices because the policy extension
changed.

Action: No action necessary.

500906001 Setting update policy status for device. Cause: Informational message.

Action: No action necessary.

50 Novell Access Manager 3.1 SP1 Event Codes

3

Identity Server (001)

3

Component 001

 Subgroup 01: End user events

 Subgroup 02: Web Service Framework (WSF)

 Subgroup 03: Web Service Consumer (WSC)

 Subgroup 04: User Authentication

Event Code Message Remedy

100100001 Type: SEVERE:NIDP:INITIALIZE:001

100100002 Type: SEVERE:NIDP:INITIALIZE:002

novdocx (en) 13 May 2009

100101001 No binding available or set for

profile.

100101043 IDP is unable to load ESP

metadata.

Type: SEVERE:NIDP:USERMSG:001

Cause: An action using Liberty or SAML protocols
could not be completed because the server and trusted
provider are not compatibly configured to interact to
complete the action.

Action: Set the desired protocol profiles in the
administration tool to match those supported at the
trusted provider.

Type: SEVERE:NIDP:USERMSG:043

Cause: The IDP cannot connect to the metadata URL
for the ESP. The IDP may not be able to resolve the
domain name for the ESP or if HTTPS is being used,
the IDP may not trust the SSL certificate for the ESP.
The ESP might also not be running.

Action: Make sure that certificates for ESP are
imported and trusted into IDP configuration. Check the
metadata URL for the ESP and make sure the metadata
can be retrieved from a browser: http://<DNS_name>/
nesp/idff/metadata

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)

51

Event Code Message Remedy

novdocx (en) 13 May 2009

100101044 ESP is unable to load IDP

metadata

100101045 An error happened while the

request was being sent to the
correct cluster member for
processing.

100102001 Incomplete web service

configuration.

Type: SEVERE:NIDP:USERMSG:044

Cause: The ESP cannot connect to the metadata URL
for the IDP. The ESP may not be able to resolve the
domain name for the IDP or if HTTPS is being used, the
ESP may not trust the SSL certificate for the IDP. The
IDP may also not be running

Action: Make sure the IDP is running and that all
certificates are imported and trusted. Check the
metadata URL for the IDP and make sure the metadata
can be retrieved from a browser: http://<DNS_name>/
nidp/idff/metadata A common cause is the base URL on
the 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.

Type: SEVERE:NIDP:USERMSG:045

Cause: The target cluster member may be unavailable.

Action: Ensure that all cluster devices are operating

correctly.

Type: SEVERE:NIDP:WSF:001

Cause: The web service instance type (attribute
nidsWsfServiceInstanceType on the nidsWsfService
object) is not available in the service definition.

Action: Delete the associated web service definition
and recreate it.

100102002 Invalid web service

configuration.

100102003 Unable to instantiate the web

service provider authority
class. This class will be
com.novell.nidp.liberty.wsf.co
nfig.authority.ldap.WSFConfig
AuthorityLdap.

100102004 Unable to load web services. Type: SEVERE:NIDP:WSF:004

Type: SEVERE:NIDP:WSF:002

Cause: The web service configuration XML (attribute
nidsConfigXML on the nidsWsfService object) has
invalid XML.

Action: Delete the associated web service definition
and recreate it.

Type: SEVERE:NIDP:WSF:003

Cause: Some Java error (probably a classpath issue) is
causing the main authority class to not instantiate.

Action: Review how the Access Manager product was
installed and attempt to determine if Java class files are
being accessed from an unexpected source.

Cause: This error catches all failures encountered
while trying to load all web services. The reason will be
different depending on where the error happened.

Action: Try to delete and recreate the web services.

52 Novell Access Manager 3.1 SP1 Event Codes

Event Code Message Remedy

novdocx (en) 13 May 2009

100102005 Unable to access Novell

Secret Store.

100102006 Unable to create user profile

object.

100102007 Unable to instantiate

password callback class.

Type: SEVERE:NIDP:WSF:005

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.

Type: SEVERE:NIDP:WSF:006

Cause: A Liberty User Profile Object did not exist for
the current user, so an attempt was made to create one.
That attempt failed!

Action: Determine if the named container exists and
that the administrator user has rights to create objects
there.

Type: SEVERE:NIDP:WSF:007

Cause: Could not find the password callback class in
the classpath.

Action: Make sure the password callback class to
check UsernameToken that decrypts an encrypted
message in WSS is in the classpath.

100102008 Unable to convert XML into

Document.

100102009 Unable to process

WSSecurity (WSS) message.

100102010 No WSS header found Type: SEVERE:NIDP:WSF:010

Type: SEVERE:NIDP:WSF:008

Cause: This error occurred when converting XML to
Document in WSS (Receiver side). It may happen due
to incorrect WSC requests.

Action: Check the WSC (Sender side) request and
resend it.

Type:SEVERE:NIDP:WSF:009

Cause: This error occurred when processing WSS
headers (Receiver side). It may happen due to incorrect
WSS headers in WSC requests.

Action: Check the WSS headers in WSC (Sender side)
request and resent it.

Cause: This error occurred when processing WSS
headers (Receiver side). It may happen due to no WSS
headers in WSC requests.

Action: Check the WSS headers in WSC (Sender side)
request and resend it.

Identity Server (001) 53

Event Code Message Remedy

novdocx (en) 13 May 2009

100102011 No processed WSS header

found

100102012 WSS untrusted certificate Type: SEVERE:NIDP:WSF:012

100102013 Type: SEVERE:NIDP:WSF:013

100102014 Type: SEVERE:NIDP:WSF:014

100102015 Type: SEVERE:NIDP:WSF:015

100102016 Type: SEVERE:NIDP:WSF:016

100102017 Type: SEVERE:NIDP:WSF:017

100102018 Type: SEVERE:NIDP:WSF:018

Type: SEVERE:NIDP:WSF:011

Cause: This error occurred after processing WSS
headers (Receiver side). It may happen due to incorrect
or no WSS headers in WSC requests.

Action: Check the WSS headers in WSC (Sender side)
request and resend it.

Cause: This error occurred when validating signature
on WSS headers (Receiver side). The certificate used
for the signature is not trusted.

Action: Check the certificate used to sign the message.
The certificate is trusted if either it itself or the certificate
of the issuer is installed in the trust store.

100102019 Type: SEVERE:NIDP:WSF:019

100102020 Type: SEVERE:NIDP:WSF:020

100102021 Type: SEVERE:NIDP:WSF:021

100102022 Type: SEVERE:NIDP:WSF:022

100102023 Type: SEVERE:NIDP:WSF:023

100102024 Type: SEVERE:NIDP:WSF:024

100102025 The Service Discovery

Service has not been
initialized.

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

Type: SEVERE:NIDP:WSF:025

Cause: The Discovery Service has not been enabled or
created.

Action: Create and enable a Liberty Discovery Service
using the Access Manager administration utility.

54 Novell Access Manager 3.1 SP1 Event Codes

Event Code Message Remedy

100102032 Type: SEVERE:NIDP:WSF:032

100102033 Type: SEVERE:NIDP:WSF:033

novdocx (en) 13 May 2009

100103001 Web Service Consumer XML

Configuration Parse
Exception.

100103002 Type: SEVERE:NIDP:WSC:002

100103003 Type: SEVERE:NIDP:WSC:003

100103004 Type: SEVERE:NIDP:WSC:004

100103005 Type: SEVERE:NIDP:WSC:005

100103006 Type: SEVERE:NIDP:WSC:006

100103007 Type: SEVERE:NIDP:WSC:007

100103008 Type: SEVERE:NIDP:WSC:008

100103009 Type: SEVERE:NIDP:WSC:009

100103010 Type: SEVERE:NIDP:WSC:010

100103011 Type: SEVERE:NIDP:WSC:011

100103012 Type: SEVERE:NIDP:WSC:012

100103013 Type: SEVERE:NIDP:WSC:013

Type: SEVERE:NIDP:WSC:001

Cause: The nidsConfigXML attribute on the nidsWsf
object has invalid XML.

Action: Delete the nidsConfigXML attribute and
reconfigure WSC.

100103014 Type: SEVERE:NIDP:WSC:014

100103015 Type: SEVERE:NIDP:WSC:015

100103016 Type: SEVERE:NIDP:WSC:016

100103017 Type: SEVERE:NIDP:WSC:017

100104105 Could not initialize Kerberos/

GSS

100104107 Kerberos Configuration is not

properly initialized

Type: SEVERE:NIDP:USERAUTH:105

Cause: Failure at GSS-API

Action: Check the following according the details of the

error message: Keytab file - validity, presently only
understands DES; Service Principal Name (SPN)

Type: SEVERE:NIDP:USERAUTH:107

Cause: Kerberos Configuration is not properly
initialized in the admin user interface

Action: Make sure all the required configuration setting
are properly specified in admin UI

Identity Server (001) 55

Event Code Message Remedy

novdocx (en) 13 May 2009

100104108 SPNEGO/Kerberos method

not implemented

100105001 An error happened while

forwarding a request to a
cluster member.

100105002 Failed to initialize JNDI

connections.

100105003 Error obtaining SOAP

response.

Type: SEVERE:NIDP:USERAUTH:108

Cause: SPNEGO/Kerberos NegTokenInit not
implemented.

Action: NegTokenInit token not implemented as the
server side does not need to generate it new. No Action
needed.

Type: SEVERE:NIDP:APP:001

Cause: An internal error occurred.

Action: Evaluate the error and take appropriate action.

Type: SEVERE:NIDP:APP:002

Cause: NIDP attempts to create JNDI connections to
each user store replica during NIDP startup. In this
case, NIDP was unable to establish connections with
the indicated host.

Action: Ensure that the host is available and that the
configuration information for the replica is correct.

Type: SEVERE:NIDP:APP:003

Cause: A SOAP request was made and a response
was expected, but an error happened retrieving the
response.

Action: Evaluate the indicated reason and take
appropriate action.

100105004 Error in SOAP response

format.

100105005 Error executing Login Policy

Check LDAP Extension for
user on user store

100105006 Type: SEVERE:NIDP:APP:006

Type: SEVERE:NIDP:APP:004

Cause: A SOAP request was made and a response
was expected, the response was obtained but the
format of it was unexpected.

Action: Evaluate the indicated reason and take
appropriate action.

Type: SEVERE:NIDP:APP:005

Cause: User authenticated using X509. An additional
check of the directory's user login policy needs to be
made using an LDAP method extension. This check
was successfully done using an LDAP extension.
However, after the LDAP extension is called, it must be
called a second time to update the user account with a
success or failure. 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

100105007 Type: SEVERE:NIDP:APP:007

56 Novell Access Manager 3.1 SP1 Event Codes

Event Code Message Remedy

novdocx (en) 13 May 2009

100105008 The audit logging system is

not operational.

100106001 Type: SEVERE:NIDP:IDFF:001

200102001 Invalid access code found for

web service specific user
interaction query policy.

200102002 Invalid access code found for

web service specific user
interaction modify policy.

200102003 Unrecognized web service. Type: ERROR:NIDP:WSF:003

Type: SEVERE:NIDP:APP:008

Cause: The audit logging system can, in rare
circumstances, become non-operational.

Action: Examine the error description supplied and
take appropriate action.

Type: ERROR:NIDP:WSF:001

Cause: The web service definition has a service level
user interaction policy that is not ALWAYS or NEVER.
Disallowed values are NO and ONCE.

Action: Using Access Manager management tools, edit
the policy associated with the web service.

Type: ERROR:NIDP:WSF:002

Cause: The web service definition has a service level
user interaction policy that is not ALWAYS or NEVER.
Disallowed values are NO and ONCE.

Action: Using Access Manager management tools, edit
the policy associated with the web service.

200102004 Error writing user interaction

access policy to the data
store.

200102005 Cannot read or write web

service data because zero
data locations are specified.

Cause: The web service definition has a service type
specifier (attribute nidsWsfServiceInstanceType on
object nidsWsfService) that is not recognized.

Action: Using Access Manager management tools,
delete the associated web service and recreate it.

Type: ERROR:NIDP:WSF:004

Cause: The IDP received user interaction access policy
from the user, but was unable to persist it to the data
store.

Action: Check the Access Manager Configuration
datastore to see if it is available.

Type: ERROR:NIDP:WSF:005

Cause: When an IDSIS web service is reading or
writing data it follows the configured data locations to
know where to perform its operations. If the
administrator has not set up any data locations then the
operation must fail.

Action: Add at least one data location the web service.

Identity Server (001) 57

Event Code Message Remedy

novdocx (en) 13 May 2009

200102006 Cannot read or write web

service data because the first
data location is unknown.

200102007 Unexpected error writing data

to web service.

200102008 Unable to locate the cached

NIDPSession object given
session id.

200102009 Cached NIDPPrincipal object

has zero NIDPSubject
objects.

200102010 No web service authority

available.

Type: ERROR:NIDP:WSF:006

Cause: When an IDSIS web service is reading or
writing data it follows the configured data locations to
know where to perform its operations.

Action: Delete all data locations from the associated
web service and add them back into the list.

Type: ERROR:NIDP:WSF:007

Cause: Writing to web services is prone to various
unexpected errors.

Action: Evaluate the reason for the error and take
appropriate action.

Type: ERROR:NIDP:WSF:008

Cause: The user session has expired.

Action: The user must login again.

Type: ERROR:NIDP:WSF:009

Cause: The user session has expired.

Action: The user must login again.

Type: ERROR:NIDP:WSF:010

Cause: A web service of the provided type did not
initialize correctly.

Action: Delete the web service and recreate it.

200102011 No web service available. Type: ERROR:NIDP:WSF:011

Cause: A web service of the provided type does not
exist, or is not enabled.

Action: Create or enable a web service of this type.

200102012 Unable to understand the web

service request's XML.

200102013 Error processing web service

query request.

Type: ERROR:NIDP:WSF:012

Cause: A web service sent a request to the IDP that
cannot be parsed or it is missing data such that the
request cannot be understood.

Action: Notify your system administrator that invalid
web service requests are being made to the system.

Type: ERROR:NIDP:WSF:013

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.

58 Novell Access Manager 3.1 SP1 Event Codes

Event Code Message Remedy

novdocx (en) 13 May 2009

200102014 Error processing web service

modify request.

200102015 Unable to locate the user's

local identifier in the resource
id.

200102016 Unable to locate a cached

NIDPPrincipal object given
the local id.

200102017 Unable to locate a

NIDPIdentity object given the
local id.

200103001 The indicated web service is

not available or it has been
disabled! An attempt was
made to access this service to
operate on the indicated data.

Type: ERROR:NIDP:WSF:014

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.

Type: ERROR:NIDP:WSF:015

Cause: The web service resource id, an identifier
indicating what user the request is destined for, did not
contain the information required to identify the user.

Action: Notify your system administrator that invalid
web service requests are being made to the system.

Type: ERROR:NIDP:WSF:016

Cause: The user session has expired.

Action: The user must login again.

Type: ERROR:NIDP:WSF:017

Cause: The user session has expired.

Action: The user must login again.

Type: ERROR:NIDP:WSC:001

Cause: The Web Service Consumer received a request
and one of the data tokens referenced a data item that
is not available in any of the services known to the
Access Manager.

Action: The system has encountered an invalid
configuration and should be restarted by the system
administrator.

200103002 Cannot make web service

request because there are
zero web service resource
offerings available.

200103003 Unable to locate an identity id

from the authentications
available in the provided
NIDPSession.

200104001 Could not get client certificate. Type: ERROR:NIDP:USERAUTH:001

Type: ERROR:NIDP:WSC:002

Cause: The Web Service Consumer received a request
but there were zero service resource offerings provided.
So, the web service has no destination service to which
a request can be made.

Action: The user must login again.

Type: ERROR:NIDP:WSC:003

Cause: The user session has expired.

Action: The user must login again.

Cause: Could not get user certificate from the client

browser

Action: Install user X509 certificate on the client
browser and try again.

Identity Server (001) 59

Event Code Message Remedy

200104003 Could not read configuration Type: ERROR:NIDP:USERAUTH:003

Cause: Could not read configuration out of file

Action: Make sure the X509 config properties file is

present.

novdocx (en) 13 May 2009

200104004 User Certificate

Authentication Failed

200104005 No matching Principal found. Type: ERROR:NIDP:USERAUTH:005

200104006 More than one Principal

matched.

Type: ERROR:NIDP:USERAUTH:004

Cause: User Certificate Authentication Failed due to
the reasons in detailed message

Action: Take appropriate action as per the reasons in
the detailed message

Cause: No Principal from X509Certificate found in User
store

Action: Check the X509Class Method and it's attribute
mapping profile as defined using administration tool.
Also, make sure the matched user exists in the User
store.

Type: ERROR:NIDP:USERAUTH:006

Cause: Principal from X509Certificate Multiple users
found in User store which matched Principal from
X509Certificate based on X509Class attribute mapping
profile.\

Action: Check the X509Class Method and it's attribute
mapping profile as defined using administrator tool.
Also, check if multiple user exists in the User store(s).

200104008 Error loading Trust store Type: ERROR:NIDP:USERAUTH:008

200104009 Client certificate not yet valid. Type: ERROR:NIDP:USERAUTH:009

Cause: X509 certificate is valid in the future

Action: Use a valid certificate

200104010 Client certificate no longer

valid.

200104011 The Certificate has been

revoked.

200104012 Error Parsing Certificate. Type: ERROR:NIDP:USERAUTH:012

Type: ERROR:NIDP:USERAUTH:010

Cause: X509 certificate is expired

Action: Use a valid certificate

Type: ERROR:NIDP:USERAUTH:011

Cause: The Certificate has been revoked

Action: Use a valid certificate which is not revoked.

Cause: Error Parsing Certificate when performing

certificate validations

Action: Use a valid X509 certificate.

60 Novell Access Manager 3.1 SP1 Event Codes

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.

novdocx (en) 13 May 2009

200104018 Could not verify CRL

signature.

200104019 Could not find Key for this

server.

200104020 CRL/OCSP is too old; New

version already available.

200104021 No Issuer Certificate found. Type: ERROR:NIDP:USERAUTH:021

Type: ERROR:NIDP:USERAUTH:018

Cause: Could not verify signature on the fetched CRL

Action: Make sure the CRL server public key/certificate

is in NIDP/ESP trust store.

Type: ERROR:NIDP:USERAUTH:019

Cause: Could not find Key/Cert for NIDP/ESP server
towards authenticating to OCSP server

Action: Make sure the NIDP/ESP Signing keystore has
appropriate Key/Cert in it.

Type: ERROR:NIDP:USERAUTH:020

Cause: During validations, the fetched CRL Or OCSP
is stale. Newer version will be available

Action: In case of CRLs, next attempt to fetch CRL
should get a fresh CRL after purging the cached one. In
case of OCSP, notify the OCSP server administrator.

Cause: Issuer of user certificate not found which is
required for OCSP validations

Action: Make sure the issuer of user/client certificate is
either found in certificate-chain or in NIDP/ESP trust
store.

200104022 Error getting OCSP

Response.

200104023 Error processing OCSP

Response.

Type: ERROR:NIDP:USERAUTH:022

Cause: Could not get OCSP Response from the OCSP
server

Action: Make sure its going to the right OCSP server.

Type: ERROR:NIDP:USERAUTH:023

Cause: OCSP response could not be processed

Action: Make sure its going to the right OCSP server

and that it is operating correctly.

Identity Server (001) 61

Event Code Message Remedy

novdocx (en) 13 May 2009

200104024 At least one parameter of

OCSPProcessor was
uninitialized.

200104025 Request was already

generated.

200104026 OCSP response was already

processed

200104027 Internal error occurred in the

OCSP Server.

200104028 Your request did not fit the

RFC 2560 syntax.

Type: ERROR:NIDP:USERAUTH:024

Cause: At least one parameter of OCSPProcessor was
uninitialized during OCSP validations

Action: Make sure the NIDP/ESP Signing keystore has
appropriate Key/Cert in it. Also, that the NIDP/ESP
OCSP trust store has the valid public-key/certificate of
OCSP server.

Type: ERROR:NIDP:USERAUTH:025

Cause: OCSP request was already generated for
certificate(s)

Action: Check the client certificate chain.

Type: ERROR:NIDP:USERAUTH:026

Type: ERROR:NIDP:USERAUTH:027

Cause: OCSP server responded to the request with an
internal error.

Action: Contact OCSP server administrator.

Type: ERROR:NIDP:USERAUTH:028

Cause: OCSP server responded to the request with
malformed request message.

Action: Contact OCSP administrator and check the
request.

200104029 Your request was not signed. Type: ERROR:NIDP:USERAUTH:029

Cause: Request to OCSP server needs to be signed.

Action: Enable signing of OCSP requests in

X509Class administration.

200104030 The server was too busy to

answer you.

200104031 The server could not

authenticate you.

Type: ERROR:NIDP:USERAUTH:030

Cause: OCSP server is too busy to respond to
requests.

Action: Contact OCSP server administrator.

Type: ERROR:NIDP:USERAUTH:031

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.

62 Novell Access Manager 3.1 SP1 Event Codes

Event Code Message Remedy

novdocx (en) 13 May 2009

200104032 Unknown OCSPResponse

status code.

200104033 No valid OCSPResponse

obtained.

200104034 Response was generated in

the future.

200104035 Error verifying responder

certificate.

200104036 Response seems to be signed

with untrusted certificate.

Type: ERROR:NIDP:USERAUTH:032

Cause: OCSP server responded to the request with
unknown status code.

Action: Contact OCSP server administrator.

Type: ERROR:NIDP:USERAUTH:033

Cause: Invalid OCSP response obtained.

Action: Check the OCSP server response version and

contact administrator.

Type: ERROR:NIDP:USERAUTH:034

Cause: OCSP response is not yet valid.

Action: Disable OCSP validations Or Contact OCSP

server administrator.

Type: ERROR:NIDP:USERAUTH:035

Cause: This may happen when reading the OCSP trust
store during OCSP validations.

Action: Make sure OCSP trust store exists on NIDP
server.

Type: ERROR:NIDP:USERAUTH:036

Cause: OCSP server trusted-root certificate not found
in OCSP trust store.

200104037 The received responder id

does not match your
responder certificate.

200104038 Could not verify OCSP server

response.

200104039 No client certificates inside

OCSP response.

Action: Import OCSP server trusted root in Nidp's
OCSP trust store.

Type: ERROR:NIDP:USERAUTH:037

Cause: The response ID received in OCSP response
does not match.

Action: Make sure NIDP's OCSP trust store has the
right OCSP server public-key certificate.

Type: ERROR:NIDP:USERAUTH:038

Cause: OCSP server response is incorrect.

Action: Verify the OCSP server URL. Make sure

NIDP's OCSP trust store has the right OCSP server
public-key certificate.

Type: ERROR:NIDP:USERAUTH:039

Cause: Empty response from OCSP server.

Action: Verify the OCSP server URL.

Identity Server (001) 63

Event Code Message Remedy

novdocx (en) 13 May 2009

200104040 Number of certificates inside

OCSP response does not fit
to request.

200104041 Certificate was revoked in the

future.

200104042 Received certificate twice or

one, that was not requested.

200104043 Request was not accepted. Type: ERROR:NIDP:USERAUTH:043

200104044 Wrong response type (not

application/ocsp-response).

Type: ERROR:NIDP:USERAUTH:040

Cause: OCSP response does not contain the
requested number of certificate status.

Action: Verify the OCSP server URL.

Type: ERROR:NIDP:USERAUTH:041

Cause: OCSP response not yet valid.

Action: Verify the OCSP server URL.

Type: ERROR:NIDP:USERAUTH:042

Cause: OCSP response does not match request.

Action: Verify the OCSP server URL.

Cause: Could not connect to OCSP server.

Action: Verify the OCSP server URL.

Type: ERROR:NIDP:USERAUTH:044

Cause: Malformed OCSP response.

Action: Verify the OCSP server URL.

200104045 No OCSPResponse

message.

200104046 Could not read whole

OCSPResponse.

200104047 Exception Occurred. Type: ERROR:NIDP:USERAUTH:047

200104051 Unsupported critical extension

OID(s).

200104053 Error processing CRL

Response.

Type: ERROR:NIDP:USERAUTH:045

Cause: No OCSPResponse message.

Action: Verify the OCSP server URL.

Type: ERROR:NIDP:USERAUTH:046

Cause: Malformed OCSP response.

Action: Verify the connection to OCSP server URL.

Cause: Error getting CRL.

Action: Verify the connection to CRL server URL.

Type: ERROR:NIDP:USERAUTH:051

Cause: Some Critical extension OID(s) not understood.

Action: Check the certificate for unsupported critical

extensions. If needed, add the processing of the critical
extension in NDPCertPathChecker class.

Type: ERROR:NIDP:USERAUTH:053

Cause: Error processing CRL Response.

Action: Check X509class config and user/client

certificate CRL extension.

64 Novell Access Manager 3.1 SP1 Event Codes

Event Code Message Remedy

novdocx (en) 13 May 2009

200104054 Error processing certificate

validations.

200104055 Protocol not supported or

none specified.

200104057 Unable to do X509 Certificate

based authentication over non
SSL (HTTP)

200104100 Error processing

Authorization header

200104101 Error processing SPNEGO/

Kerberos

Type: ERROR:NIDP:USERAUTH:054

Cause: Error processing CRL/OCSP validations.

Action: Check X509class config and user/client

certificate CRL extension.

Type: ERROR:NIDP:USERAUTH:055

Cause: Transport protocol not supported to fetch CRL.

Action: Currently, CRLs can be fetched over http and

LDAP protocols. Make sure the X509class config and/
or user/client certificate CRL extension does not have
any other transport protocol specified.

Type: ERROR:NIDP:USERAUTH:057

Cause: URL protocol is HTTP

Action: URL protocol needs to be HTTPS

Type: ERROR:NIDP:USERAUTH:100

Cause: Could not process HTTP Authorization header

Action: Try with correct authorization header with

base64 encoded SPNEGO token

Type: ERROR:NIDP:USERAUTH:101

Cause: Error processing SPNEGO/Kerberos. The
cause is included in detailed message

Action: Take action as per the detailed error message

200104102 No Kerberos Principal found

in the token

200104103 No SPNEGO Token found Type: ERROR:NIDP:USERAUTH:103

200104104 GSS Context already

established

200104106 Unrecognized SPNEGO

To ke n

Type: ERROR:NIDP:USERAUTH:102

Cause: Failure at GSS-API

Action: Make sure the Kerberos keytab file is

generated correctly by KDC

Cause: No SPNEGO Token found in the request

Action: Include the SPNEGO token in the request to

use this authentication

Type: ERROR:NIDP:USERAUTH:104

Cause: GSS Context already established

Action: Close the browser and try again

Type: ERROR:NIDP:USERAUTH:106

Cause: Unrecognized SPNEGO Token

Action: Include the correct SPNEGO token in the

request to use this authentication

Identity Server (001) 65

Event Code Message Remedy

novdocx (en) 13 May 2009

200104109 Malformed SPNEGO

NegTokenInit

200104110 Malformed SPNEGO Token

field

200104111 Multiple users matched in the

user stores

200104112 No user matched in the user

stores

200107005 Error building certificate chain

during validations.

Type: ERROR:NIDP:USERAUTH:109

Cause: Malformed token NegTokenInit

Action: Try again with correct NegTokenInit token

Type: ERROR:NIDP:USERAUTH:110

Cause: Malformed SPNEGO Token field

Action: Try again with correct NegTokenInit token

Type: ERROR:NIDP:USERAUTH:111

Cause: Multiple users matched in the user stores

Action: Make sure the users are unique in user stores

Type: ERROR:NIDP:USERAUTH:112

Cause: No user found in the user stores

Action: Make sure the user attribute (as defined in

admin UI) is populated in correct format.

Type: ERROR:NIDP::005

Cause: This could occur when all the CDPs are
unreachable.

Action: Change the Certificate with correct CDPs or
make sure CDP is up and able to serve.

300101002 An authenticated subject is

required.

300101003 An authentication principal is

required.

300101004 Identity does not exist or is not

specified.

Type: WARN:NIDP:USERMSG:002

Cause: An action that can only be performed by an
authenticated user was attempted.

Action: Provide proper user credentials and retry
desired action.

Type: WARN:NIDP:USERMSG:003

Cause: An action that can only be performed by an
authenticated user was attempted.

Action: User must be authenticated to perform
operation.

Type: WARN:NIDP:USERMSG:004

Cause: An action was attempted that requires a
federated identity to exist.

Action: Create a federated link prior to performing the
action.

66 Novell Access Manager 3.1 SP1 Event Codes

Event Code Message Remedy

novdocx (en) 13 May 2009

300101005 Invalid or no provider is

specified.

300101006 An authenticated session is

required.

300101007 Invalid artifact. Type: WARN:NIDP:USERMSG:007

300101008 No assertion returned in

response.

Type: WARN:NIDP:USERMSG:005

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.

Type: WARN:NIDP:USERMSG:006

Cause: An action that can only be performed by an
authenticated user was attempted.

Action: Provide proper user credentials and retry
desired action.

Cause: An artifact was received from an identity
provider that is invalid or has not been used within a
reasonable time frame.

Action: Make sure that the provider sending the artifact
is trusted or check for possible security intrusions.

Type: WARN:NIDP:USERMSG:008

Cause: Assertions will not be returned in a response
whenever authentication at the identity provider fails.
The cause for this can include invalid configurations
and canceling the authentication process at the identity
provider.

Action: Make sure that both the identity and service
providers are configured correctly to trust each other.
Provide proper credentials during the authentication
process at the identity provider.

300101009 Invalid issuer. Type: WARN:NIDP:USERMSG:009

Cause: A response was received from a provider that is
not trusted.

Action: Make sure intended provider is trusted or
check for possible intrusions.

300101010 Response does not match

request.

Type: WARN:NIDP:USERMSG:010

Cause: A response was received for a request that was
not issued.

Action: Retry action and check for possible intrusion.

Identity Server (001) 67

Event Code Message Remedy

300101011 Assertion is being replayed. Type: WARN:NIDP:USERMSG:011

Cause: An assertion has been received that was
already used to authenticate a user at the service
provider.

Action: This is a security mechanism that if persists
may require some investigation to determine who is
trying to replay the assertion. Assertions are only good
for single use.

novdocx (en) 13 May 2009

300101012 Assertion does not contain an

authentication statement.

300101013 Unable to validate the subject

of the assertion.

300101014 Assertion not yet valid. Type: WARN:NIDP:USERMSG:014

Type: WARN:NIDP:USERMSG:012

Cause: An identity provider has sent an assertion that
is not complete.

Action: Check with administrator of trusted provider to
determine why statement is not being sent.

Type: WARN:NIDP:USERMSG:013

Cause: A subject may not have been sent in the
assertion or was not valid. This check protects from
certain assertion attacks.

Action: If persistent, check the protocol message sent
for a missing subject and then notify administrator of
trusted site.

For more information, see “Federation with External

SAML 2.0 Partner Gives 300101013 Error” (http://
www.novell.com/support/php/
search.do?cmd=displayKC&docType=kc&externalId=3
903427&sliceId=2&docTypeID=DT_TID_1_1&dialogID
=69860557&stateId=0%200%2069862016).

Cause: An assertion was received that is not valid until
sometime in the future.

300101015 Assertion no longer valid. Type: WARN:NIDP:USERMSG:015

68 Novell Access Manager 3.1 SP1 Event Codes

Action: Check server's clock for accuracy. Attempt to

validate the clock accuracy of the computer generating
the assertion.

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.

Event Code Message Remedy

300101016 No matching audience. Type: WARN:NIDP:USERMSG:016

Cause: An assertion was received that was not
intended for your server.

Action: Determine the origin of the assertion and make
sure that you want to accept assertions from it.

For more information, see “Access Manager

300101016 Error - No Matching Audience” (http://
www.novell.com/support/php/
search.do?cmd=displayKC&docType=kc&externalId=3
260366&sliceId=2&docTypeID=DT_TID_1_1&dialogID
=69860436&stateId=0%200%2069856899).

novdocx (en) 13 May 2009

300101017 Missing or invalid signature on

assertion.

300101018 Missing or invalid signature on

request/response.

300101020 Digital signature is required. Type: WARN:NIDP:USERMSG:020

300101021 Signature validation failed. Type: WARN:NIDP:USERMSG:021

300101022 An undetermined problem in

the message format has
occurred.

Type: WARN:NIDP:USERMSG:017

Cause: The identity provider did not sign.

Action: Check with provider of assertion to determine

why assertion is not signed.

Type: WARN:NIDP:USERMSG:018

Cause: A protocol message was received that was
expected to be digitally signed, but was not.

Action: It may be necessary to contact the trusted
provider administrator to determine why the message is
not signed. Make sure authentication request signing
settings match those for the trusted provider.

Cause: The digital signature of a protocol message
could not be verified using the public key obtained in the
metadata of a trusted provider.

Action: Update the metadata of trusted provider. This
should ensure you have the latest signing certificate.

Type: WARN:NIDP:USERMSG:022

Cause: An error was detected in the exchange of either
a 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.

Action: Check the configuration for identifying users for
the trusted provider and ensure the specified method
can resolve to a single user in your directory.

Identity Server (001) 69

Event Code Message Remedy

300101024 Failed to load java class. Type: WARN:NIDP:USERMSG:024

Cause: A Java class failed to be loaded during program
execution.

Action: Check the logs to determine the class that is
failing to load. Make sure the class being loaded is in
the classpath of the JVM.

300101025 Type: WARN:NIDP:USERMSG:025

300101026 Type: WARN:NIDP:USERMSG:026

300101027 Type: WARN:NIDP:USERMSG:027

novdocx (en) 13 May 2009

300101028 SOAP TLS authorization

failed.

300101029 Type: WARN:NIDP:USERMSG:029

300101030 SOAP fault. Type: WARN:NIDP:USERMSG:030

300101031 Received an identity that does

not resolve to the current
logged in user.

Type: WARN:NIDP:USERMSG:028

Cause: SSL mutual authentication is being used to
authenticate a SOAP back channel session and the
credentials cannot be validated.

Action: Make sure certificates for back channel
communications are trusted on each end.

For more information, see “Access Manager

300101028 - SOAP TLS Authorization Failed” (http://
www.novell.com/support/php/
search.do?cmd=displayKC&docType=kc&externalId=3
813149&sliceId=2&docTypeID=DT_TID_1_1&dialogID
=69848431&stateId=0%200%2069844751).

Cause: An error was detected in the transmission of
protocols using SOAP.

Action: Turn tracing on and look for any obvious
causes for the problem.

Type: WARN:NIDP:USERMSG:031

Cause: This is caused when a user is logged in with
one identity and then attempts to authenticate as the
identity of another user. For a given session, all
authentications must resolve to the same user.

300101032 Assertion is expired. Type: WARN:NIDP:USERMSG:032

70 Novell Access Manager 3.1 SP1 Event Codes

Action: Log out of the current user and log in again as

the desired user.

Cause: The use of the assertion to authenticate the
server did not occur within the time limits specified by
the assertion.

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.

Event Code Message Remedy

novdocx (en) 13 May 2009

300101033 IDP return authentication

failure.

300101034 No target is defined. Type: WARN:NIDP:USERMSG:034

300101035 Type: WARN:NIDP:USERMSG:035

300101036 Not enough memory to

process request.

Type: WARN:NIDP:USERMSG:033

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. It may just be necessary to
attempt authentication again.

Cause: A request was made of the server's intersite
transfer service without specifying a target resource.

Action: Requests for the intersite transfer service must
include an id of the intended service provider to be
authenticated as well as the target resource to be
displayed. To avoid this error, provide an
&TARGET="value" on the URL.

Type: WARN:NIDP:USERMSG:036

Cause: The system does not have enough memory to
complete the requested action.

Action: Wait a few moments for memory to free up and
retry request. It may be necessary to add additional
memory to the server.

300101037 Server is not in a running

state.

300101038 JSP file not found. Type: WARN:NIDP:USERMSG:038

300101039 Invalid authentication

credentials were provided.

Type: WARN:NIDP:USERMSG:037

Cause: A request was made of the server that can only
be performed when the server is in a running state.

Action: Start the server.

Cause: An attempt was made to load a JSP page that

does not exist.

Action: Determine the JSP not loading and make sure
it is in the correct location.

Type: WARN:NIDP:USERMSG:039

Cause: A user has attempted to authenticate to the
system with credentials that are not valid for the
account.

Action: User needs to enter correct credentials.

Identity Server (001) 71

Event Code Message Remedy

300101040 User password has expired. Type: WARN:NIDP:USERMSG:040

Cause: A user has attempted to authenticate to the
system with a password that is expired.

Action: The user needs to create a new password.

novdocx (en) 13 May 2009

300101041 User account identification

failed.

300101042 Invalid assertion conditions. Type: WARN:NIDP:USERMSG:042

Type: WARN:NIDP:USERMSG:041

Cause: Account identification can fail due to: 1. User
cancels authentication request 2. User cannot be
uniquely identified by Matching Expression 3.
Necessary attributes to do user matching or
provisioning were not obtained.

Action: Check Account Identification configuration for
the trusted provider and make sure that necessary
attributes are available. If using Matching Expressions,
make sure that they include attributes that can resolve
to a single user. If using Provisioning, make sure
required attributes are all available in the defined
attribute set for the trusted provider.

For more information, see “Access Manager Error

300101041 Provisioning New Users Using SAML2”
(http://www.novell.com/support/php/
search.do?cmd=displayKC&docType=kc&externalId=3
219302&sliceId=1&docTypeID=DT_TID_1_1&dialogID
=69780245&stateId=0%200%2069778277).

Cause: A set of conditions that are not understood
were sent as part of an assertion.

Action: Check with the provider of the assertion to
determine what these conditions are and why they are
being sent.

300101046 Unknown URL host. Type: WARN:NIDP:USERMSG:046

300101047 An untrusted provider is being

referenced in a request or a
response.

72 Novell Access Manager 3.1 SP1 Event Codes

Action: Use logs to determine the problematic host and

determine why DNS is failing.

Type: WARN:NIDP:USERMSG:047

Action: Use logs to determine the provider that is
untrusted and then create a trusted relationship if
desired.

Event Code Message Remedy

novdocx (en) 13 May 2009

300101048 The LDAP servers are too

busy to accept more users.

300101049 The HTTPS protocol was not

used to access this
authentication card.

300101050 The Authentication Card

specified is not valid.

300101051 The user’s session limit has

been reached.

Type: WARN:NIDP:USERMSG:048

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. It may be
necessary to add additional LDAP servers or upgrade
the hardware specifications of the existing LDAP
servers.

Type: WARN:NIDP:USERMSG:049

Cause: Accessing the site was done via http, not https.

Action: Access the site again using https.

Type: WARN:NIDP:USERMSG:050

Cause: An invalid card identifier was used, most likely
due to modifying a url.

Action: Specify cards to use only by clicking on them.

Type: WARN:NIDP:USERMSG:051

Cause: User has already logged in the maximum
allowable times.

300101052 A response was expected at

the url but none was found.

300101053 CardSpace authentication

profile failed to load.

300101054 CardSpace authentication

fails becase a required
attribute is not in assertion.

300102001 No Discovery Service

Configured! Unable to create
the requested resource
offering!

Action: Logout of one or more sessions.

Type: WARN:NIDP:USERMSG:052

Cause: The wrong endpoint may be accessed for the
operation desired.

Action: Check the action being performed against the
url/endpoint being accessed.

Type: WARN:NIDP:USERMSG:053

Cause: TrustedProvider failed to load (probably due to
certificate errors).

Action: Check the certificates for the trusted provider
and make sure they are valid.

Type: WARN:NIDP:USERMSG:054

Cause: A required attribute was not returned in the
assertion provided by an STS.

Action: Check the attribute value at the STS, or make
the attribute optional.

Type: WARN:NIDP:WSF:001

Cause: The system administrator did not create or
enable a Discovery service.

Action: Create or enable a Discovery web service.

Identity Server (001) 73

Event Code Message Remedy

novdocx (en) 13 May 2009

300102002 Unable to find user object with

identifier.

300102003 Unrecognized select string for

service.

300102004 Unable to process web

service query request! Select
string missing!

300102005 Unable to perform trusted

user interaction service
request. Web service
authority was not found.

Type: WARN:NIDP:WSF:002

Cause: An LDAP search was performed for a user
object with a given identifier. This identifier may be a
GUID. The search resulted in zero hits. This usually
means that web service data cannot be read or written
for the user.

Action: The user needs to login again.

Type: WARN:NIDP:WSF:003

Cause: The select string (XPath) is either incorrectly
formed or not supported by the web service.

Action: The system administrator must enable services
to support the select string.

Type: WARN:NIDP:WSF:004

Cause: The select string (XPath) is not in the web
service query request.

Action: Inform your system administrator that an
improperly formatted web service request is being
made.

Type: WARN:NIDP:WSF:005

Cause: An internal system error.

Action: The system has encountered an invalid

configuration and should be restarted by the system
administrator.

300102006 Unable to perform trusted

user interaction service
request. Unable to obtain
trusted user interaction
service description from
SOAP headers.

300102007 Unable to perform trusted

user interaction service
request. No trusted user
interaction service description
provided in SOAP headers.

300102008 Trusted user interaction

service failed.

Type: WARN:NIDP:WSF:006

Cause: The web service making the request did not
provide valid or complete information about the trusted
user interaction service.

Action: The system administrator must complete the
definition of the trusted interaction service.

Type: WARN:NIDP:WSF:007

Cause: The web service making the request did not
provide valid or complete information about the trusted
user interaction service.

Action: The system administrator must complete the
definition of the trusted interaction service.

Type: WARN:NIDP:WSF:008

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.

74 Novell Access Manager 3.1 SP1 Event Codes

Event Code Message Remedy

novdocx (en) 13 May 2009

300102009 Error creating user interaction

redirection request.

300102010 Unable to perform user

interaction redirection
request. User intervention
service not found.

300102011 Error reading data from LDAP

data attribute plugin.

300102012 Error writing data to LDAP

data attribute plugin.

Type: WARN:NIDP:WSF:009

Cause: There was an error converting the redirect
request to an XML DOM.

Action: Evaluate the reason and take the appropriate
actions.

Type: WARN:NIDP:WSF:010

Cause: There must be an interaction service on the IDP
creating the user interaction redirection request.

Action: If it does not exist, using Access Manager
management tools, create one.

Type: WARN:NIDP:WSF:011

Cause: If a web service's data locations includes LDAP,
then LDAP data attribute plugins are used to read data
from the LDAP user store. This error provides
descriptions of various errors that can happen while
doing this.

Action: Evaluate the reason and take the appropriate
actions.

Type: WARN:NIDP:WSF:012

Cause: If a web service's data locations includes LDAP,
then LDAP data attribute plugins are used to write data
to the LDAP user store. This error provides descriptions
of various errors that can happen while doing this.

300102013 Cannot read/write Credential

Profile data because the
user's LDAP user store
distinguished name is not
available.

300102014 A Web Service request was

received for a user, but the
session for that user is not
found.

300102015 A Web Service request was

received for a user, but the
session for that user has
insufficient data in it.

Action: Evaluate the reason and take the appropriate
actions.

Type: WARN:NIDP:WSF:013

Cause: All Credential Profile reads and writes end up
operating on a user object in a user store. If this user
object cannot be found, then the operation must fail.
This may happen if a temporary identifier is being used
for the authentication.

Action: Use a permanent federation to the service
provider if your system allows it.

Type: WARN:NIDP:WSF:014

Cause: The user's login has timed out and has been
removed from the system.

Action: The user must login again.

Type: WARN:NIDP:WSF:015

Cause: An internal error has occurred.

Action: The user must login again.

Identity Server (001) 75

Event Code Message Remedy

novdocx (en) 13 May 2009

300102016 A Web Service request was

received for a user, but the
Liberty User Profile object for
that user is unavailable.

300102017 A Web Service request was

received for a user, and
attempt to read the requested
attributes from the Liberty
User Profile object was made,
but an error occurred.

300102018 A Web Service request was

received for a user, While
reading user data from an
LDAP user object, a mismatch
occurred because the LDAP
attribute is multi-valued, but
the Liberty attribute is single­valued.

300102019 The user used an X509

Certificate to authenticate and
we tried to put the cert into the
SecretStore as a Base64 DER
encoded cert, but we got an
encoding error from the
security layer when trying to
get the DER encoded cert.
Result is that there will not be
a X509 Certificate in Secret
Store for this user.

Type: WARN:NIDP:WSF:016

Cause: An internal error has occurred.

Action: Make sure the administrator user has rights to

read, write and create Liberty User Profile objects in the
configuration data store.

Type: WARN:NIDP:WSF:017

Cause: An internal error has occurred.

Action: Evaluate the reason and take the appropriate

actions.

Type: WARN:NIDP:WSF:018

Cause: A multi-valued LDAP attribute has been
mapped to a single-valued Liberty attribute.

Action: Change the attribute mapping.

Type: WARN:NIDP:WSF:019

Cause: The X509 certificate cannot be encoded.

Action: Review the type of X509 certificates that are

being used for authentication.

300102020 A SAMLAssertion was

requested for a given user.
While generating the
SAMLAssertion an error
occurred.

300102021 Type: WARN:NIDP:WSF:021

300102022 Type: WARN:NIDP:WSF:022

300103001 The web service request did

not return a response within
the protocol timeout limit.
Request abandoned.

76 Novell Access Manager 3.1 SP1 Event Codes

Type: WARN:NIDP:WSF:020

Cause: The SAMLAssertion cannot be created.

Action: Review the reason for the failure and take

appropriate actions.

Type: WARN:NIDP:WSC:001

Cause: The web service consumer waited for the web
service request to return a response, but it did not
during the allowed waiting period.

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.

Event Code Message Remedy

novdocx (en) 13 May 2009

300103002 An unexpected error

happened in the web service
consumer while processing a
web service request.

300103003 Web service consumer

request pending data packet
id is not available in request.

300103004 The Web service consumer

request pending data packet
with the indicated id is not
available in web service
consumer's cache.

Type: WARN:NIDP:WSC:002

Cause: There are various reasons why a web service
request could fail.

Action: Evaluate the reason and take appropriate
actions.

Type: WARN:NIDP:WSC:003

Cause: After user interaction, processing of the original
request returns to the web service consumer. A data
packet containing information about how to continue the
request is cached on the web service consumer. The id
of that packet must be passed through all redirections
and requests associated with the user interaction. If that
id is not available when the web service consumer
regains control, then the request cannot continue.

Action: Submit the request again.

Type: WARN:NIDP:WSC:004

Cause: After user interaction, processing of the original
request returns to the web service consumer. A data
packet containing information about how to continue the
request is cached on the web service consumer. The id
of that packet must be passed through all redirections
and requests associated with the user interaction. That
id will be used to access the pending data packet when
the web service consumer regains control. If the
pending data packet with the corresponding id is no
longer available on the system, then the request cannot
continue. The data packet may have timed out.

300104049 Could not find NIDP PKIX

Certificate Path Checker
Class.

300104050 Could not instantiate NIDP

PKIX Certificate Path Checker
Class.

Action: Submit the request again.

Type: WARN:NIDP:USERAUTH:049

Cause: PKIX Certificate Path Checker Class not found.

Action: Warning message that PKIX Certificate Path

Checker Class not found. This optional class is used to
process custom certificate extensions. If required, this
class needs to be in NIDP classpath. It may not be
present on ESP.

Type: WARN:NIDP:USERAUTH:050

Cause: Incorrect class constructor.

Action: Make sure the class has the right constructor.

Identity Server (001) 77

Event Code Message Remedy

novdocx (en) 13 May 2009

300105001 No user Login Policy Check

LDAP Extension method
available on user store.

300105002 Type: WARN:NIDP:APP:002

300105003 Type: WARN:NIDP:APP:003

300105004 Type: WARN:NIDP:APP:004

300105005 Type: WARN:NIDP:APP:005

300105006 Type: WARN:NIDP:APP:006

300105007 Type: WARN:NIDP:APP:007

300105008 Type: WARN:NIDP:APP:008

300105009 Type: WARN:NIDP:APP:009

300105010 Type: WARN:NIDP:APP:010

Type: WARN:NIDP:APP:001

Cause: User authenticated using X509. An additional
check of the directory's user login policy needs to be
made using an LDAP method extension. However, the
directory indicated does not support the required LDAP
extension method.

Action: Make sure the LDAP extension method with
OID 2.16.840.1.113719.1.39.42.100.25 is present in the
user store. Versions 8.7.3 and greater of eDirectory
should support this method.

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

78 Novell Access Manager 3.1 SP1 Event Codes

Event Code Message Remedy

novdocx (en) 13 May 2009

300105021 Unable to delete unneeded

Image Pool Image File.

300105022 Unable to create a necessary

directory for the Image Pool.

Type: WARN:NIDP:APP:21

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. Part of synchronization
process involves deleting from the file system images
that no longer exist in eDirectory. Also, the reverse is
true, images that are new to eDirectory and do not yet
exist on the file system are created in directories that
reflect the image set. File system errors may occur
during this synchronization process if a file or directory
cannot be deleted or created.

Action: Ensure that no errant files are copied or
directories manually created in the file system path
[TOMCAT_HOME]/webapps/nidp/images/pool. Make
sure the disk is not full.

Type: WARN:NIDP:APP:22

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. Part of synchronization
process involves deleting from the file system images
that no longer exist in eDirectory. Also, the reverse is
true, images that are new to eDirectory and do not yet
exist on the file system are created in directories that
reflect the image set. File system errors may occur
during this synchronization process if a file or directory
cannot be deleted or created.

300105023 Unable to create a necessary

directory for the Image Pool.

Action: Make sure the disk is not full.

Type: WARN:NIDP:APP:23

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. Part of synchronization
process involves deleting from the file system images
that no longer exist in eDirectory. Also, the reverse is
true, images that are new to eDirectory and do not yet
exist on the file system are created in directories that
reflect the image set. File system errors may occur
during this synchronization process if a file or directory
cannot be deleted or created.

Action: Make sure the disk is not full.

Identity Server (001) 79

Event Code Message Remedy

novdocx (en) 13 May 2009

300105024 Unable to update the "last

used" attribute of an identity
object.

300105025 Unable to auto delete an

identity object.

300105027 No Filename specified in

System property.

Type: WARN:NIDP:APP:24

Cause: Each time an identity object is accessed, the
"last used" time is updated. This allows the system to
track identities that have not been used for a
configurable time period so that they may be deleted.

Action: Make sure the administrator object for the
Trust/Config data store has rights to the indicated
directory context.

Type: WARN:NIDP:APP:25

Cause: Periodically, the IDP attempts to clean up
(delete) identity objects that have not been used for a
configurable period of time. If an old unused identity is
found, an attempt will be made to delete it. If that delete
fails, this error will be logged.

Action: Make sure the administrator object for the
Trust/Config data store has rights to the indicated
directory context.

Type: WARN:NIDP:APP:27

Cause: Trying to read properties from file which is not
specified in System property.

Action: Make sure the properties file is passed in the
appropriate system property .

300105028 Error trying to delete a

CardSpace Issued Card
Identity Object.

300105029 Cannot load a custom LDAP

Store Plugin module.

Type: WARN:NIDP:APP:28

Cause: When a CardSpace Managed Card that is
backed by a Personal Card is issued, an Identity object
is created to represent the "Federation" that allows that
card to log into the IDP without supplying any additional
credentials. For security reasons, the user may delete
that Identity object, or that "federation," when the
associated card becomes out of date or compromised.
However, when the system attempted to delete the
Identity object, the indicated error happened.

Action: Examine the supplied error detail and take
applicable actions.

Type: WARN:NIDP:APP:29

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.

80 Novell Access Manager 3.1 SP1 Event Codes

Event Code Message Remedy

novdocx (en) 13 May 2009

300105030 Cannot instantiate a custom

LDAP Store Plugin module.

300105031 A user store was configured

with an unrecognized
directory type.

300106001 Type: WARN:NIDP:IDFF:001

300106002 Type: WARN:NIDP:IDFF:002

300106003 Type: WARN:NIDP:IDFF:003

300106004 Type: WARN:NIDP:IDFF:004

300106005 Type: WARN:NIDP:IDFF:005

Type: WARN:NIDP:APP:30

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. Also, ensure the LDAP Store Plugin has a
zero parameter constructor.

Type: WARN:NIDP:APP:031

Cause: The configuration was manually modified to
include an invalid directory type specifier. Or the
configuration has been corrupted. Or there was no valid
implementation of an LDAP Store Plugin for this
directory type.

Action: Examine the supplied error detail and take
applicable actions.

500102001 The authentication

information for the user was
successfully found.

500102002 The Liberty User Profile object

for the associated user was
found in the configuration
datastore.

500102003 Created new user profile

object.

500102004 Read data from user profile

object.

Type: INFO:NIDP:WSF:001

Scenario: A Web Service request was made to query or
modify user attributes. The user's authentication
information was successfully found.

See Also: 600102001

Type: INFO:NIDP:WSF:002

Scenario: A Web Service request was made to query or
modify user attributes. One of the data locations
specified for the service is the Liberty User Profile
object and that object was successfully found.

Type: INFO:NIDP:WSF:003

Scenario: A request was made to query or modify user's
attributes. A Liberty User Profile object did not yet exist
for this user, so one was created.

Type: INFO:NIDP:WSF:004

Scenario: A Web Service request was made to query
user attributes. One of the data locations specified for
the service is the Liberty User Profile object and that
object was successfully read.

See Also: 600102002

Identity Server (001) 81

Event Code Message Remedy

novdocx (en) 13 May 2009

500102005 Attempted to read data from

the Liberty User Profile object,
but it did not contain the
requested data.

500102006 Read data from attributes

obtained when a remote
authentication source pushed
the attributes to the NIDP.

500102007 Read data by making a call to

a remote service made
available through a user
authentication.

Type: INFO:NIDP:WSF:005

Scenario: A Web Service request was made to query
user attributes. One of the data locations specified for
the service is the Liberty User Profile object. That object
was successfully accessed but did not contain the
requested data.

Type: INFO:NIDP:WSF:006

Scenario: When a user authenticates, the
authentication entity can push user attributes to the
NIDP as part of the response to the authentication. The
NIDP remembers these attributes for the life of that user
session. If one of the data locations specified for a Web
Service is remote, then these attributes may be
returned as part of a query.

See Also: 600102005

Type: INFO:NIDP:WSF:007

Scenario: A request was made to query a user's
attributes. One of the data locations for the Web Service
was remote. So, a request was made to a remote
service to read attributes.

See Also: 600102006

500102008 Completed building composite

data that was read from all
data locations for user.

500102009 Initiating a user interaction

redirect.

500102010 Initiating a user interaction call

to a trusted user interaction
service.

Type: INFO:NIDP:WSF:008

Scenario: A request was made to query a user's
attributes. If multiple data locations are specified for the
Web Service, then attributes may be read from multiple
data locations and then aggregated into a composite
data structure.

See Also: 600102007

Type: INFO:NIDP:WSF:009

Scenario: A request was made to query or modify user's
attributes. Policy indicates that the user must be asked
if the attribute operation is permitted. The request
indicated that a redirect user interaction service should
be used to perform user interaction, so redirection is
being invoked using the redirection user interaction
service protocol.

Type: INFO:NIDP:WSF:010

Scenario: A request was made to query or modify user's
attributes. Policy indicates that the user must be asked
if the attribute operation is permitted. 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.

82 Novell Access Manager 3.1 SP1 Event Codes

Event Code Message Remedy

novdocx (en) 13 May 2009

500102011 Read Credential Profile data

from Novell Secret Store.

500102012 Read Credential Profile data

from an extended user
authentication object attribute.

500102013 Web service data write denied

because the LDAP attribute
plugin access for the named
data item is read only!

500102014 Override not allowed. Cannot

override existing data.

500102015 Existing data changed since

notChangedSince time.

Type: INFO:NIDP:WSF:011

Scenario: A request was made to query data from a
user's Credential Profile. The data was successfully
read.

See Also: 600102008

Type: INFO:NIDP:WSF:012

Scenario: A request was made to query data from a
user's Credential Profile. The data was read from an
extended schema attribute on the user's authenticated
user object.

See Also: 600102010

Type: INFO:NIDP:WSF:013

Scenario: The system administrator has marked this
data item as read only in the LDAP Attribute Plugin.

Type: INFO:NIDP:WSF:014

Scenario: The data that is being written already exists in
the user's profile. Data override is not allowed so this
data cannot be written.

Type: INFO:NIDP:WSF:015

Scenario: User profile data is marked with the last time
the data changed. The query request indicated that it
did not want the data written if the current data in the
profile has been changed since an indicated time. The
system determined that the current data in the profile
has been changed since the time provided, so this data
cannot be written.

500103001 Filled the user attribute

request from data already in
the web service consumer
cache.

500103002 Web service consumer

request complete.

500103003 Web service consumer

request requires user
interaction.

Type: INFO:NIDP:WSC:001

Scenario: When the WSC reads user attributes, it
caches the results of each read. In this case, a
subsequent request queried attributes already read, so
they were provided from the WSC cache.

Type: INFO:NIDP:WSC:002

Scenario: The WSC was asked to query or modify data
for a given user. That request is complete.

Type: INFO:NIDP:WSC:003

Scenario: The WSC was asked to query or modify data
for a given user. The entity called to perform the
operation indicated that the user must be asked if the
attribute operation is acceptable.

Identity Server (001) 83

Event Code Message Remedy

novdocx (en) 13 May 2009

500103004 User interaction policy and

data values received.

500104002 Getting properties from file

(informational)

500104007 X509 Authentication matched

principal (informational)

500104013 No CRL/OCSP defined by the

administrator

500104014 No CRL/OCSP found in the

certificate.

500104016 Could not fetch CRL from the

local cache (informational)

Type: INFO:NIDP:WSC:004

Scenario: A Web Service request was made to query or
modify user attributes. It was determined that the user
must be asked if the attribute operation is acceptable.
The user's answers have been returned to the NIDP.

Type: INFO:NIDP:USERAUTH:002

Scenario: Getting properties from file

Type: INFO:NIDP:USERAUTH:007

Scenario: X509 Authentication matched principal

Type: INFO:NIDP:USERAUTH:013

Cause: No CRL/OCSP defined by the administrator

Type: INFO:NIDP:USERAUTH:014

Cause: No CRL/OCSP found in the certificate

Action: CRL/OCSP validations are enabled but no

CRL/OCSP responder URL was defined by the
administrator. CRL/OCSP URLs may be defined if
needed.

Type: INFO:NIDP:USERAUTH:016

Scenario: Could not fetch CRL from the local cache,
getting it from the CDP

500104048 Successfully loaded NIDP

PKIX Certificate Path Checker
Class (informational)

500104113 Kerberos Principal match

found in the user store
(informational)

500105001 Forwarding HTTP request to

cluster member.

500105002 Successfully initialized JNDI

connections.

Type: INFO:NIDP:USERAUTH:048

Scenario: Successfully loaded NIDP PKIX Certificate
Path Checker Class

Type: INFO:NIDP:USERAUTH:113

Scenario: Kerberos Principal found in the user store

Type: INFO:NIDP:APP:001

Scenario: A request was received on a cluster member
that does not own the authentication information for the
associated user. The request must be processed on the
cluster member that does own the user authentication
information, so the request is being forwarded to that
cluster member.

Type: INFO:NIDP:APP:002

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.

84 Novell Access Manager 3.1 SP1 Event Codes

Event Code Message Remedy

novdocx (en) 13 May 2009

500105003 Failed X509 authentication

due to Login Policy Check
Extension Method evaluation.

500105004 An recoverable error

happened while forwarding a
login request.

500105005 Type: INFO:NIDP:APP:005

500105006 Type: INFO:NIDP:APP:006

500105007 Type: INFO:NIDP:APP:007

500105008 Type: INFO:NIDP:APP:008

500105009 Type: INFO:NIDP:APP:009

500105010 Type: INFO:NIDP:APP:010

500105011 Type: INFO:NIDP:APP:011

500105012 Type: INFO:NIDP:APP:012

500105013 Type: INFO:NIDP:APP:013

Type: INFO:NIDP:APP:003

Scenario: The directory login policy for the indicated
user denied login.

Type: INFO:NIDP:APP:004

Scenario: The request landed on the wrong cluster
member. An attempt was made to proxy the request,
but an error occurred! However, this ESP can process
this request, so let execution proceed on this box.

500105014 Type: INFO:NIDP:APP:014

500105015 Type: INFO:NIDP:APP:015

500105016 Type: INFO:NIDP:APP:016

500105017 Type: INFO:NIDP:APP:017

500105018 Type: INFO:NIDP:APP:018

500105019 Type: INFO:NIDP:APP:019

500105020 Type: INFO:NIDP:APP:020

500105021 Type: INFO:NIDP:APP:021

500105022 Type: INFO:NIDP:APP:022

500105023 Type: INFO:NIDP:APP:023

500105024 Type: INFO:NIDP:APP:024

500105025 Type: INFO:NIDP:APP:025

500105026 Type: INFO:NIDP:APP:026

500105027 Type: INFO:NIDP:APP:027

500105028 Type: INFO:NIDP:APP:028

500105029 Type: INFO:NIDP:APP:029

500105030 Type: INFO:NIDP:APP:030

Identity Server (001) 85

Event Code Message Remedy

500105031 Type: INFO:NIDP:APP:031

500105032 Type: INFO:NIDP:APP:032

500105033 Type: INFO:NIDP:APP:033

500105034 Type: INFO:NIDP:APP:034

500105035 Type: INFO:NIDP:APP:035

500105036 Type: INFO:NIDP:APP:036

500105037 Type: INFO:NIDP:APP:037

500105038 Type: INFO:NIDP:APP:038

500105039 Type: INFO:NIDP:APP:039

500105040 Type: INFO:NIDP:APP:040

500105041 Type: INFO:NIDP:APP:041

novdocx (en) 13 May 2009

500105042 Type: INFO:NIDP:APP:042

500105043 Type: INFO:NIDP:APP:043

500105044 Type: INFO:NIDP:APP:044

500105045 Type: INFO:NIDP:APP:045

500105046 The specified identity object

was deleted because it was
not used for a configurable
time period.

500106001 Type: INFO:NIDP:IDFF:001

500106002 Type: INFO:NIDP:IDFF:002

500106003 Type: INFO:NIDP:IDFF:003

500106004 Type: INFO:NIDP:IDFF:004

500106005 Type: INFO:NIDP:IDFF:005

500106006 Type: INFO:NIDP:IDFF:006

500106007 Type: INFO:NIDP:IDFF:007

Type: INFO:NIDP:APP:046

Scenario: Periodically, the IDP attempts to clean up
(delete) identity objects that have not been used for a
configurable period of time. If an old unused identity is
found, an attempt will be made to delete it. When this
delete succeeds, this message will be logged.

500106008 Type: INFO:NIDP:IDFF:008

600102001 Verbose user authentication

information.

86 Novell Access Manager 3.1 SP1 Event Codes

Type: DEBUG:NIDP:WSF:001

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

Event Code Message Remedy

novdocx (en) 13 May 2009

600102002 Verbose user authentication

information, attribute select
string, and data.

600102003 Read single-valued attribute

from user authentication
LDAP object.

600102004 Read multi-valued attribute

from user authentication
LDAP object.

600102005 Verbose user authentication

and attribute information.

Type: DEBUG:NIDP:WSF:002

Scenario: A Web Service request was made to query
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.

See Also: 500102004

Type: DEBUG:NIDP:WSF:003

Scenario: A Web Service request to query user attribute
data was received. One of the data locations was LDAP.
This message displays the value read from the
indicated LDAP attribute for the indicated user.

Type: DEBUG:NIDP:WSF:004

Scenario: A Web Service request to query user attribute
data was received. One of the data locations was LDAP.
This message displays the value read from the
indicated LDAP attribute for the indicated user.

Type: DEBUG:NIDP:WSF:005

Scenario: When a user authenticates, the
authenticating entity can push user attributes to the
NIDP as part of the response to the authentication. The
NIDP remembers these attributes for the life of that user
session. If one of the data locations specified for a Web
Service is remote, then these attributes may be
returned as part of a query.

600102006 Adds verbose user and

attribute information to
attributes read from a remote
service whose description
was obtained at
authentication time.

600102007 Adds verbose user and

attribute information to the
final aggregated result of a
web service query!

See Also: 500102006

Type: DEBUG:NIDP:WSF:006

Scenario: A request was made to query a user's
attributes. One of the data locations for the Web Service
was remote. So, a request was made to a remote
service to read attributes.

See Also: 500102007

Type: DEBUG:NIDP:WSF:007

Scenario: A request was made to query a user's
attributes. If multiple data locations are specified for the
Web Service, then attributes may be read from multiple
data locations and then aggregated into a composite
data structure.

See Also: 500102008

Identity Server (001) 87

Event Code Message Remedy

novdocx (en) 13 May 2009

600102008 Adds verbose data to reading

Credential Profile data from
Novell Secret Store.

600102009 The user successfully logged

into Novell Secret Store using
SAML/SASL.

600102010 Adds verbose data to reading

Credential Profile data from
an extended user
authentication object attribute.

600105001 Do not need to proxy HTTP

request to other cluster
member. Well known URL
that does not require the use
of a proxy.

600105002 Do not need to proxy HTTP

request to other cluster
member. This cluster member
can handle requests for this
user.

Type: DEBUG:NIDP:WSF:008

Scenario: A request was made to query data from a
user's Credential Profile. The data was successfully
read.

See Also: 500102011

Type: DEBUG:NIDP:WSF:009

Scenario: To access secrets from Novell Secret Store,
the user must authenticate to Novell Secret Store.

Type: DEBUG:NIDP:WSF:010

Scenario: A request was made to query data from a
user's Credential Profile. The data was read from an
extended schema attribute on the user's authenticated
user object.

See Also: 500102012

Type: DEBUG:NIDP:APP:001

Scenario: The request is one of a well known list of
request types that may be processed on any cluster
member, so it does not need to be forwarded to another
cluster member.

Type: DEBUG:NIDP:APP:002

Scenario: The request arrived at the cluster member
that owns the authentication information for the user.
The request may have come straight from the router to
this cluster member, or the request may have been
forwarded here by another cluster member.

600105003 Obtained IP address of cluster

member handling this users
requests from URL parameter.

600105004 Obtained IP address of cluster

member handling this users
requests from HTTP cookie.

600105005 Obtained IP address of cluster

member handling this user's
requests by asking cluster
members which one handles
this user session.

88 Novell Access Manager 3.1 SP1 Event Codes

Type: DEBUG:NIDP:APP:003

Scenario: Each request must be processed on the
cluster member that owns the user authentication
information. The IP address of that cluster member was
found in a URL parameter.

Type: DEBUG:NIDP:APP:004

Scenario: Each request must be processed on the
cluster member that owns the user authentication
information. The IP address of that cluster member was
found in an HTTP cookie.

Type: DEBUG:NIDP:APP:005

Scenario: Each request must be processed on the
cluster member that owns the user authentication
information. The IP address of that cluster member was
found by asking all cluster members which one knew
about the user's session.

Event Code Message Remedy

novdocx (en) 13 May 2009

600105006 Must proxy HTTP request to

other cluster member.

600105007 Response of proxy HTTP

request.

600105008 Successfully obtained SOAP

response document.

600105009 Type:DEBUG:NIDP:APP:009

600105010 Type: DEBUG:NIDP:APP:010

Type: DEBUG:NIDP:APP:006

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.

Type: DEBUG:NIDP:APP:007

Scenario: Each request must be processed on the
cluster member that owns the user authentication
information. It was determined that this cluster member
is not the correct cluster member to process this
request, so the request was forwarded to another
cluster member. The results of the request, as
processed on the other cluster member, are displayed
here.

Type: DEBUG:NIDP:APP:008

Scenario: A SOAP request was made and a response
was expected, the response was successfully obtained.

600105011 Type: DEBUG:NIDP:APP:011

Identity Server (001) 89

novdocx (en) 13 May 2009

90 Novell Access Manager 3.1 SP1 Event Codes

4

Linux Access Gateway

novdocx (en) 13 May 2009

Appliance(045)

Component 045

Event Code Description Remedy

[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

for a description of the cause.

[1-9]04504000 Authentication processing See the string value in the message

for a description of the cause.

[1-9]04505000 Authorization processing See the string value in the message

for a description of the cause.

[1-9]04506000 Identity Injection processing See the string value in the message

for a description of the cause.

[1-9]04507000 Form Fill processing See the string value in the message

for a description of the cause.

4

[1-9]04508000 Caching See the string value in the message

for a description of the cause.

[1-9]04509000 Processing of Web server responses and of

responses to browser requests

[1-9]04511000 Rewriter processing See the string value in the message

[1-9]04512000 SOAP back channel processing See the string value in the message

[1-9]04513000 Device communication channel (VCC) See the string value in the message

[1-9]04514000 VM controller processing See the string value in the message

[1-9]04515000 Connection management See the string value in the message

[1-9]04516000 Core utilities (VXE) See the string value in the message

[1-9]04517000 Data Stream processing See the string value in the message

[1-9]04518000 SSL processing See the string value in the message

See the string value in the message
for a description of the cause.

for a description of the cause.

for a description of the cause.

for a description of the cause.

for a description of the cause.

for a description of the cause.

for a description of the cause.

for a description of the cause.

for a description of the cause.

Linux Access Gateway Appliance(045)

91

Event Code Description Remedy

[1-9]04519000 Command processing See the string value in the message

for a description of the cause.

[1-9]04520000 Profiler See the string value in the message

for a description of the cause.

[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.

novdocx (en) 13 May 2009

92 Novell Access Manager 3.1 SP1 Event Codes

5

SSL VPN Server (005)

Component 005

 Subgroup 01: Server

 Subgroup 02: Client. For a description of these event codes, see “Error Messages” in the Novell

Access Manager 3.1 SSL VPN User Guide.

Event Code Description Remedy

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

novdocx (en) 13 May 2009

5

20050101201 Error spawning stunnel Cause: The

stunnel

executable or corrupted

Action: Check if the binary is present and has
correct permissions. Installation may be a
problem

20050101202 Server stunnel conf file could not be

opened

20050101203 Server sockd conf file could not be

opened

20050101204 Could not find core config file Cause: The

Cause: The

stunnel.conf

present

Action: Configuration may be bad. Check for
other configuration errors in the logs

Cause: The

sockd.conf

present

Action: Configuration may be bad. Check for
other configuration errors in the logs

config.xml

Action: Restart the sslvpn service. Apply the
changes from device manager and observe
for any other errors while applying the
changes on the device

file may not be present, or not

/opt/novell/sslvpn/bin/

/etc/opt/novell/sslvpn/

file may be corrupted or not

/etc/opt/novell/sslvpn/

file may be corrupted or not

/etc/opt/novell/sslvpn/

file is not present or corrupted

SSL VPN Server (005)

93

Event Code Description Remedy

novdocx (en) 13 May 2009

40050101205 Configuration file does not have

proper contents. Parsing configuration
failed. Connection Manager has bad
configuration data. Could not add new
connection

20050101206 Resource allocation failed Cause: Might be a potential issue

20050101207 Failed to send stunnel response

“1231” to fd “5”

20050101208 Could not open the file “/opt/novell/

sslvpn/connmansocket” exiting! Could
not get File Lock for ConnMan.
Another instance may be already
running

20050101209 Could not open the Unix domain

socket

Cause: The

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

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

connmansocket

by another instance

Action: Forcefully delete this file and restart
sslvpn service

Cause: The

connman

/etc/opt/novell/sslvpn/

file is not properly formatted.

/opt/novell/sslvpn/

file may have been locked

/opt/novell/sslvpn/

file may have been locked

4005010120A Could not bind the Local socket. TCP

socket could not be opened

4005010120B VCC has not been started. May be

VCC port is invalid

2005010120C Failed to parse Stunnel certificate.

error code = XXXX

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

sslvpn/config.xml

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

restart

Cause: Stunnel Certificate is in bad format

Action: Recreate the Stunnel certificate in

device manager and apply changes to the
device

/etc/opt/novell/

file and verify the

/etc/init.d/novell-jcc

command.

94 Novell Access Manager 3.1 SP1 Event Codes

Event Code Description Remedy

novdocx (en) 13 May 2009

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

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

50050101400 Failed to connect to connection

Manager

20050101401 Error in sending message to

Connection Manager

20050101402 Error in receiving message Cause: May be connection socket would

20050101403 Failed to get the lock of the connection

Manager socket. Service cannot be
stopped

20050101404 Failed to update SSLVPN Server

Configuration

Cause: Connection manager may not be
running

Action: Start the connection using the

sslvpnc –up

Cause: Connection Manager socket would
have closed

Action: Make sure connection Manager
running

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
correct and well formed

command.

config.xml

config.xml

is

is

SSL VPN Server (005) 95

Event Code Description Remedy

50050101405 Too many arguments Cause: User entered the more arguments

than the command can use.

novdocx (en) 13 May 2009

Action: Type
command syntax, and use it.

50050101406 Too few arguments Cause: User entered fewer arguments than

the command requires.

Action: Type
command syntax, and use it.

50050101407 Invalid command Cause: User entered the wrong command

Action: Type
command syntax, and use it.

30050101408 Failed to start SSL VPN service.

Check log(/var/log/messages)

50050101409 Invalid argument Cause: The user has entered invalid

Cause: The
invalid.

Action: Check the
correct it.

arguments.

Action: Use the
to discover the valid arguments.

sslvpn –help

sslvpn –help

sslvpn –help

config.xml

config.xml

sslvpnc –help

, read the

, read the

, read the

file is probably

file and

command

96 Novell Access Manager 3.1 SP1 Event Codes

6

J2EE Agents (006)

Component 006

 Subgroup 01: Management

 Subgroup 02: Authentication (JAAS)

 Subgroup 03: Authorization (JACC)

 Subgroup 99: Policy PEP

Event Code Message Remedy

novdocx (en) 13 May 2009

6

100601001 Could not find initial XML configuration in

classPath

100601002 Could not add agent specific information

to initial configuration

100601003 Configuration of agent failed Cause: Invalid configuration was sent to the

100601004 Could not create an LDAP connection Cause: LDAP connection failed due to: 1)

100601005 Could not read JCC id file Cause: File rights to the JCC ID file are denied.

Cause: An initial XML configuration should
exists in the
doesn’t when this error occurs.

Action: Verify that Agent files are in the proper
place.

Cause: Unexpected XML error, possibly from
faulty XML libraries.

Action: Submit requested logs and data.

agent.

Action: Submit requested logs and data.

Network Outage, 2) DNS configuration, 3) port
configurations, 4) Firewall configurations, etc.

Action: Verify that the management server can
be contacted.

Action: Verify that the JCC ID file (named

JBoss.id

the application server has read access to the
file.

NidsCommonAgent.jar

or

WebSphere.id)

but

is present and

100601006 Could not write to JCC id file Cause: File creation rights to the

are denied to the application server.

Action: Verify that the JCC ID file (named

JBoss.id

the application server has write access to the
file.

100601007 Could not log configuration Cause: Missing or outdated log jar files.

Action: Check that logging utilities are present

or

WebSphere.id

jcc

directory

) is present and

J2EE Agents (006)

97

Event Code Message Remedy

100601008 Could not determine Agent Type Cause: Agent Type property not set and/or

JACC not configured properly.

Action: Verify that these properties are set.

novdocx (en) 13 May 2009

100602000 A Severe error occurred in the

authentication module (JAAS)

100602001 The identity server returned a null or

empty user name

100602002 Returned -503 due to unconfigured

identityServerBaseURL

Cause: The session might have timed out.

Action: Submit requested logs/data.

Cause: The session might have timed out.

Action: Retry

Cause: The application server URL has not

been configured.

Action: Configure the agent to have the
correct base URL

100602003 Couldn't configure SAX parser Cause: Something is wrong with the Java

environment, or the XML libraries are not
configured.

Action: Obtain latest XML libraries from
apache.org and put them into the classpath.

100602004 Couldn't communicate with the identity

server due to a null URL for the server

Cause: No trusted identity server is configured.

Action: Configure the agent to have a trusted

Identity Server.

100602005 Couldn't open an URL connection to the

Cause: Invalid or missing application URL.

embedded server provider

Action: Configure the agent to have a valid
application URL. Restart the agent or
application server where the agent resides.

100602006 Couldn't read response from the identity

server

100602007 Couldn't parse the XML document from

the identity server

100602008 Could not build the WebSphere principal

and credential

100602009 WebSphere is not configured with global

and server security

98 Novell Access Manager 3.1 SP1 Event Codes

Cause: Connection might have been

interrupted.

Action: Retry, verify network connectivity, DNS
resolution, etc.

Cause: Unexpected response from the Identity
Server

Action: Submit requested logs/data.

Cause: Unexpected error in WebSphere

Action: Submit requested logs/data.

Cause: WebSphere does not have global

security enabled.

Action: Enable WebSphere for global and
server security.

Event Code Message Remedy

novdocx (en) 13 May 2009

100602010 Could not parse system property

'com.novell.nids.agent.sessionVerification
Minutes'

100602011 AuthSessionCache cleanup thread

existing

100602012 An error was encountered in reflection

code to get moduleID from
HttpServletRequest

100602013 An Error occurred decoding a soap

response

500602001 Event occurred: Agent sent a redirect to

nesp

500602002 Event occurred: Login Servlet received

login from nesp

500602003 Event occurred: Verifying nidsID

Cause: This property is set to override the
default time of 5 minutes. The set value for this
property was not a valid Integer and could not
be parsed.

Action: Check the system property
com.novell.nids.agent.sessionVerificationMinut
es has a valid number.

Cause: The session cache cleanup threat was
terminated.

Action: Check logs to see if other events may
have caused this. Send logs to support.

Cause: WebLogic API has been changed.

Action: Contact Novell Support.

Cause: Java is corrupt and does not support

UTF-8

500602004 Event occurred: Contacted esp for

session and attributes

500602005 Event occurred: esp session successfully

verified, posting login

500602006 Event occurred: LoginModule received

login

500602007 Event occurred: LoginModule

successfully logged in the user

500603008 Event occurred: JACC called for

permission

500603009 Event occurred: JACC decision:

permission allowed

500603010 Event occurred: JACC decision:

permission denied

100603001 Failed to construct the policy enforcement

points

Cause: An erroneous policy may have been
sent from the management console.

Action: Search for errors from the 099
subcomponent.

J2EE Agents (006) 99

Event Code Message Remedy

novdocx (en) 13 May 2009

100603002 An error was encountered during policy

evaluation

100603003 Could not obtain a request object during

policy evaluation

100603004 Exception occurred persisting policies/

roles to file

200601000 A Warning message occurred in the

management of the agent

200602000 A Warning message occurred in the

authentication module (JAAS)

Cause: An erroneous policy may have been
sent from the management console.

Action: Search for errors from the 099
subcomponent.

Cause: Unexpected error occurred evaluating
a policy.

Action: Submit requested logs/data. Search
for errors from the 099 subcomponent.

Cause: File rights denied access to read/write
policy and roles file in WebSphere.

Action: Verify that the file exists and can be
written to by the application server.

Cause: A Warning message might indicate
incorrect configuration.

Action: If condition persists, submit requested
logs/data.

Cause: A Warning message might indicate
incorrect configuration.

Action: If condition persists, submit requested
logs/data.

200603000 A Warning message occurred in the

authorization module (JACC)

300601000 Generic trace/debug message from agent

management

030060200 Generic trace/debug message from

authentication module (JAAS)

300603000 Generic trace/debug message from

authorization module (JACC)

200699002 Invalid input data. Invalid data has been

received which prevents policy from being
evaluated.

Cause: A Warning message might indicate
incorrect configuration.

Action: Submit requested logs/data.

Action: A trace/debug message does not

indicate failure or misconfiguration, but it might
help diagnosing a problem.

Action: A trace/debug message does not
indicate failure or misconfiguration, but it might
help diagnosing a problem.

Action: A trace/debug message does not
indicate failure or misconfiguration, but it might
help diagnosing a problem.

Action: See supplementary messages in logs
for indication of specific problem.

100 Novell Access Manager 3.1 SP1 Event Codes