Jorge 's Quest For Knowledge! : Troubleshooting MIIS (ILM) Related Error Codes

Saturday, October 25, 2008 5:31 PM Jorge

Troubleshooting MIIS (ILM) Related Error Codes

When working with MIIS, which is now called ILM Synchronization/Metadirectory Services and Object Provisioning, in relation to Imports, Exports or Synchronizations you might get errors. Some of the errors are easier to understand than others. Understanding the errors allows you to resolve the issue much faster (no rocket science here!). For that purpose I have published the available error codes in this post. At the bottom of the page I will publish the URL sources containing this information. Happy Troubleshooting!

CONNECTION RELATED ERRORS:

Error Value	Description
successful-connection	Successful connection to the connected directory.
failed-connection	Connection to the connected directory has failed for a reason other than authentication. Generally, the connected directory error element will be present to assist in troubleshooting.
dropped-connection	The connection between the management agent and the connected directory no longer exists. The management agent will try to reconnect to the connected directory in many cases. Generally, the connected directory error element will be present to assist in troubleshooting.
failed-authentication	Authentication is not possible using the supplied credentials.
failed-permission	Insufficient rights to access a container in the connected directory. This error is only expected for LDAP management agents which search different connected directory containers. Generally the connected directory error element will be present to assist in troubleshooting and the error literal will indicate the name of the container where the problem occurred.
failed-search	A container or table search failed with an unexpected error. Generally, the connected directory error element will be present to assist in troubleshooting and the error literal will indicate the name of the container it had trouble searching.
warning-no-watermark	The management agent cannot read the watermark when doing a full import. This error is only expected for the management agent for Sun ONE Directory Server 5.1 (formerly iPlanet Directory Server) when the initial management agent configuration was completed when the connected directory had change log enabled. Later when the connected directory change log is turned off, if the management agent configuration is not updated, this warning will occur when a full import is done.

DISCOVERY RELATED ERRORS:

