Result text

Explanation

batch-file-not-found

The batch or application file configured for the Single step is not or no longer available

batch-file-failed-with-exitcode

The batch or application returned an error code other than "0"

import-add-threshold-exceeded

The import add threshold exceeds the configured setting

import-update-threshold-exceeded

The import update threshold exceeds the configured setting

import-delete-threshold-exceeded

The import delete threshold exceeds the configured setting

export-add-threshold-exceeded

The export add threshold exceeds the configured setting

export-update-threshold-exceeded

The export update threshold exceeds the configured setting

export-delete-threshold-exceeded

The export delete threshold exceeds the configured setting

threshold-exceeded

A threshold is exceeded

process-exception

The batch or application file could not be started or has a unknown exception occurred

stopped\aborted

The stop function is executed, this will occur when you have pressed the stop button while the sequencer was still running.

agent-missing-or-unavailable

The ILM/FIM Agent that has been configured is not or no longer available.

disabled

The step is disabled

no-sync-data-available

There where no pending import objects to be synchronized and the option "Run even if no import data is available to be synchronized"
is enabled.

no-export-data-available

There where no pending export objects to be exported and the option "Run even if no export data is available to be exported"
is enabled.

filter-incomplete

The custom filtering is enabled but there is error in receiving the messages from the Traxion ILM Framework

success-filtered

There are no errors but the custom filtering filtered some objects, check the report for details

Result text

Explanation

completed-discovery-errors

The full import run step stopped and the data was not obsoleted because of discovery errors between the connected directory and the connector space. If an import run step returned this value, the processing of retries and cleanup of placeholder objects will not be performed.

completed-export-errors

The run step completed with export errors.

completed-no-objects

The full import run step found nothing to import.

completed-sync-errors

The run step completed with synchronization errors or warnings.

completed-transient-objects

The run step completed with objects in the connector space in a transient state.  

completed-warnings

The run step completed with synchronization warnings.

connection-failure

The server is not running or your credentials were removed from the security groups.

in-progress

Indicates the percentage of completion for processes that are not yet complete.

no-start-bad-ma-configuration

The run step failed to start because the management agent configuration is corrupt.

Recreate the management agent to prevent this return value.

no-start-connection

The run step failed to start because of connection problems.

Verify that you are connected to the server to prevent this return value.

no-start-credentials

The run step failed to start because of credential problems.

Verify that the credentials used to execute the run profile are members of the appropriate security group.

no-start-database-permission

The run step failed to start because the account used does not have permission to access to the database or the table. Verify that the account used to run the management agent has access to the database or table.

no-start-database-schema-mismatch

The run step failed to start because the configured schema does not match the schema in the connected directory. Verify that the schemas in the connected directory and the configuration match.

no-start-database-table

The run step failed to start because the management agent is connected to the database but could not access the specified table.

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.

no-start-file-access-denied

The run step failed to start because access to the file specified in the Input file name text box of Management agent configuration in the Configure Run Profile dialog box was denied. Verify that you have access to the file.

no-start-file-code-page

The run step failed to start because the selected code page does not match the file specified in Template Input File of the management agent properties.

Use the code page that is appropriate for the input file.

no-start-file-contains-incorrect-step-type

The run step failed to start because the step requires a different type of drop file. For example, the step might require a delta-import drop file but the drop file is from a full-import step.

Verify that you are providing the correct type of drop file.

no-start-file-not-found

The run step failed to start because the file specified in Input file name text box of Management agent configuration in the Configure Run Profile dialog box could not be found.

Verify the specified input file is in the working folder of the management agent.

no-start-file-open

The run step failed because the file specified in Input file name text box of Management agent configuration in the Configure Run Profile dialog box could not be opened.

no-start-file-sharing-violation

The run step failed to start because of a sharing violation on the file specified in Input file name text box of Management agent configuration in the Configure Run Profile dialog box.

no-start-full-import-required

The delta import run step failed to start because you first need to complete a full import step.

Complete a full import step before starting a delta import to prevent this return value.

no-start-header-row-mismatch

The import run step stopped because the header row in the file did not match the configured header row.

Make the necessary modifications so that the header row in the file matches the configured header row.

no-start-ma

The run step failed to start because of an unknown management agent error.

no-start-no-domain-controller

The run step failed to start because the domain controller could not be contacted by the server.

Verify that the domain controller is connected to the network.

no-start-unknown-profile-name

Could not execute management agent because the name of the profile passed as a parameter to the Execute call is unknown.

stopped-connectivity

The run step stopped because of connectivity loss.

Restore connectivity to the server.

stopped-error-limit

The run step stopped because the run profile reached the error limit. The errors appear in Synchronization Errors in Identity Manager. Resolve these errors.

stopped-extension-dll-exception

The run step stopped because of an exception in the either the IMASynchronization.Initialize or IMVSynchronization.Initialize methods.

Check the event log for the assembly name and the exception call stack. Resolve the exception in the method.

stopped-file-error

The run step stopped because the program could not write to the file.

stopped-ma

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

stopped-parsing-errors

The run step stopped because the program could not parse the specified file or Sun ONE Directory Server 5.1 change log.

stopped-server

The run step stopped because of an unknown server error. Resolve the server error.

stopped-user-termination-from-wmi-or-ui

The run step stopped because the user stopped running the run profile.

success

The operation completed with no errors.