Share via


<ma-object-error>

Stores information about a parsing error or an object error.

Schema Hierarchy

<run-history>
  <run-details>
    <step-details>
      <ma-discovery-errors>

Syntax

<xs:element name="ma-object-error" minOccurs="0" maxOccurs="unbounded" >  <xs:complexType>    <xs:sequence>       <xs:element name="error-type" minOccurs="1" maxOccurs="1">         <xs:simpleType>           <xs:restriction base="xs:string">           <xs:enumeration value="missing-change-type"/>           <xs:enumeration value="invalid-change-type"/>           <xs:enumeration value="multi-valued-change-type"/>           <xs:enumeration value="need-full-object"/>           <xs:enumeration value="missing-dn"/>           <xs:enumeration value="dn-not-ldap-conformant"/>           <xs:enumeration value="invalid-dn"/>           <xs:enumeration value="missing-anchor-component"/>           <xs:enumeration value="multi-valued-anchor-component"/>           <xs:enumeration value="anchor-too-long"/>           <xs:enumeration value="duplicate-object"/>           <xs:enumeration value="missing-object-class"/>           <xs:enumeration value="missing-object-type"/>           <xs:enumeration value="unmappable-object-type"/>           <xs:enumeration value="parse-error"/>           <xs:enumeration value="read-error"/>           <xs:enumeration value="staging-error"/>           <xs:enumeration value="invalid-reference-value"/>         </xs:restriction>       </xs:simpleType>     </xs:element>     <xs:element name="entry-number" type="xs:unsignedInt" minOccurs="0" maxOccurs="1"  />     <xs:element name="line-number" type="xs:unsignedInt" minOccurs="0" maxOccurs="1"  />     <xs:element name="column-number" type="xs:unsignedInt" minOccurs="0" maxOccurs="1"  />     <xs:element name="dn" type="dnType" minOccurs="0" maxOccurs="1"  />     <xs:element name="anchor" type ="anchorType" minOccurs="0" maxOccurs="1" />     <xs:element name="attribute-name" type="xs:string" minOccurs="0" maxOccurs="1"  />     <xs:element name="cd-error" minOccurs="0" maxOccurs="1" >       <xs:complexType>         <xs:sequence>           <xs:element name="error-code" type="xs:string" minOccurs="1" maxOccurs="1"  />           <xs:element name="error-literal" type="xs:string" minOccurs="1" maxOccurs="1"  />           <xs:element name="server-error-detail" type="xs:string" minOccurs="0" maxOccurs="1"  />           <xs:element name="value" type="xs:string" minOccurs="0" maxOccurs="unbounded" />         </xs:sequence>       </xs:complexType>     </xs:element>   </xs:sequence> </xs:complexType></xs:element>

element

Attributes and Elements

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

Attributes

None

Child Elements

Element Min Occurs Max Occurs Description

<anchor> of <ma-object-error>

0

1

Indicates the anchor of the object that has the error on it.

Note

Reported by management agents if they have this information available. This is not shown in the user interface, but is available when the run history is saved to a file.

<attribute-name>

0

1

Gives the context if there is a mismatch on what type of attribute it is or whether an attribute contains a single value.

<cd-error> of <ma-object-error>

0

1

Enables the management agent to report additional connected directory–specific information about the error.

<column-number>

0

1

Indicates the column number at or near where the problem occurred.

Note

Only used by the file management agent.

<dn> of <ma-object-error>

0

1

Indicates the distinguished name (DN) of the object for which the error occurred.

Note

Reported by management agents, if they have this information available. In the case of flat file management agent (with no configured DN attribute) and database management agents, if an anchor component is missing, no DN is available. File management agents also might not report a DN if there are problems with parsing the element.

<entry-number>

0

1

Indicates which record the error returns to.

Note

Only used 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 the file management agent.

<error-type> of <ma-object-error>

1

1

Contains a description of the discovery error. The list of errors is described in the Remarks section.

<line-number>

0

1

Indicates the line number at or near where the problem occurred.

Note

Only used by the file management agent.

Parent Elements

Element Description

<ma-discovery-errors>

Stores a list of parsing and object errors on objects that the management agent tries to discover.