Error Value		Description
missing-change-type		Returned during a delta import run by a file management agent, database management agent, or the management agent for Sun ONE Directory Server 4.1x and 5.x (formerly iPlanet Directory Server) and Netscape Directory Server 4.1 and 6.01 when the change type column value (for example, add, modify, delete) is not present.
invalid-change-type		Returned either during a LDIF full import, or during a delta import run by a file management agent, database management agent, or the management agent for Sun ONE Directory Server 4.1x and 5.x (formerly iPlanet Directory Server) and Netscape Directory Server 4.1 and 6.01 when the change type column value doesn't match the list of valid changes types.
multi-valued-change-type		Returned during a delta import run by a file management agent or the management agent for Sun ONE Directory Server 4.1x and 5.x (formerly iPlanet Directory Server) and Netscape Directory Server 4.1 and 6.01 when more than one value for the change type is present.
need-full-object		Returned during a delta import run of a file management agent or when resuming from a file management agent. It indicates the management agent has submitted a modification on an object which cannot be located in the connector space. The synchronization engine is requesting the current values of all attributes on the object. Since this is an import from a file, that information is not available. A full import run will take care of this problem.
missing-dn		Returned for file management agents (LDIF, DSML, or flat file with configured distinguished name attribute) when there is no distinguished name value. This is also returned in the case of a corrupted Sun ONE Directory Server 5.1 change log where the distinguished name attribute is missing. It indicates the management agent could read the element and parse it, but there was no distinguished name value for the object.
dn-not-ldap-conformant		Returned when a management agent for LDAP, LDIF, or DSML, or a flat file with a configured distinguished name attribute reports a distinguished name value that does not conform to the LDAP specification.
invalid-dn		Returned when an management agent reports that a distinguished name does not meet an Identity Integration Server constraint, which includes: One or more characters that are not allowed by Identity Integration Server An empty RDN An RDN exceeding the maximum for Identity Integration Server The number of hierarchy levels of the distinguished name exceeded the maximum for Identity Integration Server
missing-anchor-component		Returned by a file management agent, database management agent or iPlanet 4.0 management agent when the anchor could not be constructed because one or more anchor construction rule attributes did not have values.
multi-valued-anchor-component		Returned by the management agent for Sun ONE Directory Server 4.1x and 5.x (formerly iPlanet Directory Server) and Netscape Directory Server 4.1 and 6.01 indicating the management agent could not construct the anchor because an anchor construction rule attribute had more than one value.
anchor-too-long		Returned by the database management agent, files management agent or the management agent for Sun ONE Directory Server 4.1x and 5.x (formerly iPlanet Directory Server) and Netscape Directory Server 4.1 and 6.01 indicating the management agent anchor construction produced an anchor which exceeded the maximum size limit for Microsoft Identity Integration Server 2003.
duplicate-object		Returned on full imports by either a file management agent or a database management agent. It indicates an object with the same anchor has already been reported to the synchronization engine during this run.
missing-object-class		Returned by either a file management agent (DSML, LDIF, or a flat file management agent with a configured object class attribute) or in the case of a corrupted Sun ONE Directory Server 4.1x and 5.x (formerly iPlanet Directory Server) and Netscape Directory Server 4.1 and 6.01 change log. This indicates that the management agent could not read a value for the object class attribute.
missing-object-type		Returned when doing a resume of import from a corrupted drop file. Note This error should not be encountered during normal operation.
unmappable-object-type		Returned by a file management agent when it reads an object which has a set of object class values that cannot be matched to any of the prefix mappings.
parse-error		Returned by the management agent for Sun ONE Directory Server 4.1x and 5.x (formerly iPlanet Directory Server) and Netscape Directory Server 4.1 and 6.01 in delta mode and by a file management agent when it cannot parse an entry. The <entry-number> element (and in most cases <line-number> and <column-number>) will be present to help locate the error. The <attribute-name> element may be present. The Sun ONE Directory Server 5.1 management agent will terminate the run when this is encountered. The file management agent will log the discovery error and continue.
read-error		Returned by a call based management agent when there is a generic error reading a particular object. This generally causes termination of the run. The connected directory error element will be present to help troubleshoot the problem.
staging-error		Returned by most management agents, including the management agent for Sun ONE Directory Server 4.1x and 5.x (formerly iPlanet Directory Server) and Netscape Directory Server 4.1 and 6.01. It indicates the synchronization engine could not stage the delta in the connector space. The server will create an event log giving information about the problem that can be used for troubleshooting. Most management agents will continue the import run when the error is logged, but Sun ONE Directory Server 5.1 delta runs will stop because gaps in the change log processing could be cause an inconsistent state in the connector space. Note: This error should not be encountered during normal operation.
invalid-reference-value		Returned by a management agent indicating a distinguished name does not meet Microsoft Identity Integration Server 2003 constraints, which include: One or more characters that are not allowed by Microsoft Identity Integration Server 2003 An empty RDN An RDN exceeding the maximum for Microsoft Identity Integration Server 2003 The number of hierarchy levels of the distinguished name exceeded the maximum for Microsoft Identity Integration Server 2003
invalid-modification-type		Returned during a delta import on an LDIF management agent under two conditions: when a value modification type is not one of the standard LDIF modification types; when there is a non-replace LDIF delta on objectclass, such as: "add: objectclass" or "delete:objectclass"
conflicting-modification-types		Returned during a delta import on an LDIF management agent under two conditions: when there are different attribute level modification types in the same record (in this case the attribute name which produced the conflicting types is reported); when multiple replace LDIF objectclass deltas are seen in the same file, such as: replace: objectclass objectclass: group - replace: objectclass objectclass: user
multi-single-mismatch		Returned by a file management agent when the management agent reports more than one value add or more than one value delete for an attribute that is defined in Microsoft Identity Integration Server 2003 as being a single valued attribute. This error may indicate that the connected directory schema stored with Microsoft Identity Integration Server 2003 was incorrectly specified (file management agents) or out of date with the current connected directory schema.
invalid-attribute-value		Returned by a called-based management agent when an attribute value is read that does not conform to the attribute type declared in schema.
invalid-base64-value		Returned by the LDIF management agent, DSML management agent or Sun ONE Directory Server 5.1 management agent when they fail to parse a base64-encoded value.
invalid-numeric-value		Returned by a file management agent or an LDAP management agent when they are unable to parse a numeric value.
invalid-boolean-value		Returned by a file management agent or an LDAP management agent when they are unable to parse a Boolean value.
reference-value-not-ldap-conformant		Returned by an LDAP management agent, LDIF management agent, DSML management agent or flat file (with configured distinguished name attribute) indicating a distinguished name value does not conform to the LDAP specification.
unsupported-value-type		Returned by an LDIF management agent when a file reference is specified for an attribute which is not of the string attribute type. This is also returned by the DSML management agent when a URI reference is specified for an attribute which is not of the string attribute type. If a file reference needs to be interpreted, set up a scripted import attribute flow and parse the value to discover the file reference the string points to.
locking-error-needs-retry		Returned by a management agent when another management agent is trying to synchronize the same connector spaces object. To resolve this error, rerun the management agent a second time and error should not reoccur. Note This is an error for runs involving full import or full synchronization, and a warning in the following cases: A delta-import to a file A delta-import stage to the connector space A delta-import, delta synchronization A delta synchronization from the connector space A delta synchronization from a file

IMPORT AND SYNCHRONIZATION (IMPORT ATTRIBUTE FLOW – IAF) RELATED ERRORS:

