Share via

2.2.1.1.1 step-details

  • Article

The step-details element is an instance of the step-DetailsType type, which is specified via the following XML Schema ([XMLSCHEMA1]) definition:

 <!-- step result types -->
  <xs:complexType name="stepResultType">
   <xs:simpleContent>
    <xs:extension base="xs:string">
     <xs:attribute name="progress" type="progressType" use="optional" />
     <xs:attribute name="file" type="xs:string" use="optional" />
    </xs:extension>
   </xs:simpleContent>
  </xs:complexType>
  
 <xs:complexType name="step-detailsType">
   <xs:sequence>
    <xs:element name="start-date" type="dateTimeNoT" minOccurs="1" maxOccurs="1"  />
    <xs:element name="end-date" type="dateTimeNoT" minOccurs="1" maxOccurs="1"  />
    <!-- add enum -->
    <xs:element name="step-result">
     <xs:complexType>
      <xs:simpleContent>
       <xs:restriction base="stepResultType">
        <xs:enumeration value="completed-discovery-errors"/>
        <xs:enumeration value="completed-export-errors"/>
        <xs:enumeration value="completed-no-objects"/>
        <xs:enumeration value="completed-sync-errors"/>
        <xs:enumeration value="completed-transient-objects"/>
        <xs:enumeration value="completed-warnings"/>
        <xs:enumeration value="completed-skipped-already-completed"/>
        <xs:enumeration value="completing-obsoletion"/>
        <xs:enumeration value="completing-referential-updates"/>
        <xs:enumeration value="completing-recomputation"/>
        <xs:enumeration value="in-progress"/>
        <xs:enumeration value="no-start-bad-ma-configuration"/>
        <xs:enumeration value="no-start-change-log-not-enabled"/>
        <xs:enumeration value="no-start-connection"/>
        <xs:enumeration value="no-start-credentials"/>
        <xs:enumeration value="no-start-database-permission"/>
        <xs:enumeration value="no-start-database-schema-mismatch"/>
        <xs:enumeration value="no-start-database-table"/>
        <xs:enumeration value="no-start-delta-step-type-not-configured"/>
        <xs:enumeration value="no-start-file-access-denied"/>
        <xs:enumeration value="no-start-file-code-page"/>
        <xs:enumeration value="no-start-file-not-found"/>
        <xs:enumeration value="no-start-file-open"/>
        <xs:enumeration value="no-start-file-sharing-violation"/>
        <xs:enumeration value="no-start-full-import-required"/>
        <xs:enumeration value="no-start-header-row-mismatch"/>
        <xs:enumeration value="no-start-ma"/>
        <xs:enumeration value="no-start-ma-working-directory"/>
        <xs:enumeration value="no-start-no-domain-controller"/>
        <xs:enumeration value="no-start-no-partition-delete"/>
        <xs:enumeration value="no-start-partition-not-configured"/>
        <xs:enumeration value="no-start-partition-rename"/>
        <xs:enumeration value="no-start-server"/>
        <xs:enumeration value="no-start-no-steps-in-profile"/>
        <xs:enumeration value="stopped-bad-ma-configuration"/>
        <xs:enumeration value="stopped-change-log-out-of-order"/>
        <xs:enumeration value="stopped-code-page-conversion"/>
        <xs:enumeration value="stopped-connectivity"/>
        <xs:enumeration value="stopped-database-connection-lost"/>
        <xs:enumeration value="stopped-database-disk-full"/>
        <xs:enumeration value="stopped-deadlocked"/>
        <xs:enumeration value="stopped-disk-full"/>
        <xs:enumeration value="stopped-error-limit"/>
        <xs:enumeration value="stopped-export-write"/>
        <xs:enumeration value="stopped-extension-dll-access"/>
        <xs:enumeration value="stopped-extension-dll-ambiguous"/>
        <xs:enumeration value="stopped-extension-dll-exception"/>
        <xs:enumeration value="stopped-extension-dll-file-not-found"/>
        <xs:enumeration value="stopped-extension-dll-instantiation"/>
        <xs:enumeration value="stopped-extension-dll-invalid-assembly"/>
        <xs:enumeration value="stopped-extension-dll-load"/>
        <xs:enumeration value="stopped-extension-dll-missing-dependency"/>
        <xs:enumeration value="stopped-extension-dll-no-implementation"/>
        <xs:enumeration value="stopped-extension-dll-not-configured-for-ma"/>
        <xs:enumeration value="stopped-extension-dll-not-configured-for-mv"/>
        <xs:enumeration value="stopped-extension-dll-updated-version"/>
        <xs:enumeration value="stopped-file-embedded-nulls"/>
        <xs:enumeration value="stopped-import-read"/>
        <xs:enumeration value="stopped-ma"/>
        <xs:enumeration value="stopped-object-limit"/>
        <xs:enumeration value="stopped-out-of-memory"/>
        <xs:enumeration value="stopped-parsing-errors"/>
        <xs:enumeration value="stopped-server"/>
        <xs:enumeration value="stopped-service-shutdown"/>
        <xs:enumeration value="stopped-user-termination-from-extension"/>
        <xs:enumeration value="stopped-user-termination-from-wmi-or-ui"/>
        <xs:enumeration value="success"/>
       </xs:restriction>
      </xs:simpleContent>
     </xs:complexType>
    </xs:element>
    <xs:element name="step-description" type="xs:anyType" minOccurs="1" maxOccurs="1"  />
    <xs:element name="current-export-step-counter" type="numberType" minOccurs="1" maxOccurs="1"  />
    <xs:element name="last-successful-export-step-counter" type="numberType" minOccurs="1" maxOccurs="1"  />
    <xs:element name="ma-connection" type="ma-connectionType" minOccurs="1" maxOccurs="1" />
    <xs:element name="ma-discovery-errors" type="ma-discovery-errorsType" minOccurs="1" maxOccurs="1" />
    <xs:element name="ma-discovery-counters" type="ma-discovery-countersType" minOccurs="1" maxOccurs="1" />
    <xs:element name="synchronization-errors" type="synchronization-errorsType" minOccurs="1" maxOccurs="1" />
    <xs:element name="mv-retry-errors" type="mv-retry-errorsType" minOccurs="1" maxOccurs="1" />
    <xs:element name="outbound-flow-counters" type="outbound-flow-countersType" minOccurs="0" maxOccurs="unbounded" />
    <xs:element name="staging-counters" type="staging-countersType" minOccurs="1" maxOccurs="1" />
    <xs:element name="inbound-flow-counters" type="inbound-flow-countersType" minOccurs="1" maxOccurs="unbounded" />
    <xs:element name="export-counters" type="export-countersType" minOccurs="1" maxOccurs="1" />
   </xs:sequence>
   <xs:attribute name="step-number" type="numberType" use="required" />
   <xs:attribute name="step-id" type="guidType" use="required" />
  </xs:complexType>

