An existing scope named "{0}" already exists in the workflow server. Use the -Force parameter to overwrite the existing scope. When using -Force, if another SharePoint farm was registered using this scope, that farm may not be able to continue working with the workflow server unless re-registered under another scope name.
An existing LobSystem (External System) with Name '{0}' already defines an Entity (External Content Type) with Namespace ...
An existing LobSystem (External System) with Name '{0}' already defines an Entity (External Content Type) with Namespace ...
An existing request to enable the Enterprise feature is in progress. To check the status of this request, go to the Timer ...
An existing request to upgrade from Oem to Enterprise is currently being processed. To check the status of this request, ...
An existing scope named "{0}" already exists in the workflow server. Use the -Force parameter to overwrite the existing scope. ...
An expiration schedule set on the Document or Item content type cannot be based off of a system generated property such as ...
An expiration timer job is currently running. It may take awhile before all of your expired items are processed, depending ...
An export named '{0}' already exists at this location, and is ineligble for resume. Please choose a different location, or ...
An external content type which has the same name and namespace with the current external content type has been created in ...