The following table describes the error codes generated by the amadmin command line tool to Access Manager’s debug file.
Table D–4 amadmin error codes
Error Message |
Code |
Description/Probable Cause |
Action |
---|---|---|---|
nocomptype |
1 |
Too few arguments. |
Make sure that the mandatory arguments (--runasdn, --password, --passwordfile, --schema, --data, and --addAttributes) and their values are supplied in the command line. |
file |
2 |
The input XML file was not found. |
Check the syntax and make sure that the input XML is valid. |
nodnforadmin |
3 |
The user DN for the --runasdn value is missing. |
Provide the user DN as the value for --runasdn. |
noservicename |
4 |
The service name for the --deletservice value is missing. |
Provide the service name as the value for --deleteservice. |
nopwdforadmin |
5 |
The password for the --password value is missing. |
Provide the password as the value for --password. |
nolocalename |
6 |
The locale name was not provided. The locale will default to en_US. |
See the Online Help for a list of locales. |
nofile |
7 |
Missing XML input file. |
Provide at least one input XML filename to process. |
invopt |
8 |
One or more arguments are incorrect. |
Check that all arguments are valid. For a set of valid arguments, type amadmin --help. |
oprfailed |
9 |
Operation failed. |
When amadmin fails, it produces more precise error codes to indicate the specific error. Refer to those error codes to evaluate the problem. |
execfailed |
10 |
Cannot process requests. |
When amadmin fails, it produces more precise error codes to indicate the specific error. Refer to those error codes to evaluate the problem. |
policycreatexception |
12 |
Policy cannot be created. |
amadmin produces exception messages to indicate the specific error. Refer to those messages to evaluate the problem. |
policydelexception |
13 |
Policy cannot be deleted. |
amadmin produces exception messages to indicate the specific error. Refer to those messages to evaluate the problem. |
smsdelexception |
14 |
Service cannot be deleted. |
amadmin produces exception messages to indicate the specific error. Refer to those messages to evaluate the problem. |
ldapauthfail |
15 |
Cannot authenticate user. |
Make sure the user DN and password are correct. |
parserror |
16 |
Cannot parse the input XML file. |
Make sure that the XML is formatted correctly and adheres to the amAdmin.dtd . |
parseiniterror |
17 |
Cannot parse due to an application error or a parser initialization error. |
Make sure that the XML is formatted correctly and adheres to the amAdmin.dtd . |
parsebuilterror |
18 |
Cannot parse because a parser with specified options cannot be built. |
amadmin produces exception messages to indicate the specific error. Refer to those messages to evaluate the problem. |
ioexception |
19 |
Cannot read the input XML file. |
amadmin produces exception messages to indicate the specific error. Refer to those messages to evaluate the problem. |
fatalvalidationerror |
20 |
Cannot parse because the XML file is not a valid file. |
Check the syntax and make sure that the input XML is valid. |
nonfatalvalidationerror |
21 |
Cannot parse because the XML file is not a valid file. |
amadmin produces exception messages to indicate the specific error. Refer to those messages to evaluate the problem. |
validwarn |
22 |
XML file validation warnings for the file. |
amadmin produces exception messages to indicate the specific error. Refer to those messages to evaluate the problem. |
failedToProcessXML |
23 |
Cannot process the XML file. |
amadmin produces exception messages to indicate the specific error. Refer to those messages to evaluate the problem. |
nodataschemawarning |
24 |
Neither --data or --schema options are in the command. |
Check that all arguments are valid. For a set of valid arguments, type amadmin --help. |
doctyperror |
25 |
The XML file does not follow the correct DTD. |
Check the XML file for the DOCTYPE element. |
statusmsg9 |
26 |
LDAP Authentication failed due to invalid DN, password, hostname, or portnumber. |
Make sure the user DN and password are correct. |
statusmsg13 |
28 |
Service Manager exception (SSO exception). |
amadmin produces exception messages to indicate the specific error. Refer to those messages to evaluate the problem. |
statusmsg14 |
29 |
Service Manager exception. |
amadmin produces exception messages to indicate the specific error. Refer to those messages to evaluate the problem. |
statusmsg15 |
30 |
Schema file inputstream exception. |
amadmin produces exception messages to indicate the specific error. Refer to those messages to evaluate the problem. |
statusmsg30 |
31 |
Policy Manager exception (SSO exception). |
amadmin produces exception messages to indicate the specific error. Refer to those messages to evaluate the problem. |
statusmsg31 |
32 |
Policy Manager exception. |
amadmin produces exception messages to indicate the specific error. Refer to those messages to evaluate the problem. |
dbugerror |
33 |
More than one debug option is specified. |
Only one debug option should be specified. |
loginFalied |
34 |
Login failed. |
amadmin produces exception messages to indicate the specific error. Refer to those messages to evaluate the problem. |
levelerr |
36 |
Invalid attribute value. |
Check the level set for the LDAP search. It should be either SCOPE_SUB or SCOPE_ONE. |
failToGetObjType |
37 |
Error in getting object type. |
Make sure that the DN in the XML file is value and contains the correct object type. |
invalidOrgDN |
38 |
Invalid organization DN. |
Make sure that the DN in the XML file is valid and is an organization object. |
invalidRoleDN |
39 |
Invalid role DN. |
Make sure that the DN in the XML file is valid and is a role object. |
invalidStaticGroupDN |
40 |
Invalid static group DN. |
Make sure that the DN in the XML file is valid and is a static group object. |
invalidPeopleContainerDN |
41 |
Invalid people container DN. |
Make sure the DN in the XML file is valid and is a people container object. |
invalidOrgUnitDN |
42 |
Invalid organizational unit DN. |
Make sure that the DN in the XML file is valid and is a container object. |
invalidServiceHostName |
43 |
Invalid service host name. |
Make sure that the hostname for retrieving valid sessions is correct. |
subschemaexception |
44 |
Subschema error. |
Subcschema is only supported for global and organization attributes. |
serviceschemaexception |
45 |
Cannot locate service schema for service. |
Make sure that the sub schema in the XML file is valid. |
roletemplateexception |
46 |
The role template can be true only if the schema type is dynamic. |
Make sure that the role template in the XML file is valid. |
cannotAddusersToFileredRole |
47 |
Cannot add users to a filtered role. |
Made sure that the role DN in the XML file is not a filtered role. |
templateDoesNotExist |
48 |
Template does not exist. |
Make sure that the service template in the XML file is valid. |
cannotAdduUersToDynamicGroup |
49 |
Cannot add users to a dynamic group. |
Made sure that the group DN in the XML file is not a dynamic group. |
cannotCreatePolicyUnderContainer |
50 |
Policies can not be created in an organization that is a child organization of a container. |
Make sure that the organization in which the policy is to be created is not a child of a container. |
defaultGroupContainerNotFound |
51 |
The group container was not found. |
Create a group container for the parent organization or container. |
cannotRemoveUserFromFilteredRole |
52 |
Cannot remove a user from a filtered role. |
Make sure that the role DN in the XML file is not filtered role. |
cannotRemoveUsersFromDynamicGroup |
53 |
Cannot remove users from a dynamic group. |
Make sure that the group DN in the XML file is not a dynamic group. |
subSchemStringDoesNotExist |
54 |
The subschema string does not exist. |
Make sure that the subschema string exists in the XML file. |
defaultPeopleContainerNotFound |
59 |
You are trying to add user to an organization or container. And default people container does not exists in an organization or container. |
Make sure the default people container exists. |
nodefaulturlprefix |
60 |
Default URL prefix is not found following --defaultURLPrefix argument |
provide the default URL prefix accordingly. |
nometaalias |
61 |
Meta Alias is not found following --metaalias argument |
provide the Meta Alias accordingly. |
missingEntityName |
62 |
Entity Name is not specified. |
provide the entity name. |
missingLibertyMetaInputFile |
63 |
File name for importing meta data is missing. |
provide the file name that contains meta data. |
missingLibertyMetaOutputFile |
64 |
File name for storing exported meta data is missing. |
provide the file name for storing meta data. |
cannotObtainMetaHandler |
65 |
Unable to get a handler to Meta attribute. Specified user name and password may be incorrect. |
ensure that user name and password are correct. |
missingResourceBundleName |
66 |
Missing resource bundle name when adding, viewing or deleting resource bundle that is store in directory server. |
provide the resource bundle name |
missingResourceFileName |
67 |
Missing file name of file that contains the resource strings when adding resource bundle to directory server. |
Please provide a valid file name. |
failLoadLibertyMeta |
68 |
Failed to load liberty meta to Directory Server. |
Please check the meta data again before loading it again |