The run-details/step-details element stores information about one step of the executed run profile.

The run-details/step-details/@step-number attribute is the run profile step number starting at 1.

The run-details/step-details/@step-id attribute is the run profile step GUID of the run profile step as specified in the management agent properties.

The run-details/step-details/start-date element contains the date and time at which the step began.

The run-details/step-details/end-date element contains the date and time at which the step completed.

The run-details/step-details/step-result element contains the current run profile step status and MUST be one of the following values:

completed-discovery-errors: The full import run step stopped because of discovery errors between the data source and the connector space.

completed-export-errors: The run step completed with export errors. The next step in the run profile will run and data will be obsoleted.

completed-no-objects: The full import run step found no objects to import. The next step in the run profile will run and data will be obsoleted.

completed-sync-errors: The run step completed with synchronization errors or warnings. The next step in the run profile will run and data will be obsoleted.

completed-transient-objects: The run step completed with objects in the connector space in a transient state. The next step in the run profile will run and data will be obsoleted.

completed-warnings: The run step completed with synchronization warnings. The next step in the run profile will run and data will be obsoleted.

completed-skipped-already-completed: The run step was skipped because the run profile was executed in resume mode and the step had completed in the most recent previous attempt. The next step in the run profile will run and data will be obsoleted.

completing-obsoletion: The synchronization engine is in the process of marking objects in the connector space that no longer exist in the data source as obsolete.

completing-referential-updates: The synchronization engine is in the process of completing its referential updates, ensuring that objects that refer to other objects via attribute values are correctly linked.

completing-recomputation: The synchronization engine is in the process of evaluating further metaverse attribute value changes as the result of changes to metaverse attribute values.

in-progress: The synchronization engine is currently executing a run profile for the management agent.

no-start-bad-ma-configuration: The run step failed to start because the management agent configuration is invalid.

no-start-change-log-not-enabled: The delta import run step failed to start because the change log in the data source was not enabled.

no-start-connection: The run step failed to start because of connection problems with the data source.

no-start-credentials: The run step failed to start because the credentials were not accepted by the data source.

no-start-database-permission: The management agent does not have the permissions needed to access the data source.

no-start-database-table: The management agent could not read or write the database table.

no-start-database-schema-mismatch: The database schema does not match the schema defined for the management agent.

no-start-delta-step-type-not-configured: The delta import run step failed to start because the management agent is not configured for a delta import. The next step in the run profile will not run and data will not be obsoleted.

no-start-file-access-denied: The run step failed to start because access to the input file in the management agent configuration was denied.

no-start-file-code-page: The run step failed to start because the selected code page does not match the code page of the file specified in the management agent properties.

no-start-file-not-found: The run step failed to start because the input file specified in the management agent configuration could not be found.

no-start-file-open: The run step failed to start because the input file specified in the management agent configuration could not be opened.

no-start-file-sharing-violation: The run step failed to start because of a sharing violation on the input file specified in the management agent configuration.

no-start-full-import-required: The delta import run step failed to start because a full import step is required prior to running a delta import step.

no-start-header-row-mismatch: The header row in the file does not match the definition specified in the management agent.

no-start-ma: The run step failed to start because of an unknown management agent error.

no-start-ma-working-directory: The run step failed to start because there is no directory or a directory could not be created for the management agent.

no-start-no-domain-controller: The run step failed to start because the domain controller (DC) could not be contacted by the synchronization engine.

no-start-no-partition-delete: The run step failed to start because the domain or naming context (NC) specified in the run step has been deleted.

no-start-partition-not-configured: The run step failed to start because the required partition is not selected in the management agent properties.

no-start-partition-rename: The run step failed to start because the partition selected in the management agent properties has been renamed in the data source.

no-start-server: The run step failed to start because of an unknown synchronization engine error.

no-start-no-steps-in-profile: The run step failed because the run profile contains a step that refers to a partition that has been deleted.

stopped-bad-ma-configuration: The run step stopped because of an invalid management agent configuration.

stopped-change-log-out-of-order: The run step stopped because the data source change log entries are not numbered sequentially.

stopped-code-page-conversion: The import run step stopped because of a code page conversion error.

stopped-connectivity: The run step stopped because of connectivity loss with the data source.

stopped-database-connection-lost: The run step stopped because the server is not connected to the database used by the synchronization engine.

stopped-database-disk-full: The run stopped because the database used by the synchronization engine is full.

stopped-deadlocked: The run step stopped because of an internal server deadlock between multiple currently executing management agent run profiles.

stopped-disk-full: The run step stopped because of a full disk.

stopped-error-limit: The run step stopped because the run profile encountered more than the configured maximum number of errors. The default maximum number of errors is 5000.

stopped-export-write: The export run step stopped because of an error writing to the data source.

stopped-extension-dll-access: The run step stopped because the synchronization engine service account does not have the required permissions to access the Extensions folder.

stopped-extension-dll-ambiguous: The run step stopped because the rules extension contains multiple implementations of the script-based synchronization rule interfaces.

stopped-extension-dll-exception: The run step stopped because of an exception was returned during the initialization of a script-based synchronization rule.

stopped-extension-dll-file-not-found: The run step stopped because the assembly of a script-based synchronization rule specified in the management agent properties cannot be found.

stopped-extension-dll-instantiation: The run step stopped because the constructor of a script-based synchronization rule threw an exception.

stopped-extension-dll-invalid-assembly: The run step stopped because the specified assembly of a script-based synchronization rule is not a valid .NET assembly.

stopped-extension-dll-load: The run step stopped because the specified assembly of a script-based synchronization rule cannot be loaded due to an unknown error.

stopped-extension-dll-missing-dependency: The run step stopped because the extension object cannot be instantiated because the script-based synchronization rule extension is missing a dependency file.

stopped-extension-dll-no-implementation: The run step stopped because the class that is implementing the required interface cannot be found in the specified assembly of a script-based synchronization rule.

stopped-extension-dll-not-configured-for-ma: The run step stopped because the specified assembly of a script-based synchronization rule is not a management agent rules extension.

stopped-extension-dll-not-configured-for-mv: The run step stopped because the specified assembly of a script-based synchronization rule is not a metaverse rules extension.

stopped-extension-dll-updated-version: The run step failed because the Extensions folder was updated when the run step executed.

