Microsoft Identity Integration Server 2003 Developer Reference

import-error

The <import-error> element lists an error importing a connector space delta into the metaverse.

Usage

<import-error
	cs-guid = "guid"
cs-guid The GUID for the connected data source.

	dn = "dn"
dn The distinguished name identifying the connected data source.

/>

Attributes

Attribute Type Required Description
cs-guid guid Yes The GUID for the connected data source.
dn dn Yes The distinguished name identifying the connected data source.

Child Elements

Element Description
<date-occurred> The date, in Coordinated Universal Time (UTC), when this instance of the error occurred. The format is documented in the Remarks section.
<first-occurred> The date, in Coordinated Universal Time (UTC), when this error first occurred. The format is documented in the Remarks section.

This date differs from <date-occurred> if the same error has been encountered on a previous run. If the same error had not been encountered on a previous run, this date is the same as <date-occurred>.

<retry-count> The number of previous runs for which the same error has been encountered. If the same error was not encountered on a previous run, this value is zero.
<algorithm-step> The stage of synchronization when the error occurred.
<error-type> 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.

The following are the possible values for this element.

Error Description
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.
<extension-error-info> This gives the 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 will appear:

  • extension-dll-exception
  • extension-entry-point-not-implemented
  • extension-unexpected-attribute-value

For the following values, only contextual information will appear:

  • 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> Identifies the rule that caused the import error. Full rule error information is included whenever Identity Integration Server detects an error condition or an exception is thrown when mapping an attribute for attribute flow or join. The following <error-type> element values result in full rule error information appearing 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 results in full rule error information appearing in this element:
<change-not-reimported> This information shows an exported change that was not confirmed on reimport.

Parent Elements

Element
<synchronization-errors>

Child Element Sequence

The tree shows the ordering and number of child elements. Child elements in a Sequence must appear in the order given and child elements in a Choice are mutually exclusive. Sequences and Choices can be nested. Element names are followed by the minimum and maximum occurrences.

Sequence
	date-occurred
<date-occurred> The date, in Coordinated Universal Time (UTC), when this instance of the error occurred. The format is documented in the Remarks section.
 (Exactly 1)
	first-occurred
<first-occurred> The date, in Coordinated Universal Time (UTC), when this error first occurred. The format is documented in the Remarks section.

This date differs from <date-occurred> if the same error has been encountered on a previous run. If the same error had not been encountered on a previous run, this date is the same as <date-occurred>.

 (Exactly 1)
	retry-count
<retry-count> The number of previous runs for which the same error has been encountered. If the same error was not encountered on a previous run, this value is zero.
 (Exactly 1)
	algorithm-step
<algorithm-step> The stage of synchronization when the error occurred.
 (Exactly 1)
	error-type
<error-type> 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.

The following are the possible values for this element.

Error Description
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.
 (Exactly 1)
	extension-error-info
<extension-error-info> This gives the 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 will appear:

  • extension-dll-exception
  • extension-entry-point-not-implemented
  • extension-unexpected-attribute-value

For the following values, only contextual information will appear:

  • 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>.
 (Minimum = 0; Maximum = 1)
	rule-error-info
<rule-error-info> Identifies the rule that caused the import error. Full rule error information is included whenever Identity Integration Server detects an error condition or an exception is thrown when mapping an attribute for attribute flow or join. The following <error-type> element values result in full rule error information appearing 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 results in full rule error information appearing in this element:
 (Minimum = 0; Maximum = 1)
	change-not-reimported
<change-not-reimported> This information shows an exported change that was not confirmed on reimport.
 (Exactly 1)
Sequence

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.

Element Information

Can be empty No