Error Value	Description
exported-change-not-reimported	Changes exported to a management agent were not reconfirmed during this import management agent run. A user or a system process operating outside Microsoft Identity Integration Server 2003 has changed the data in the connected directory in a way that conflicts with the export attribute flow rules configured for Microsoft Identity Integration Server 2003. Alternately, this value indicates a configuration problem where the export attribute flow rule is trying to flow a value to a connected directory object, but the connected directory automatically resets the value to something different without reporting an error to the management agent. The <change-not-reimported> element indicates which changes were not reconfirmed.
extension-dll-exception	The rules extension caused an exception.
extension-dll-crash	The process executing the rules extension unexpectedly terminated. This error can only occur when an a rule extension is being executed out-of-process. A possible cause for this error value is the rules extension is calling code that causes an access violation.
extension-dll-timeout	The rules extension contains an extension timeout value and the call to the extension exceeds this timeout value. Note that when you are debugging the process that is executing the extension, timeouts are not enforced.
extension-projection-object-type-not-set	The implementation of the IMASynchronization.ShouldProjectToMV method in the rules extension does not specify the metaverse object type.
extension-projection-invalid-object-type	The implementation of the IMASynchronization.ShouldProjectToMV method in the rules extension sets the value of the outbound metaverse object type to a value that is not listed in Metaverse Designer of Identity Manager. Check that the method uses one of the specified object type values.
extension-join-resolution-invalid-object-type	The implementation of the IMASynchronization.ResolveJoinSearch method in the rules extension sets the value of the outbound metaverse object type to a value that is not listed in Metaverse Designer of Identity Manager. Check that the method sets the value of the outbound metaverse object type to one of the listed object type values.
extension-join-resolution-index-out-of-bounds	The implementation of the IMASynchronization.ResolveJoinSearch method in the rules extension set an index value that is less than zero or greater than the number of metaverse entry objects.
extension-provisioning-call-limit-reached	The Provision method is called more than 10 times during the synchronization of a single object. The Provision method can be called more than once if the customer logic in the Provision method deprovisions an object and there is resulting attribute recall that causes a change to the metaverse object resulting in a new call to Provision and so on. Identity Integration Server limits the number of such Provision calls to 10 calls in order to stop possible infinite provisioning notes.
extension-deprovisioning-invalid-result	The implementation of the IMASynchronization.Deprovision method returns an invalid DeprovisionAction enumeration value. Verify that the method returns a valid value.
extension-entry-point-not-implemented	The rules extension throws an EntryPointNotImplementedException exception.
extension-unexpected-attribute-value	The rules extension throws an UnexpectedDataException exception.
flow-multi-values-to-single-value	When an import or export attribute flow rule configured in Identity Manager attempts to flow a multi-valued attribute to an attribute with a single value. This value only occurs in flow rules configured in Identity Manager. If the flow rule uses a rules extension that flows a multi-valued attribute to a single value attribute, the TooManyValuesException exception is thrown.
cs-attribute-type-mismatch	The type of the imported attribute does not match the attribute type specified in the management agent schema. For more information about synchronizing the management agent schema with the connected data source schema, see "Refresh a management agent schema" in Microsoft Identity Integration Server 2003 help.
join-object-id-must-be-single-valued	The data source attribute value used to join a metaverse object through a join rule specified in the properties of a management agent in Identity Manager contains more than one value. The data source attribute value used in the join rule can only contain a single value.
dn-index-out-of-bounds	The distinguished name component index value used in an import attribute flow configured in the properties of a management agent in Identity Manager is larger than the number of components in the distinguished name of the source object.
connector-filter-rule-violation	A connector object becomes a filtered disconnector object as a result of a connector-filter configuration during provisioning or export attribute flow. This value will not occur on explicit connector objects.
unsupported-container-delete	The management agent is attempting to delete a container object during deprovisioning. The management agents included in Microsoft Identity Integration Server 2003 cannot delete container objects.
ambiguous-import-flow-from-multiple-connectors	An import attribute flow rule defined in Identity Manager is for a management agent with multiple connector objects joined to a metaverse object. To import attributes through a management agent with multiple connectors to a metaverse object, use a rules extension to define the flow rules rather than configuring a join rule in the properties of a management agent.
ambiguous-export-flow-to-single-valued-attribute	The export flow rule configured in the properties for a management agent in Identity Manager is attempting to flow values from a reference attribute of a metaverse object to a single connector object in the connector space but the metaverse object is joined to multiple connector objects in the connector space
cannot-parse-dn-component	The distinguished name mapping rule specified in the properties of a management agent in Identity Manager cannot flow an improperly formatted distinguished name component to the metaverse object.
cannot-parse-object-id	The string value used to search for a metaverse object in a join rule specified in the properties of a management agent in Identity Manager is not in the correct globally-unique identifier (GUID) format. The GUID format is "{nnnnnnnn-nnnn-nnnn-nnnn-nnnnnnnnnnnn}" where "n" is a hexadecimal number.
unexported-container-rename	The implementation of the IMVSynchronization.Provision or IMASynchronization.Deprovision method is attempting to rename a container object with one or more unexported child objects.
unique-index-violation	A user is manually setting a unique index number on an attribute in a metaverse table. Do not manually configure the metaverse tables.
mv-constraint-violation	The attribute value from the connector space exceeds the length restrictions of the metaverse attribute.
locking-error-needs-retry	Returned by a management agent when another management agent is trying to synchronize the same connector spaces object. To resolve this error, rerun the management agent a second time and error should not reoccur. Note This is an error for runs involving full import or full synchronization, and a warning in the following cases: A delta-import to a file A delta-import stage to the connector space A delta-import, delta synchronization A delta synchronization from the connector space A delta synchronization from a file
unexpected-error	An unexpected error occurred during an apply change management agent run. Check the event log for more information.
exported-change-not-reimported	Changes exported to a management agent were not reconfirmed during this import management agent run. A user or a system process operating outside Microsoft Identity Integration Server 2003 has changed the data in the connected directory in a way that conflicts with the export attribute flow rules configured for Microsoft Identity Integration Server 2003. Alternately, this value indicates a configuration problem where the export attribute flow rule is trying to flow a value to a connected directory object, but the connected directory automatically resets the value to something different without reporting an error to the management agent. The <change-not-reimported> element indicates which changes were not reconfirmed.

