<error-type>

Visual Studio 2010

Updated: April 16, 2010

Contains the value that indicates the type of error that occurred. The element can contain an <extension-error-info> of <retry-error> element. The <extension-error-info> element provides additional information about the cause of the error. For more information, see <extension-error-info> of <retry-error>

<error-type>
</error-type>

element

The following sections describe attributes, child elements, and parent elements.

Attributes

None

Child Elements

None

Parent Elements

 

Element Description

<import-error>

Lists an error that occurs when you import a connector space delta into the metaverse.

<retry-error>

Contains information about an object that could not be synchronized.

The following are the possible values for this element.

 

Error Description

exported-change-not-reimported

Changes that were exported to a management agent were not reconfirmed during this import management agent run. A user or a system process that operates outside Forefront Identity Manager Synchronization Service (FIM Synchronization Service) has changed the data in the connected directory in a way that conflicts with the export attribute flow rules that are configured for FIM Synchronization Service. Alternatively, this value indicates a configuration problem in which 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 that executes the rules extension unexpectedly terminated. This error can only occur when 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.

noteNote:
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 ShouldProjectToMV method in the rules extension does not specify the metaverse object type.

extension-projection-invalid-object-type

The implementation of the 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 Synchronization Service Manager. Verify that the method uses one of the specified object type values.

extension-join-resolution-invalid-object-type

The implementation of the 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 Synchronization Service Manager. Verify 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 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. You can call the Provision method 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. FIM Synchronization Service limits the number of such Provision calls to 10 calls to stop possible infinite provisioning notes.

extension-deprovisioning-invalid-result

The implementation of the 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 that is configured in Synchronization Service Manager tries to flow a multi-valued attribute to an attribute that has a single value. This value only occurs in flow rules that are configured in Synchronization Service 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 Forefront Identity Manager 2010 (FIM) Help.

join-object-id-must-be-single-valued

The data source attribute value that is used to join a metaverse object through a join rule that is specified in the properties of a management agent in Synchronization Service Manager contains more than one value. The data source attribute value that is used in the join rule can only contain a single value.

dn-index-out-of-bounds

The distinguished name component index value that is used in an import attribute flow that is configured in the properties of a management agent in Synchronization Service 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 does not occur on explicit connector objects.

unsupported-container-delete

The management agent is trying to delete a container object during deprovisioning. The management agents in FIM Synchronization Service cannot delete container objects.

ambiguous-import-flow-from-multiple-connectors

An import attribute flow rule that is defined in Synchronization Service Manager is for a management agent that has multiple connector objects joined to a metaverse object. To import attributes through a management agent that has multiple connectors to a metaverse object, use a rules extension to define the flow rules instead of configuring a join rule in the properties of a management agent.

ambiguous-export-flow-to-single-valued-attribute

The export flow rule that is configured in the properties for a management agent in Synchronization Service Manager is trying 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 that is specified in the properties of a management agent in Synchronization Service Manager cannot flow an incorrectly formatted distinguished name component to the metaverse object.

cannot-parse-object-id

The string value that is used to search for a metaverse object in a join rule that is specified in the properties of a management agent in Synchronization Service Manager is not in the correct GUID format. The GUID format is {nnnnnnnn-nnnn-nnnn-nnnn-nnnnnnnnnnnn}, where n is a hexadecimal number.

unexported-container-rename

The implementation of the Provision method or the Deprovision method is trying to rename a container object that has 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 the error should not reoccur.

noteNote:
This is an error for runs that involve full import or full synchronization, and it is 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 that were exported to a management agent were not reconfirmed during this import management agent run. A user or a system process that operated outside FIM Synchronization Service changed the data in the connected directory in a way that conflicts with the export attribute flow rules that are configured for FIM Synchronization Service. Alternatively, 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.



Community Additions

ADD
Show: