WMI Provider Return Strings

Article
01/10/2011

This topic defines the common return values for methods, properties, and XML elements.

The following return values are common to all Windows Management Instrumentation (WMI) provider methods.

Return Code	Description
call-failure	An unexpected error occurred. Check the event log for more information.
connection-failure	This error is returned when you successfully obtain a WMI object, but either the service was stopped, or your security identity was removed from the security groups that have rights to use the WMI interface (administrators, operators, password set, and browse).

call-failure

An unexpected error occurred.

Check the event log for more information.

connection-failure

This error is returned when you successfully obtain a WMI object, but either the service was stopped, or your security identity was removed from the security groups that have rights to use the WMI interface (administrators, operators, password set, and browse).

The return values that are listed in the following table are common to the following methods, properties, and XML elements:

Execute Method
RunStatus Method
RunStatus Property
<step-result> element of the <run-history> XML string

Return Code	Description
completed-discovery-errors	The full import run step stopped and the data was not obsoleted because there were discovery errors between the connected directory and the connector space. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
completed-export-errors	The run step completed with export errors. The next step in the run profile will run. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
completed-no-objects	The full import run step found nothing to import.
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. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
completed-transient-objects	The run step completed with objects in the connector space in a transient state. For more information about the transient state, see "The metaverse and the connector space" in the Forefront Identity Manager Synchronization Service 2010 on-the-box on-the-box Help. The next step in the run profile will run, and data will be obsoleted. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
completed-warnings	The run step completed with synchronization warnings. The next step in the run profile will run, and data will be obsoleted. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
completing-obsoletion	The system is in the process of marking objects in the connector space that no longer exist in the connected data source as obsolete. You can view the progress of this process by using the in-progress value.
completing-referential-updates	The system is in the process of completing its referential updates. You can view the progress of this process by using the in-progress value.
connection-failure	The server is not running, or your credentials were removed from the security groups. Verify that you are a member of a Forefront Identity Manager Synchronization Service (FIM Synchronization Service) security group. The method can return this string after you obtain the WMI provider object.
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 corrupted. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Re-create the management agent to prevent this return value. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
no-start-change-log-not-enabled	The delta import run step failed to start because the change log in the Sun ONE Directory Server 5.1 (formerly iPlanet Directory Server) was not enabled. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Enable the change log in the server to prevent this return value. For more information about enabling the change log, see the Sun ONE Directory Server 5.1 documentation. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
no-start-connection	The run step failed to start because of connection problems. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Verify that you are connected to the server to prevent this return value. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
no-start-credentials	The run step failed to start because of credential problems. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Verify that the credentials that are used to execute the run profile are members of the appropriate security group. For more information about Forefront Identity Manager Synchronization Service 2010 security groups, see "Using security groups" in the Forefront Identity Manager Synchronization Service 2010 on-the-box Help. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
no-start-database-permission	The run step failed to start because the account that was used does not have permission to access the database or the table. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Verify that the account that was used to run the management agent has access to the database or table. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
no-start-database-schema-mismatch	The run step failed to start because the configured schema does not match the schema in the connected directory. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Verify that the schemas in the connected directory and the configuration match. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
no-start-database-table	The run step failed to start because the management agent is connected to the database but cannot access the specified table. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up.
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. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up.
no-start-file-access-denied	The run step failed to start because access to the file that is specified in the Input file name text box in Management agent configuration in the Configure Run Profile dialog box was denied. Verify that you have access to the file. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
no-start-file-code-page	The run step failed to start because the selected code page does not match the file that is specified in Template Input File of the management agent properties. The next step in the run profile will not run and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Use the code page that is appropriate for the input file. For more information about specifying the code page, see "Select a template input file" in the Forefront Identity Manager Synchronization Service 2010 on-the-box Help. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
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 that is specified in the Input file name text box in Management agent configuration in the Configure Run Profile dialog box could not be found. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Verify that the specified input file is in the working folder of the management agent. For more information about specifying the input file that is used by a run profile step, see "Example: Running a Management Agent With a Specified Run Profile" in the Forefront Identity Manager Synchronization Service 2010 on-the-box Help. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
no-start-file-open	The run step failed because the file that is specified in the Input file name text box in Management agent configuration in the Configure Run Profile dialog box cannot be opened. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
no-start-file-sharing-violation	The run step failed to start because of a sharing violation on the file that is specified in the Input file name text box in Management agent configuration in the Configure Run Profile dialog box. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Verify that Forefront Identity Manager Synchronization Service 2010 is the only program that is using this file. If it is not, close all other programs. If this string is the value for the RunStatus Method, no run step is currently running, but a run step was run in the past.
no-start-full-import-required	The delta import run step failed to start because you first need to complete a full import step. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Complete a full import step before you start a delta import to prevent this return value. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
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. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
no-start-no-domain-controller	The run step failed to start because the domain controller could not be contacted by the server. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Verify that the domain controller is connected to the network. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
no-start-no-partition-delete	The run step failed to start because domain or naming context has been deleted. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Verify that the specified partition still exists. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
no-start-partition-not-configured	The run step failed to start because the required partition is not selected in the Configure Directory Partitions dialog box of the management agent properties. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Verify that the appropriate partition is selected. For more information, see "Configure directory partitions" in the Forefront Identity Manager Synchronization Service 2010 on-the-box Help. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
no-start-partition-rename	The run step failed to start because the selected partition in the Configure Directory Partitions dialog box of the management agent properties was renamed. Verify that the appropriate partition is selected. For more information, see "Configure directory partitions" in the Forefront Identity Manager Synchronization Service 2010 on-the-box Help. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
no-start-server	The run step failed to start because of an unknown server error. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up.
no-start-unknown-profile-name	Could not execute management agent because the name of the profile that was passed as a parameter to the Execute call is unknown.
stopped-bad-ma-configuration	The run step stopped because of a corrupted management agent configuration. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Verify that your management agent is configured correctly. For more information about configuring your management agent, see “Configure Management Agents” in the Forefront Identity Manager Synchronization Service 2010 on-the-box Help.
stopped-change-log-out-of-order	In some cases, the Sun ONE Directory Server writes a change log (used for delta imports) using entries that are not numbered sequentially. To fix this problem, run a full import before you do more delta imports.
stopped-code-page-conversion	The import run step stopped because of a code page conversion error. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Verify that you are using the appropriate code page for the template input file. For more information about setting the code page, see "Select template input file" in the Forefront Identity Manager Synchronization Service 2010 on-the-box Help. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
stopped-connectivity	The run step stopped because of connectivity loss. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Restore connectivity to the server. If this string is the value for the RunStatus Method, no run step is currently running, but a run step was run in the past.
stopped-database-connection-lost	The run step stopped because the server is not connected to the Microsoft SQL Server database that is used by the Forefront Identity Manager Synchronization Service 2010 server. This value occurs if the server stores the metadirectory on a separate computer that is running SQL Server. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Resolve the connection problem.
stopped-database-disk-full	The run stopped because the SQL Server database that is used by the Forefront Identity Manager Synchronization Service 2010 server is full. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Create some space in the SQL Server database.
stopped-deadlocked	The run step stopped because of an internal server deadlock between multiple management agent runs. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value retries are not processed, and placeholder objects are not cleaned up. Resolve the deadlock.
stopped-disk-full	The run step stopped because of a full disk. Create space on the disk. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Create space on the disk. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
stopped-error-limit	The run step stopped because the run profile reached the error limit. The errors appear in Synchronization Errors in the Synchronization Service Manager. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Resolve these errors. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
stopped-export-write	The export run step stopped because of an error writing to the connected directory. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Verify that the server is connected to the network and has write access to the connected directory. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
stopped-extension-dll-access	The run step stopped because the Forefront Identity Manager Synchronization Service 2010 service account does not have the required permissions to access the Extensions folder. The next step in the run profile does not run, and data is not obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Verify that the Forefront Identity Manager Synchronization Service 2010 service account is in the Security tab in the properties of the Extensions folder. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
stopped-extension-dll-ambiguous	The run step stopped because the rules extension contains multiple implementations of the IMASynchronization interface or the IMVSynchronization interface. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Verify that the rules extension contains only a single implementation of the IMASynchronization interface or the IMVSynchronization interface. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
stopped-extension-dll-exception	The run step stopped because of an exception in either the Initialize method or the Initialize method. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Check the event log for the assembly name and the exception call stack. Resolve the exception in the method. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
stopped-extension-dll-file-not-found	The run step stopped because the specified assembly name cannot be found. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Check the event log for the assembly name that the server was trying to load. Then specify the correct assembly name in Properties, in the Configure Rules Extensions dialog box of the management agent, or in Configure Rules Extensions on the Metaverse Rules Extensions tab to prevent this return value. For more information, see "Configure rules extensions" for management agent rules extensions, or "Configure provisioning for metaverse rules extensions" in the Forefront Identity Manager Synchronization Service 2010 on-the-box Help. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
stopped-extension-dll-instantiation	The run step stopped because the constructor method in the rules extension threw an exception. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Resolve the exception. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
stopped-extension-dll-invalid-assembly	The run step stopped because the specified assembly name is not a valid Microsoft .NET Framework assembly. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Check the event log for the assembly name that the server was trying to load, and verify that the specified assembly is a .NET Framework assembly. For more information about specifying the assembly name, see "Configure rules extensions" for management agent rules extensions or "Configure provisioning" for metaverse rules extensions in the Forefront Identity Manager Synchronization Service 2010 on-the-box Help. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
stopped-extension-dll-load	The run step stopped because the specified assembly name cannot be loaded because of an unknown error. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Check the event log for the assembly name that the server was trying to load. If this string is the value for the RunStatus Property, no run step is currently running, but a run step has been run in the past.
stopped-extension-dll-missing-dependency	The run step stopped because the extension object cannot be instantiated because the rules extension is missing a dependency file. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Verify that all files that the rules extension requires are installed and registered on the server. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
stopped-extension-dll-no-implementation	The run step stopped because the class that is implementing the IMASynchronization interface or the IMVSynchronization interface cannot be found in the specified assembly name of the rules extension. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Check the event log for the name of the rules extension that is being used, and verify that the rules extension implements the required interfaces. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
stopped-extension-dll-not-configured-for-ma	The run step stopped because the specified assembly name is not a management agent rules extension. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Check the event log for the name of the management agent that is being used, and verify that the specified assembly name in Configure Extensions of the management agent Properties dialog box is a management agent rules extension. For more information about specifying the assembly name for a management agent, see "Configure rules extensions" in the Forefront Identity Manager Synchronization Service 2010 on-the-box Help. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
stopped-extension-dll-not-configured-for-mv	The run step stopped because the specified assembly name is not a metaverse rules extension. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Verify that the name that is specified in Assembly name in the Configure Extension tab of the Configure Extensions dialog box is a metaverse rules extension. For more information, see “To enable metaverse rules extensions” in the Forefront Identity Manager Synchronization Service 2010 on-the-box Help. If this string is the value for the RunStatus Method, no run step is currently running, but a run step was run in the past.
stopped-extension-dll-updated-version	The run step failed because the Extensions folder was updated when the run step executed. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Do not add, delete, or modify any files in the Extensions folder while you are running a management agent run profile. Modify the files in this folder only after you run a management agent run profile. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
stopped-file-embedded-nulls	The import run step stopped because the file contains embedded null characters. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Remove the embedded null characters, and restart the run profile.
stopped-file-error	The run step stopped because the program could not write to the file. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
stopped-import-read	The import run step stopped because of a read error on the connected directory. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Verify that the server is connected to the connected directory and that the server has read permissions for the connected directory. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
stopped-ma	The run step stopped because of an unknown error from the management agent. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
stopped-object-limit	The run step stopped because the object limit that is specified in the Threshold text box of the Configure Step page in the Configure Run Profile dialog box. The next step in the run profile will run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Increase the object limit. For more information about increasing the object limit, see “To add or edit a step for a management agent run profile” in the Forefront Identity Manager Synchronization Service 2010 on-the-box Help. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
stopped-out-of-memory	The run step stopped because of insufficient server memory. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Increase the server memory.
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. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
stopped-server	The run step stopped because of an unknown server error. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up Resolve the server error. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
stopped-service-shutdown	The run step stopped because the Forefront Identity Manager Synchronization Service 2010 service stopped. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Verify that the service is running. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
stopped-user-termination-from-extension	The run step stopped because the rules extension threw the TerminateRunException exception to stop the run. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. Check the event log for the assembly name and the exception call stack. Resolve the exception in the method.
stopped-user-termination-from-wmi-or-ui	The run step stopped because the user stopped running the run profile. The next step in the run profile will not run, and data will not be obsoleted. If an import run step returns this value, retries are not processed, and placeholder objects are not cleaned up. If this string is the value for the RunStatus Property, no run step is currently running, but a run step was run in the past.
success	The operation completed with no errors.

Share via

WMI Provider Return Strings

See Also

Reference

Concepts

Additional resources