EXPORT AND SYNCHRONIZARION (EXPORT ATTRIBUTE FLOW – EAF) RELATED ERRORS:

Error Value	Cause
ambiguous-update	The management agent cannot fulfill an update or delete request because the anchor is incorrectly configured or not unique. This error can be returned by SQL and Oracle management agents. If this error is encountered, check the anchor construction rules to ensure that each object has a unique anchor value.
anchor-too-long	An attempt is made to construct an anchor that exceeded the maximum size limit for Microsoft Identity Integration Server 2003. This error can be returned by database management agents, file management agents, or the iPlanet 4.0 management agent.
cd-error	An error is encountered while attempting to communicate with a connected data source, but there is no specialized error type for this error. This error is accompanied by a <cd-error> element, which contains information that should aid in troubleshooting the cause of the error.
cd-existing-object	A request to add an object is exported to the connected data source, but the object is already present in the connected data source. This error can be returned by call-based management agents except for relational database management agents. It is never returned by file management agents.
cd-missing-object	A request to modify an object is exported to the connected data source, but the object cannot be found in the connected data source. This error can be returned by call-based management agents, but never by a file management agents. The likely cause of this error is because some person or external process has deleted the object from the connected data source outside Identity Integration Server.
certifier-ou-not-configured	An attempt is made to provision out a new user or container (o or ou) and the certifier name you have specified for the "_MMS_Certifier" attribute is not the name of a properly configured certifier container. Each certifier container must be configured using the Identity Integration Server administrative UI before it can be used in provisioning. This error can be returned by the management agent for Lotus Notes.
code-page-conversion	An attempt is made to export an attribute value, which is stored in Unicode within the Identity Integration Server, to the code page of the export file, but fails because of conversion errors. This error can be returned by file management agents.
constraint-violation	An attempt is made to export an add, modify, or delete request that violates the constraints of a connected data source. This error can be returned by LDAP management agents and database management agents. Violations for LDAP management agents include setting multiple values for a single valued attribute, exceeding field width constraints on string and binary attributes, or exceeding range constraints on numeric attributes. Database management agents can impose a variety of constraints, including those for referential integrity, rules, and constraints that may be defined for their database.
dn-attributes-failure	An attempt is made to export an add or modify request that sets a reference value for which there is no corresponding connected data source object. This error can be returned by the Active Directory management agent, Active Directory/Application Mode management agent, and global address list synchronization management agent. The other management agents do not generate an error in this situation—the set is accepted by the connected data source. To correct this error, use the connector space object viewer to determine which of the changes to the reference attributes were not successfully exported.
duplicate-anchor	The anchor on a newly provisioned object is not unique. This error can be returned by file management agents, database management agents, or the iPlanet 4.0 management agent. If this error is encountered, check the anchor construction rules to ensure that each object has a unique anchor value.
encryption-not-enabled	An attempt is made to set or change the password attribute and the connection that the management agent uses to communicate to the connected data source has not been configured with an appropriate encryption mechanism (128 bit SSL or TLS). This error can be returned by the Active Directory/Application Mode management agent. 128-bit SSL or TLS configuration is a requirement imposed by Active Directory/AM for setting passwords.
insufficient-columns	An attempt is made to export an add or modify request to an object and the number of values for a multivalued attribute exceeds the number of columns configured for that attribute's multi-values. This error can be returned by the Fixed Width management agent or Delimited management agent.
insufficient-field-width	An attempt is made to export an add or modify request to an object and the value of an attribute exceeds the width of the column. This error can be returned by the Fixed Width management agent.
invalid-attribute-value	An attempt is made to flow out an attribute value that contains characters which are not not valid for the connected data source. For example, the attribute values exported to the fixed width, delimited, and AVP file management agents cannot contain CR, LF, or EOF characters.
invalid-dn	An attempt is made to export a newly provisioned object or rename an existing object, and the distinguished name is incompatible with the connected data source naming requirements. This error can be returned by LDAP management agents and the Windows NT 4.0 management agent.
invalid-provisioning-attribute-value	An attempt is made to export a newly provisioned object, but certain attributes for provisioning set by the customer extension are not valid (such as not in a certain value range).
kerberos-no-logon-server	An attempt is made to set or change a password attribute, and the management agent cannot resolve a server for the domain part of the logon credentials. This generally means a NetBIOS or DNS misconfiguration. This error can be returned by the Active Directory management agent or the global address list synchronization management agent.
kerberos-time-skew	The password attribute is being set or changed, and the time on the server running Identity Integration Services differs from the time on the Active Directory domain controller by more than five minutes. This error can be returned by the management agent for Active Directory or the management agent for Active Directory global address list (GAL).
locking-error-needs-retry	Returned by a management agent when another management agent is trying to synchronize the same connector spaces object. To resolve this error, rerun the management agent a second time and error should not reoccur.
missing-anchor-component	An attempt is made to export a newly provisioned object, but an anchor cannot be generated because a value required for constructing the anchor is not available. Possible for reasons for this error are that the attribute was not set at provisioning time (in the case of the iPlanet 4.0 management agent, database management agents, or file management agents) or it cannot be read from the connected data source (Active Directory management agents, the iPlanet 5.0 management agent, and database management agents when the anchor is constructed from an auto-increment column).
missing-provisioning-attribute	An attempt is made to export a newly provisioned object, but certain attributes that are required for provisioning a new object have not been set by the customer extension. This error can be returned by the Notes management agent.
modify-naming-attribute	An attempt is made to export a request where a naming attribute (such as CN for many object types) is set to a value that conflicts with the RDN value. This error can be returned by LDAP management agents. This error can occur because of a poorly defined export attribute flow rule or an error in the process code that sets initial values on a newly provisioned object.
multi-valued-anchor-component	An attempt is made to construct the anchor for a newly provisioned object, but one of the attributes used in constructing the anchor has multiple values. This error can be returned by the iPlanet 4.0 management agent. Attributes used in the anchor construction can be defined to be multivalued in the connected data source schema, but they must only have a single value on the objects in Identity Integration Server.
no-export-to-this-object-type	The management agent only allows import of objects of this object type. No export operations are allowed on this type of object. This error is returned by the NT 4.0 management agent if you try to perform provisioning operations or export attribute flow on computer objects.
non-existent-parent	An attempt is made to export an add or a rename request but the parent object does not exist in the connected data source. This error can be returned by LDAP management agents.
password-policy-violation	The password attribute is set or changed to a value which does not meet the administrator defined password policy of the connected data source. This error can be returned by the Active Directory management agent and global access list directory synchronization management agents.
password-set-disallowed	The password encryption is set to either no encryption or less than 128-bit SSL and the administrator has not explicitly made an override to allow password sets. This error can be returned by the Active Directory management agent.
permission-issue	An attempt is made to export an add, modify, or delete request and the management agent has insufficient permissions to perform the operation against the connected data source. This error can be returned by LDAP management agents and the NT4.0 management agent.
provision-to-secondary-nab	An attempt is made to provision a person or certifier object to a secondary Notes address book. This error can be returned by the Notes management agent. Lotus Notes only allows provisioning contacts to secondary Notes address books.
rename-to-existing-dn	An attempt is made to change the distinguished name of the object at the time of export but there is already an object in the connector space with that distinguished name. The distinguished name of an object can be changed on export in two ways: Database management agents, where the distinguished name is calculated based on the values of the attributes making up the anchor (these values may not be present until the object is exported) LDAP management agents where the connected data source applies certain normalization rules that cause the distinguished name to change. In either case, examine how the distinguished name property of the object is created in the provisioning extension.
schema-violation	An attempt is made to export an object modification that would add an attribute that is not in the connected data source schema or remove an attribute from an object which is required by the schema. This error can be returned by LDAP management agents. In most cases Identity Integration Server will not allow this error to occur since its rules check the stored copy of the connected data source schema. However, this error can occur if the Identity Integration Server schema is out of date with the connected data source schema. If this error is encountered, use the Identity Manager to refresh the schema stored with the management agent.
syntax-violation	An attempt is made to export a request where the value for an attribute violates certain value constraints. This error can be returned by the management agent for LDAP Data Interchange Format (LDIF) files and the management agent for Windows NT 4.0. A typical case of this error is when the value being exported contains a character that is not valid.
temporary-certifier-file-creation-failure	An attempt was made to fetch the certifier information for the certifier container specified by the "_MMS_Certifier" attribute and temporarily create a certifier file in the MAData directory of the Notes MA for use by the Notes API. This occurs when a new user or container (o or ou) is provisioned. If this process of creating the certifier file fails for any reason (for example, out of disk space, permissions, etc) this export error is reported. This error can be returned by the Lotus Notes management agent.
unexpected-error	An attempt is made to export a change and an unexpected error is encountered. To help troubleshoot this error, examine the event log. This error should not be encountered as part of normal operation and indicates a product malfunction. If you do encounter this error, contact Microsoft Product Support.
unexpected-provisioning-attribute	This error is returned when you are exporting a newly provisioned object and certain attributes for provisioning set by the customer extension should not be included because they are incompatible with the values of other provisioning attributes. This error is returned by the Notes management in the following cases: When you create a contact (_MMS_IDRegType=0) and supply any one of the following attributes: _MMS_Certifier _MMS_OU _MMS_Password _MMS_IDStoreType _MMS_IDPath MailFile When you create a U.S. user or International user but do not specify creating an ID file (_MMS_IDStoreType=0), but supply the _MMS_IDPath or MailFile attributes. When you create an OU (certifier), and supply the _MMS_OU attribute. When you create an O (certifier), and supply the _MMS_Certifier attribute.

WMI PROVIDER RETURN STRINGS:

Return code/value

Description

call-failure

An unexpected error occurred.

Check the event log for more information.

connection-failure

This error is returned when you have successfully obtained a WMI object, but either the service has been stopped or your security identity has been removed from the security group(s) that have rights to use the WMI interface (administrators, operators, password set, and browse).

The following return values are common to the following methods, properties, and XML elements:

MIIS_ManagementAgent.Execute method

MIIS_ManagementAgent.RunStatus property

MIIS_RunHistory.RunStatus property

< step-result > element of the < run-history > XML string

Return code/value

Description

completed-discovery-errors

The full import run step stopped and the data was not obsoleted because of discovery errors between the connected directory and the connector space. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.

completed-export-errors

The run step completed with export errors. The next step in the run profile will run. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.

completed-no-objects

The full import run step found nothing to import.

completed-sync-errors

The run step completed with synchronization errors or warnings. The next step in the run profile will run and data will be obsoleted. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.

completed-transient-objects

The run step completed with objects in the connector space in a transient state. For more information about the transient state, see "The metaverse and the connector space" in the ILM 2007 FP1 Help. The next step in the run profile will run and data will be obsoleted. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.

completed-warnings

The run step completed with synchronization warnings. The next step in the run profile will run and data will be obsoleted. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.

