ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaef_5.4.0.1/rzaefusrerrcod.htm

199 lines
10 KiB
HTML

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="dc.language" scheme="rfc1766" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<meta name="dc.date" scheme="iso8601" content="2005-09-06" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2000, 2006" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow"/>
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="keywords" content="user enrollment errors, message" />
<title>User enrollment error codes</title>
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
<link rel="stylesheet" type="text/css" href="ic.css" />
</head>
<body>
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
<a name="usrerrcod"></a>
<h3 id="usrerrcod">User enrollment error codes</h3><a id="idx284" name="idx284"></a>
<p>If an error code appears, use option 16 to view the error message that
is associated with the error code. Although the message text associated with
the error appears, substitution text, such as the server name, does not. However,
when the message goes to the QNETWARE job log, the substitution text does appear.</p>
<p>Some error codes have a one-to-one relationship with an associated error
message. Many of the NetWare-specific messages, however, show only the NetWare error
code, then a generic message that indicates an error occurred while calling
a NetWare function. In this case, the error message has some explanatory text
for some of the common NetWare errors. Not all errors, however, are described
in the message text.</p>
<p>These error codes might appear: </p>
<dl>
<dt class="bold">Negative error code</dt>
<dd>These error codes generally indicate some sort of communication error
while trying to send requests to a NetWare server. Generally, only the final
error appears. If you know that a server is inactive, this probably explains
the error. If you think that a server is running properly, look in the <a href="rzaefjoblogs.htm#joblogs">QNETWARE job log</a> for related error messages that might
help isolate the problem.
</dd>
<dt class="bold">0-999</dt>
<dd>Error codes returned from NetWare function calls.
<dl>
<dt class="bold">216</dt>
<dd>The password is too short. Change the password on iSeries&trade; to a longer
value.
</dd>
<dt class="bold">220</dt>
<dd>The account is disabled. Re-enable the QNETWARE profile on the NDS tree.
</dd>
<dt class="bold">238</dt>
<dd>Another object already exists with the same name as the profile that
you are propagating. Either end propagation of the profile from the iSeries side, or
rename the matching object from a NetWare client.
</dd>
<dt class="bold">242-254</dt>
<dd>The QNETWARE profile on the NDS tree does not have sufficient access
rights to make the necessary user or group object changes. From a NetWare client,
make sure that the QNETWARE profile has the authority to process user and group
objects. You can do this by making the object an ADMIN user or the security
equivalent to an ADMIN user.
</dd>
<dt class="bold">333</dt>
<dd>Indicates that a connection failure has occurred. If this error occurs,
end the QNETWARE job. Then restart it by issuing a Retry entry option from the
WRKNWSENR status display for the failing profile.
</dd>
<dt class="bold">601</dt>
<dd>This normally indicates that you specified an incorrect NDS context.
Check for the profile in error by looking at the NDS context field of the
CHGNWSUSRA command. If you specified *NWSA in the CHGNWSUSRA command, check
the NDS context field in the CHGNWSA command.
</dd>
<dt class="bold">606</dt>
<dd>Another object already exists in the NDS tree with the same name as
the profile you are propagating. Either end propagation of the profile from
the iSeries side, or rename the matching object from a NetWare client.
</dd>
<dt class="bold">611</dt>
<dd>You specified an incorrect container name. Check the NDS context field
for the failing group or user profile.
</dd>
<dt class="bold">637</dt>
<dd>You are attempting an update or delete operation to a user or group
profile that has a move in progress. Typically this means that replication
of an NDS tree has not yet completed. If the operation changes to an *UPDFAIL
or *DLTFAIL status, use the Retry entry option on the WRKNWSENR status display
for the failing profile.
</dd>
<dt class="bold">654</dt>
<dd>A NetWare partition is busy. If the operation goes to a status of *UPDFAIL
or *DLTFAIL before the error clears, retry the operation. Use the Retry entry
option on the WRKNWSENR status display for the failing entry.
</dd>
<dt class="bold">668</dt>
<dd>You specified an incorrect container name. Check the NDS context
field for the failing group or user profile.
</dd>
<dt class="bold">669</dt>
<dd>The password is not correct.
</dd>
<dt class="bold">672</dt>
<dd>The QNETWARE profile on the NDS tree does not have sufficient access
rights to make object changes to the group or user. From a NetWare client, make
sure that the QNETWARE profile has the authority to process group and user objects.
Do this by making the object an ADMIN user or the security equivalent to an
ADMIN user.
</dd>
</dl>
</dd>
<dt class="bold">6000</dt>
<dd>Occurs when trying to send a request to an NDS tree. It indicates
that the context for the QNETWARE profile in the tree cannot be determined.
To correct the error, either use the ADDNTWAUTE command to <a href="rzaefauthenentry.htm#authenentry">create a NetWare authentication entry</a> for the QNETWARE profile in the tree,
or use the CHGNWSUSRA command to define such a context.
</dd>
<dt class="bold">6001</dt>
<dd>There is no QNETWARE profile on iSeries. Use the CRTUSRPRF command to create
the profile. This profile is automatically created when NetWare Enhanced Integration is installed,
but a system administrator might have deleted it.
</dd>
<dt class="bold">6002</dt>
<dd>An error occurred while trying to access the QNETWARE profile enrollment
information. The profile object is either locked by another job or damaged.
If the profile object is damaged, create the QNETWARE user profile again.
</dd>
<dt class="bold">6003</dt>
<dd>The user enrollment task could not contact the requested server in an NDS tree.
Either the servers are inactive, or they are not running the NetWare Enhanced Integration NLM. To
recover, start the inactive servers or load the NetWare Enhanced Integration NLM.
</dd>
<dt class="bold">6004</dt>
<dd>An authentication error occurred while trying to log in the QNETWARE user
to a server. Either the QNETWARE profile does not exist on the tree or server,
or the iSeries password information does not match that currently on the NetWare server
or NDS tree. Either change the iSeries password information to match the server,
or change the QNETWARE password from a NetWare utility such as NWADMIN.
</dd>
<dt class="bold">6005</dt>
<dd>An unexpected communication error occurred while trying to connect to
a NetWare server. Look in the QNETWARE job log for more detailed errors that might
help diagnose the problem.
</dd>
<dt class="bold">6006</dt>
<dd>An error occurred while trying to get the QNETWARE authentication information.
Use the ADDNTWAUTE command to add an authentication entry for the QNETWARE profile.
If one already exists, there may be some damage, so delete and re-create the QNETWARE profile.
</dd>
<dt class="bold">6007</dt>
<dd>An error occurred trying to retrieve user or group profile enrollment
information. Try the operation again. If the error persists, the profile may
be damaged. Either create the user profile again, or restore the profile from
a saved version.
</dd>
<dt class="bold">6008</dt>
<dd>An error occurred while trying to create an authentication entry for
an iSeries profile. Try the operation again. If the error persists, look
in the QNETWARE job log for any related errors that might indicate the source
of the problem.
</dd>
<dt class="bold">6009</dt>
<dd>An error occurred while trying to update the status of a profile on
a server. Try the operation again. If the problem persists, either delete
and then re-create the profile or restore the profile from a saved version.
</dd>
<dt class="bold">6011</dt>
<dd>No password is available for the user profile. This error occurs when
the QRETSVRSEC system value is set to 0, meaning that iSeries does not
keep security information. In this situation, passwords can only be retrieved
when the password is actually changed, or the user signs on to the system.
<p>For example, this error might occur if you create a new group profile
to enroll all the group members on a NetWare server. If the QRETSVRSEC system
value is set to 0, passwords for the group members are not immediately available,
so the 6011 error appears for all the group members. If one of them signs
on to iSeries, the system automatically captures the password information and
resolves the 6011 error. Until the user signs on, or the password is changed
using the CHGPWD or CHGUSRPRF command, this profile remains in a pending state.</p>
<p>This error can also occur if the user password has not changed since
you set the QRETSVRSEC system value to 1. To resolve the error, either have
the user sign on to iSeries, or change the password by using the CHGPWD or
CHGUSRPRF command.</p>
</dd>
<dt class="bold">6012</dt>
<dd>A profile update request was sent to a server, but no response was returned
within 10 minutes. The iSeries tries again. If the error persists for a particular
user, check the detailed error messages in the QNETWARE job log for more information.
</dd>
</dl>
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
</body>
</html>