Entity

Failure

How to Recover

All

During name conflict resolution, a new name was entered for the entity in the local environment with a name that already exists in the local environment.

Run the wizard again and select a name that does not exist in the local environment.

There was a change in the entity in either the source or local environment between the time it was selected for transfer and the time it is actually transferred.

Retry the transfer.

Contract

The contract contains registrations to metrics in other contracts that their version was not committed yet.

Either delete the registrations (involves creation of a new version and commit) or commit the other contract version.

The contract contains registrations to metrics in other contracts that their contract is in status Archived.

Either delete the registrations (involves creation of a new version and commit) or Un-archive the other contract.

The contract already exists in the local environment with an uncommitted version

Delete the contract version in the local environment.

The contract already exists in the local environment, but in status Archived.

Un-Archive the contract in the local environment.

There is a contract that was not committed yet in the local environment with the same name.

Change the name of the contract with the same name.

The contract from date is prior to the purge date line in the local environment.

NA

The contract contains metrics with metric types and in contract sections that do not exist in the local environment.

Run customization scripts to create the relevant sections and metric types in the local environment to fit the definition in the source environment.

There is a mandatory contract custom attribute in the local environment that is not defined in the source environment or defined as optional.

Change the custom attribute in the local environment to be an optional attribute.

The contract was transferred to the local environment in Pending status and then the user performed “Undo Commit” in the source environment.

If the last version on the local environment is in Pending status, perform “Undo Commit” on the version in the local environment and delete the version.

If the last version on the local environment is in Effective or Not Effective status, purge the contract from the local environment.

Any other unexpected failure that is caused by a temporary problem (e.g. database went down in the middle of the transfer) or a problem that its solution is unknown.

Either purge the contract in the local environment or delete the last uncommitted version of the contract in the local environment.

The contract contains quick metrics.

NA

The contract contains a registration to a metric in another contract that also contains a registration to the contract you wish to transfer.

An error pops up when clicking the next button in the content transfer wizard after selecting the contract to be transferred.

Business Logic Module

The business logic module is in Pending status.

This can happen if the business logic module was created and was in Effective status and a new version was created and committed, but was not yet changed to Effective by the background process.

Wait until the background process changes the status from Pending to Effective.

The business logic module is in status Pending in the local environment.

Wait until the background process will change the status from Pending to Effective.

There is a new version for the business logic module in Preliminary status in the local environment.

Either delete the preliminary version or commit it.

Any other unexpected failure that is caused by a temporary problem (e.g. database went down in the middle of the transfer) or a problem that its solution is unknown.

Delete the business logic module or its uncommitted version.

Report

There is a loop due to related reports definition. For example, report A is related to report B which is related to report C which is related back to report A

An error pops up when clicking the next button in the content transfer wizard after selecting the report to be transferred.

Resource, Resource Group

There is a mandatory resource or resource group custom attribute in the local environment that is not defined in the source environment or defined as optional.

Change the custom attribute in the local environment to be an optional attribute.

The resource or resource group exists in the local environment and has uncommitted change.

Commit the change or delete the uncommitted change.

Name conflicts between resource and resource group are not picked up by the content transfer wizard. For example, if a resource group in the source environment has the same name as a resource in the local environment, there would be an error within the transfer.

Manually rename the resource or resource group in the local environment.

There is a resource or resource group that was not committed yet in the local environment with the same name.

Change the name of the resource or resource group with the same name.

Contract Party, Contract Party Group, Service, Service Group, Resource, Resource Group

Name conflicts between entity and entity group are not picked up by the content transfer wizard. For example, if a contract party in the source environment has the same name as a contract party group in the local environment, there would be an error within the transfer.

Manually rename the entity in the local environment.

Event Type

Transfer changes to event type that is already in use in the local environment by a metric or alert profile fail.

NA

Contract Party, Contract, Service Domain, Domain category, Report Folder, Report

For entities in which the name uniqueness is in the scope of its parent entity, name conflict is displayed only in the level of the parent entity. If the user selects to Link&Overwrite, the job fails on name conflict in the level of the child.

Retry the transfer by running the wizard again and resolve the name conflict that is displayed for the child entity.