completing-obsoletion

The system is in the process of marking objects in the connector space that no longer exist in the connected data source as obsolete. You can see how complete by the value of in-progress.

completing-referential-updates

The system is in the process of completing its referential updates. You can see how complete by the value of in-progress.

connection-failure

The server is not running or your credentials were removed from the security groups.

Check that the credentials used is a member of a ILM 2007 FP1 security group. The method can return this string after you obtain the WMI provider object.

in-progress

Indicates the percentage of completion for processes that are not yet complete.

no-start-bad-ma-configuration

The run step failed to start because the management agent configuration is corrupt. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.

Recreate the management agent to prevent this return value.

If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.

no-start-change-log-not-enabled

The delta import run step failed to start because the change log in the Sun ONE Directory Server 5.1 (formerly iPlanet Directory Server) was not enabled. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.

Enable the change log in the server to prevent this return value. For more information about enabling the change log, see the Sun ONE Directory Server 5.1 documentation.

If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.

no-start-connection

The run step failed to start because of connection problems. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.

Verify that you are connected to the server to prevent this return value.

If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.

no-start-credentials

The run step failed to start because of credential problems. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.

Verify that the credentials used to execute the run profile are members of the appropriate security group. For more information about ILM 2007 FP1 security groups, see "Using security groups" in the Microsoft Identity Integration Server 2003 Help.

If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.

no-start-database-permission

The run step failed to start because the account used does not have permission to access to the database or the table. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.

Verify that the account used to run the management agent has access to the database or table.

If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.

no-start-database-schema-mismatch

The run step failed to start because the configured schema does not match the schema in the connected directory. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.

Verify that the schemas in the connected directory and the configuration match.

If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.

no-start-database-table

The run step failed to start because the management agent is connected to the database but could not access the specified table. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.

no-start-delta-step-type-not-configured

The delta import run step failed to start because the management agent is not configured for a delta import. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.

no-start-file-access-denied

The run step failed to start because access to the file specified in the Input file name text box of Management agent configuration in the Configure Run Profile dialog box was denied. Verify that you have access to the file.

If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.

no-start-file-code-page

The run step failed to start because the selected code page does not match the file specified in Template Input File of the management agent properties. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.

Use the code page that is appropriate for the input file. For more information about specifying the code page, see "Select a template input file" in the ILM 2007 FP1 Help.

If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.

no-start-file-contains-incorrect-step-type

The run step failed to start because the step requires a different type of drop file. For example, the step might require a delta-import drop file but the drop file is from a full-import step.

Verify that you are providing the correct type of drop file.

no-start-file-not-found

The run step failed to start because the file specified in Input file name text box of Management agent configuration in the Configure Run Profile dialog box could not be found. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.

Verify the specified input file is in the working folder of the management agent. For more information about specifying the input file used by a run profile step, see "Example: Running a Management Agent With a Specified Run Profile" in the ILM 2007 FP1 Help.

If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.

no-start-file-open

