| Microsoft Identity Integration Server 2003 Developer Reference |
The <error-type> element is the value indicates the type of error that occurred. The element can contain an <extension-error-info> element. The <extension-error-info> element provides additional information as to the cause of the error. For more information, see <extension-error-info>, later in this topic.
<error-type/>
None.
None.
| Element |
|---|
| <import-error> |
| <retry-error> |
The following are the possible values for this element.
| Error | 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:
|
| 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. |
| Can be empty | No |
|---|