stopped-file-embedded-nulls: The import run step stopped because the input file contains embedded null characters.

stopped-import-read: The import run step stopped because of a read error on the data source.

stopped-ma: The run step stopped because of an unknown error from the management agent.

stopped-object-limit: The run step stopped because the object limit specified in the threshold property of the management agent properties was reached.

stopped-out-of-memory: The run step stopped because of insufficient server memory.

stopped-parsing-errors: The run step stopped because the program could not parse the input file or the Sun ONE Directory Server change log.

stopped-server: The run step stopped because of an unknown server error.

stopped-service-shutdown: The run step stopped because the synchronization engine service stopped.

stopped-user-termination-from-extension: The run step stopped because the rules extension of a script-based synchronization rule terminated the run by signaling that an error occurred.

stopped-user-termination-from-wmi-or-ui: The run step stopped because the user stopped running the run profile using the Stop method.

success: The operation completed with no errors. The next step in the run profile will run and data will be obsoleted.

The run-details/step-details/step-result/@progress attribute contains information about the progress for given synchronization and staging tasks in the form "x/y" where x is the number of objects processed and y is the total number of items to be processed. This attribute MUST NOT be present unless the run-details/step-details/step-result is one of the following:

  • completing-referential-updates

  • completing-obsoletion

  • completing-recomputation

The run-details/step-details/step-result/@file attribute contains the name of the file configured in the management agent configuration for the step as specified in [MS-UPSCDS] section 2.2.32 and MUST NOT be present unless the run-history/run-details/step-details/step-result is one of the following:

  • completed-no-objects

  • no-start-file-access-denied

  • no-start-file-not-found

  • no-start-file-open

  • no-start-file-sharing-violation

  • stopped-extension-dll-access

  • stopped-extension-dll-ambiguous

  • stopped-extension-dll-exception

  • stopped-extension-dll-file-not-found

  • stopped-extension-dll-instantiation

  • stopped-extension-dll-invalid-assembly

  • stopped-extension-dll-load

  • stopped-extension-dll-missing-dependency

  • stopped-extension-dll-no-implementation

  • stopped-extension-dll-updated-version

  • stopped-file-embedded-nulls

  • stopped-disk-full

The run-details/step-details/step-description element contains the SyncConfig-ma-run-data/run-configuration/configuration/step value for this step as specified in [MS-UPSCDS] section 2.2.32.6.1.

The run-details/step-details/current-export-step-counter element MUST be 0.

The run-details/step-details/last-successful-export-step-counter element MUST be 0.

The run-details/step-details/ma-connection element stores information about the connection between the management agent and the data source. The management agent reports the server it connected to, in addition to any servers it failed to connect to. See section 2.2.1.1.1.1 for details about ma-connection.

The run-details/step-details/ma-discovery-errors element stores a list of errors on objects the management agent tries to discover during import. See section 2.2.1.1.1.2 for details about ma-discovery-errors.

The run-details/step-details/ma-discovery-counters element contains the management agent counters relating to imported objects. See section 2.2.1.1.1.3 for details about ma-discovery-counters.

The run-details/step-details/synchronization-errors element lists the problems encountered while synchronizing data source objects through the metaverse. These errors could be the result of a problem synchronizing a data source object to the metaverse and out to other data sources, or the result of a problem exporting a metaverse object out to a data source. See section 2.2.1.1.1.4 for details about synchronization-errors.

The run-details/step-details/mv-retry-errors element contains information about metaverse objects that the synchronization engine could not synchronize. See section 2.2.1.1.1.5 for details about mv-retry-errors.

The run-details/step-details/outbound-flow-counters element contains information about the number of provisioning changes and exported attributes. An outbound-flow-counters element MUST be present if the run profile step resulted in export attribute flow. See section 2.2.1.1.1.6 for details about outbound-flow-counters.

The run-details/step-details/staging-counters element contains information about the staging of the entries that were imported. See section 2.2.1.1.1.7 for details about staging-counters.

The run-details/step-details/inbound-flow-counters element contains information about the number of disconnectors which became connectors during this run and the disposition of existing connectors. The inbound-flow-counters element MUST be present if and only if the run profile step resulted in inbound attribute flow. See section 2.2.1.1.1.8 for details about inbound-flow-counters.

The run-details/step-details/export-counters element contains information about object changes during a management agent export. See section 2.2.1.1.1.9 for details about export-counters.