The run step failed because the file specified in Input file name text box of Management agent configuration in the Configure Run Profile dialog box could not be opened. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.

If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.

no-start-file-sharing-violation

The run step failed to start because of a sharing violation on the file specified in Input file name text box of Management agent configuration in the Configure Run Profile dialog box. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.

Verify that ILM 2007 FP1 is the only program that is using this file. If not, close all other programs.

If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.

no-start-full-import-required

The delta import run step failed to start because you first need to complete a full import step. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.

Complete a full import step before starting a delta import to prevent this return value.

If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.

no-start-header-row-mismatch

The import run step stopped because the header row in the file did not match the configured header row.

Make the necessary modifications so that the header row in the file matches the configured header row.

no-start-ma

The run step failed to start because of an unknown management agent error. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.

If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.

no-start-no-domain-controller

The run step failed to start because the domain controller could not be contacted by the server. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.

Verify that the domain controller is connected to the network.

If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.

no-start-no-partition-delete

The run step failed to start because domain or naming context has been deleted. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.

Verify that the specified partition still exists.

If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.

no-start-partition-not-configured

The run step failed to start because the required partition is not selected in Configure Directory Partitions dialog box of the management agent properties. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.

Verify that the appropriate partition is selected. For more information see "Configure directory partitions" in the ILM 2007 FP1 Help.

If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.

no-start-partition-rename

The run step failed to start because the selected partition in Configure Directory Partitions dialog box of the management agent properties has been renamed. Verify that the appropriate partition is selected. For more information, see "Configure directory partitions" in the ILM 2007 FP1 Help.

If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.

no-start-server

The run step failed to start because of an unknown server error. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.

no-start-unknown-profile-name

Could not execute management agent because the name of the profile passed as a parameter to the Execute call is unknown.

stopped-bad-ma-configuration

The run step stopped because of a corrupted management agent configuration. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.

Verify that your management agent is configured correctly. For more information about configuring your management agent, see Configure Management Agents in the ILM 2007 FP1 Help.

stopped-change-log-out-of-order

In some cases the Sun ONE Directory Server can write a change log (used for delta imports) with entries which are not numbered sequentially.

To fix this problem, run a full import before doing more delta imports.

stopped-code-page-conversion

The import run step stopped because of a code page conversion error. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.

Verify that you are using the appropriate code page for the template input file. For more information about setting the code page, see "Select template input file" in the ILM 2007 FP1 Help.

If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.

stopped-connectivity

The run step stopped because of connectivity loss. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.

Restore connectivity to the server.

If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.

stopped-database-connection-lost

The run step stopped because the server is not connected to the SQL Server database used by the ILM 2007 FP1 server. This value occurs if the server stores the metadirectory on a separate computer that is running SQL Server. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.

Resolve the connection problem.

stopped-database-disk-full

The run stopped because the SQL Server database used by the ILM 2007 FP1 server is full. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.

Create some space in the SQL Server database.

stopped-deadlocked

The run step stopped because of an internal server deadlock between multiple management a

Jorge 's Quest For Knowledge!

Search

Tags

News

Navigation

Archives

DISCLAIMER

Guess who?

Interesting Places

Other BLOGS

Troubleshooting MIIS (ILM) Related Error Codes

