<retry-error>

  • Article

Contains information about an object that could not be synchronized.

Schema Hierarchy

<run-history>
  <run-details>
    <step-details>
      <mv-retry-errors>

Syntax

<retry-error>
  <date-occurred>
  </date-occurred>
  <algorithm-step>
  </algorithm-step>
  <error-type>
  </error-type>
  <extension-error-info>
  </extension-error-info>
  <rule-error-info>
  </rule-error-info>
</retry-error>

element

Attributes and Elements

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

Attributes

None

Child Elements

Element Min Occurs Max Occurs Description

<algorithm-step> of <retry-error>

1

1

Indicates the stage of synchronization when the error occurred.

<date-occurred>

1

1

Contains the date, in Coordinated Universal Time (UTC), of when this instance of the error occurred. The format is documented in the Remarks section.

<error-type>

1

1

Indicates the type of error that occurred. The element can contain an <extension-error-info> 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>.

The following are the possible values for this element:

 

Error Description

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.

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.

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) 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-error-info> of <retry-error>

0

1

Provides contextual information about an exception, and in some cases, the call stack of an exception. This element is present for some of the <error-type> values. For the following values, the contextual information and call stack appear:

  • extension-dll-exception

  • extension-entry-point-not-implemented

  • extension-unexpected-attribute-value

For the following values, only contextual information appears:

  • extension-dll-crash

  • extension-dll-timeout

  • extension-projection-object-type-not-set

  • extension-projection-invalid-object-type

  • extension-join-resolution-invalid-object-type

  • extension-deprovisioning-invalid-result

For the meaning of these values, see <error-type>.

<rule-error-info>

0

1

Identifies the rule that caused the import error. Full rule error information is included whenever FIM Synchronization Service detects an error condition, or when an exception is thrown if an attribute is mapped for attribute flow or join. The following <error-type> element values cause full rule error information to appear in this element:

  • extension-dll-exception

  • extension-dll-crash

  • extension-dll-timeout

  • extension-entry-point-not-implemented

  • extension-unexpected-attribute-valueflow-multi-values-to-single-value

  • cs-attribute-type-mismatch

  • dn-index-out-of-bounds

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

  • mv-constraint-violation

  • cannot-parse-dn-component

  • cannot-parse-object-id

For more information about these values, see <error-type>. Errors in the implementation of the following methods result in full rule error information appearing in this element:

Parent Elements

Element Description

<mv-retry-errors>

Contains information about metaverse objects that FIM Synchronization Service could not synchronize.

Remarks

The UTC format is yyyy-MM-dd HH:mm:ss.fff.

Format specifier Description

yyyy

Specifies the four-digit year.

MM

Specifies the two-digit month in the range from 1 through 12.

dd

Specifies the two-digit day of the month in the range from 1 through 31.

HH

Specifies the-two digit hour of the day in 24-hour format in the range from 0 through 23.

mm

Specifies the two-digit minute of the day in the range from 0 through 59.

ss

Specifies the two-digit second of the day in the range from 0 through 59.

fff

Specifies the three-digit fractions of a second in the range from 0 through 999.

See Also

Reference

<mv-retry-errors>
ShouldProjectToMV
ResolveJoinSearch

Concepts

Run History XML