Remarks

The following are the possible values for the <error-type> of <ma-object-error> element.

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 Lightweight Directory Access Protocol (LDAP) Data Interchange Format (LDIF) full import, or during a delta import that is 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 does not match the list of valid change 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 that the management agent submitted a modification on an object that cannot be located in the connector space. The synchronization engine is requesting the current values of all attributes on the object. Because this is an import from a file, that information is not available. A full import run takes care of this problem.

missing-dn

Returned for file management agents (LDIF, Directory Service Markup Language [DSML], or flat file with configured distinguished name attribute) when there is no distinguished name value. This is also returned when a corrupted Sun ONE Directory Server 5.1 change log has a missing distinguished name attribute. It indicates that 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 a management agent reports that a distinguished name does not meet a Forefront Identity Manager Synchronization Service (FIM Synchronization Service) constraint, which includes:

  • One or more characters that are not allowed by FIM Synchronization Service.

  • An empty relative distinguished name (also known as RDN).

  • A relative distinguished name that exceeds the maximum for FIM Synchronization Service.

  • The number of hierarchy levels of the distinguished name exceeded the maximum for FIM Synchronization Service.

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. It indicates that 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. It indicates that the management agent anchor construction produced an anchor that exceeded the maximum size limit for FIM Synchronization Service.

duplicate-object

Returned on full imports by either a file management agent or a database management agent. It indicates an object that has the same anchor was already 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 that has a configured object class attribute), or in the case of a corrupted change log for Sun ONE Directory Server 4.1x and 5.x (formerly iPlanet Directory Server) and Netscape Directory Server 4.1 and 6.01. 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

You should not encounter this error during normal operation.

unmappable-object-type

Returned by a file management agent when it reads an object that 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, the <line-number> and <column-number> elements) are present to help locate the error. The <attribute-name> element might be present. The Sun ONE Directory Server 5.1 management agent terminates the run when this is encountered. The file management agent logs the discovery error and continues.

read-error

Returned by a call based management agent when there is a generic error reading a particular object. This generally causes the run to terminate. The connected directory error element is 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 that the synchronization engine could not stage the delta in the connector space. The server creates an event log that provides information about the problem that can be used for troubleshooting. Most management agents continue the import run when the error is logged, but Sun ONE Directory Server 5.1 delta runs stop because gaps in the change log processing can cause an inconsistent state in the connector space.

Note

You should not encounter this error during normal operation.

invalid-reference-value

Returned by a management agent and indicates a distinguished name does not meet FIM Synchronization Service constraints, which include:

  • One or more characters that are not allowed by FIM Synchronization Service.

  • An empty relative distinguished name (also known as RDN).

  • An empty relative distinguished name that exceeds the maximum for FIM Synchronization Service.

  • The number of hierarchy levels of the distinguished name exceeded the maximum for FIM Synchronization Service.

The following <error-type> of <ma-object-error> elements include an <attribute-name> element to provide the context for the error.

Value Description

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, and 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 that produced the conflicting types is reported), and when multiple replace LDIF objectclass deltas are seen in the same file, such as replace: objectclassobjectclass: groupreplace: objectclassobjectclass: 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 FIM Synchronization Service as being a single-valued attribute. This error may indicate that the connected directory schema that is stored with FIM Synchronization Service was incorrectly specified (file management agents) or is out of date with the current connected directory schema.

invalid-attribute-value

Returned by a call-based management agent when an attribute value is read that does not conform to the attribute type that is declared in the 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 cannot parse a numeric value.

invalid-boolean-value

Returned by a file management agent or an LDAP management agent when they cannot 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) that indicates 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 that is not of the string attribute type. The DSML management agent also returns this when a URI reference is specified for an attribute that is not of the string attribute type.

If a file reference must be interpreted, set up a scripted import attribute flow and parse the value to discover the file reference that the string points to.

locking-error-needs-retry

Returned by a management agent when another management agent tries to synchronize the same connector spaces object. To resolve this error, rerun the management agent a second time, and the error should not reoccur.

Note

This is an error for runs that involve 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

See Also

Reference

<ma-discovery-errors>

Concepts

Run History XML