Return code/value	Description
completed-discovery-errors	The full import run step stopped and the data was not obsoleted because of discovery errors between the connected directory and the connector space. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.
completed-export-errors	The run step completed with export errors. The next step in the run profile will run. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.
completed-no-objects	The full import run step found nothing to import.
completed-sync-errors	The run step completed with synchronization errors or warnings. The next step in the run profile will run and data will be obsoleted. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.
completed-transient-objects	The run step completed with objects in the connector space in a transient state. For more information about the transient state, see "The metaverse and the connector space" in the ILM 2007 FP1 Help. The next step in the run profile will run and data will be obsoleted. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.
completed-warnings	The run step completed with synchronization warnings. The next step in the run profile will run and data will be obsoleted. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.
completing-obsoletion	The system is in the process of marking objects in the connector space that no longer exist in the connected data source as obsolete. You can see how complete by the value of in-progress.
completing-referential-updates	The system is in the process of completing its referential updates. You can see how complete by the value of in-progress.
connection-failure	The server is not running or your credentials were removed from the security groups. Check that the credentials used is a member of a ILM 2007 FP1 security group. The method can return this string after you obtain the WMI provider object.
in-progress	Indicates the percentage of completion for processes that are not yet complete.
no-start-bad-ma-configuration	The run step failed to start because the management agent configuration is corrupt. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed. Recreate the management agent to prevent this return value. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.
no-start-change-log-not-enabled	The delta import run step failed to start because the change log in the Sun ONE Directory Server 5.1 (formerly iPlanet Directory Server) was not enabled. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed. Enable the change log in the server to prevent this return value. For more information about enabling the change log, see the Sun ONE Directory Server 5.1 documentation. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.
no-start-connection	The run step failed to start because of connection problems. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed. Verify that you are connected to the server to prevent this return value. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.
no-start-credentials	The run step failed to start because of credential problems. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed. Verify that the credentials used to execute the run profile are members of the appropriate security group. For more information about ILM 2007 FP1 security groups, see "Using security groups" in the Microsoft Identity Integration Server 2003 Help. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.
no-start-database-permission	The run step failed to start because the account used does not have permission to access to the database or the table. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed. Verify that the account used to run the management agent has access to the database or table. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.
no-start-database-schema-mismatch	The run step failed to start because the configured schema does not match the schema in the connected directory. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed. Verify that the schemas in the connected directory and the configuration match. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.
no-start-database-table	The run step failed to start because the management agent is connected to the database but could not access the specified table. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.
no-start-delta-step-type-not-configured	The delta import run step failed to start because the management agent is not configured for a delta import. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.
no-start-file-access-denied	The run step failed to start because access to the file specified in the Input file name text box of Management agent configuration in the Configure Run Profile dialog box was denied. Verify that you have access to the file. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.
no-start-file-code-page	The run step failed to start because the selected code page does not match the file specified in Template Input File of the management agent properties. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed. Use the code page that is appropriate for the input file. For more information about specifying the code page, see "Select a template input file" in the ILM 2007 FP1 Help. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.
no-start-file-contains-incorrect-step-type	The run step failed to start because the step requires a different type of drop file. For example, the step might require a delta-import drop file but the drop file is from a full-import step. Verify that you are providing the correct type of drop file.
no-start-file-not-found	The run step failed to start because the file specified in Input file name text box of Management agent configuration in the Configure Run Profile dialog box could not be found. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed. Verify the specified input file is in the working folder of the management agent. For more information about specifying the input file used by a run profile step, see "Example: Running a Management Agent With a Specified Run Profile" in the ILM 2007 FP1 Help. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.
no-start-file-open	The run step failed because the file specified in Input file name text box of Management agent configuration in the Configure Run Profile dialog box could not be opened. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.
no-start-file-sharing-violation	The run step failed to start because of a sharing violation on the file specified in Input file name text box of Management agent configuration in the Configure Run Profile dialog box. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed. Verify that ILM 2007 FP1 is the only program that is using this file. If not, close all other programs. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.
no-start-full-import-required	The delta import run step failed to start because you first need to complete a full import step. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed. Complete a full import step before starting a delta import to prevent this return value. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.
no-start-header-row-mismatch	The import run step stopped because the header row in the file did not match the configured header row. Make the necessary modifications so that the header row in the file matches the configured header row.
no-start-ma	The run step failed to start because of an unknown management agent error. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.
no-start-no-domain-controller	The run step failed to start because the domain controller could not be contacted by the server. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed. Verify that the domain controller is connected to the network. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.
no-start-no-partition-delete	The run step failed to start because domain or naming context has been deleted. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed. Verify that the specified partition still exists. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.
no-start-partition-not-configured	The run step failed to start because the required partition is not selected in Configure Directory Partitions dialog box of the management agent properties. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed. Verify that the appropriate partition is selected. For more information see "Configure directory partitions" in the ILM 2007 FP1 Help. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.
no-start-partition-rename	The run step failed to start because the selected partition in Configure Directory Partitions dialog box of the management agent properties has been renamed. Verify that the appropriate partition is selected. For more information, see "Configure directory partitions" in the ILM 2007 FP1 Help. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.
no-start-server	The run step failed to start because of an unknown server error. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.
no-start-unknown-profile-name	Could not execute management agent because the name of the profile passed as a parameter to the Execute call is unknown.
stopped-bad-ma-configuration	The run step stopped because of a corrupted management agent configuration. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed. Verify that your management agent is configured correctly. For more information about configuring your management agent, see Configure Management Agents in the ILM 2007 FP1 Help.
stopped-change-log-out-of-order	In some cases the Sun ONE Directory Server can write a change log (used for delta imports) with entries which are not numbered sequentially. To fix this problem, run a full import before doing more delta imports.
stopped-code-page-conversion	The import run step stopped because of a code page conversion error. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed. Verify that you are using the appropriate code page for the template input file. For more information about setting the code page, see "Select template input file" in the ILM 2007 FP1 Help. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.
stopped-connectivity	The run step stopped because of connectivity loss. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed. Restore connectivity to the server. If this string is the value for the MIIS_ManagementAgent.RunStatus property, then no run step is currently running but a run step has been run in the past.
stopped-database-connection-lost	The run step stopped because the server is not connected to the SQL Server database used by the ILM 2007 FP1 server. This value occurs if the server stores the metadirectory on a separate computer that is running SQL Server. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed. Resolve the connection problem.
stopped-database-disk-full	The run stopped because the SQL Server database used by the ILM 2007 FP1 server is full. The next step in the run profile will not run and data will not be obsoleted. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed. Create some space in the SQL Server database.
stopped-deadlocked	The run step stopped because of an internal server deadlock between multiple management a