ImportExport Messages

During export and import, access to the registry layer of CentraSite is required. The call to the registry layer of CentraSite has failed.

Please contact your software supplier.

The archive file is used to store the registry objects for export and import. The access to this archive file has failed.

Please make sure that the archive file name is correct and you have sufficient access rights to access this file.

The archive file is used to store the registry objects for export and import. The closing of this archive file has failed.

Please make sure that the archive file has not been removed meanwhile.

Referenced object cannot be resolved, neither from the import set nor by existing objects.

Add the referenced object.

The import of the registry object has been rejected, because the timestamp of the existing registry object is newer than the timestamp of the import registry object. You can set the replace option of the import operation to overwrite the existing registry object with an older import object.

You can set the replace option of the import operation to overwrite the existing registry object with an older import object.

The import object refers to the specified invalid object, and thus cannot be imported either.

Check why the referenced object is invalid by analyzing its error message.

The existing object contains an embedded object which is not defined in the object to be imported. This embedded object is referenced by another object either directly or through one of its embedded objects.

Please add the missing object and try importing the object.

Specified resource could not be found. It may have been previously deleted.

No action required.

The user wants to access or write an object for which the user has no privileges.

The action must be performed by a more privileged user.

The user wants to modify an object for which the user has no modify privileges.

The action must be performed by a more privileged user.

A connection to the database cannot be established.

Check whether the URL is correct.

The database connection has been lost and cannot be closed.

Please contact your software supplier.

The registry object should have been deleted after the export, but the deletion has failed.

Please contact your software supplier.

The registry object carries information about valid target registries. This information is called the lifecycle stages of the particular lifecycle state of this registry object. This registry object thus can only be imported into matching target registries.

The registry object can be imported into matching target registries only.

The user registry object already exists.

No action required.

The group registry object already exists.

No action required.

The update of the security information has failed.

Please contact your software supplier.

The import archive must contain a file named MANIFEST.TXT which contains the compatibility level of the import archive. The compatibility level of the import archive must be the same as the compatibility level of the CentraSite version used.

Use the same CentraSite version for exporting and importing.

The lookup of this key in the registry was not successful.

Please provide a valid import organization key.

The provided key exists in the registry, but the referred object is not an organization object.

Please provide a valid import organization key.

During import, the setting of the import organization has failed.

Please contact your software supplier.

The option delete after export has been set and the deletion of a repository resource has failed.

Please contact your software supplier.

The option delete after export has been set and the query to find all external links with the same URI has failed.

Please contact your software supplier.

The delete after export option is active and the policy is to be deleted after export. The collection of the registry objects belonging to the policy has failed.

Please contact your software supplier.

Role objects cannot be replaced.

Re-establish the organization's roles.

Permission objects cannot be replaced.

Re-establish the organization's permission.

The user has not enough permission to create or update an asset type.

Check the roles of the user.

You can only import an organization together with its users, groups, roles and permissions. However, if the organization already exists, then it is possible to just import an organization without its users, groups, roles and permissions.

Export the organization with the option to include users, groups, roles and permissions.

An asset type cannot be imported or updated because of an internal registry problem.

View the internal error reason and the stack trace in the log.

The asset type cannot be replaced because the layout of the importing type is incompatible with the exisiting one.

View the stack trace for the details.

A reference from the asset type to be imported is not in the registry. This is usually a referenced asset type and must be present. Due to internal reasons the import cannot continue.

Check that the referenced object (asset type) is present in the target registry.

The asset does not match the asset type. Possibly the asset has an attribute which is not defined for the given asset type.

Check the asset type for missing attributes. Import the asset type which matches the asset.

No selective import is possible, only importing the whole archive is supported.

Do not select particular keys.

The requested user name was not found in the registry.

Use a valid user name.

The schema file of an asset type cannot be imported because the asset type itself will be rejected for another reason.

Analyze the existing asset type.

The given asset type cannot be replaced because it would change or remove used information, e.g. attributes.

Check the attributes of the existing asset type. There are assets with attributes which would be removed by the import.

The repository document will not be imported because its parent object (e.g. an ExternalLink object) was rejected.

Check why the parent object was rejected.

The given object cannot be replaced, because the object that is already present has an attribute which would disappear as a result of the replacement. This attribute is referenced by others, therefore the attribute must be kept.

Check the existing object and its references.

The user has no privilege to update an object, present in the archive, to the registry. This could happen when updating asset types or taxonomies.

Check if you can import the archive as a user with more privileges.

The asset type to be imported has a lower version number than the one in the registry. The type is incompatible to the registry and therefore a replacement would destroy relevant information.

The asset type from a previous version cannot be imported.

The object to be imported already exists with the same timestamp.

No action required.

The registry object to be imported already exists and has been replaced.

No action required.

The registry object to be imported has been created.

No action required.

The option delete after export has been set and the registry object has been deleted after the export.

Please contact your software supplier.

The import of the document has been rejected, because the timestamp of the existing document is newer than the timestamp of the import document. You can set the replace option of the import operation to overwrite the existing document with an older import document.

You can set the replace option of the import operation to overwrite the existing document with an older import document.

The import document and the existing document have the same timestamp. No import is necessary.

No action required.

The option delete after export has been set and the registry object has been deleted after the export.

No action required.

The target object is not in the export set.

Before importing, the referenced (target) objects must be present in the registry.

The document, which contains executable code, is not imported because it is already present.

No action required.

The object cannot be replaced because the root object was not imported.

No action required.

Embedded objects like Classification, AuditableEvent, ExternalIdentifier, ServiceBinding, SpecificationLink and Association cannot be exported.

Deselect object from list of objects to be exported.

Export of selected object does not find any objects to be exported.

Remove object from list of objects to be exported.

A referenced object is not selected for export. Therefore there might be problems at import.

Check your associated objects and decide whether to add them to the export.

The deletion of one or more registry objects has failed during the export with delete option. The export archive however is complete.

See the reason for the rejection within the message.

A referenced object is not selected for export. Therefore there might be problems later when you try to import the archive.

Check your associated objects and decide whether to add them to the export.

It is currently not supported to delete specified object with the delete-after-export function.

Delete the object manually.

The user cannot be deleted from an organization after import because this user is already in use.

Clean up the user manually with the imported organization.

The association to an unreferenced target object was removed from the object.

Check the object and repair it if necessary.

An exported object has a reference to an object that the user has no privilege to access. This means for import that the referenced object must be present and the importing user must have privileges to access this object.

Keep this situation in mind for a later import.

Due to resolving an access violation situation, it may happen that asset types may be corrupted.

Import the archive as CentraSite Administrator.

The association to the given object has been removed during import because the target object is not present.

Re-establish the removed association if possible.

The classification has been removed from the object because its concept is not present in the registry.

Re-establish the classification if possible.

An external link reference which does not exist for the object has been removed.

Check if the external link can be re-inserted manually.

The object has a lifecycle state at import, however the associated lifecycle model is not present in the target registry.

Import the lifecycle model first.

The import processing detected an invalid user element and ignored the import.

Verify the user entry in the archive.

The object given contains a reference to an object which cannot be exported because the user has no privilege of that object. Only the reference gets exported. At import, this reference is checked and possibly removed from the object if the referenced object is not present.

Check if a more privileged user should export the object.

A service binding points to a specification object, which is not present in the archive or registry. Therefore the service binding gets removed from the service.

Check the service and its specification objects.

The required object type does not exist in CentraSite.

Make sure the required object type is available in CentraSite and create an instance of it.

A required asset is not available in CentraSite.

Create the required asset.

An internal JAXR operation failed.

Retry your request.

An XPDL file does not exist in the location specified.

Make sure the given XPDL file is in the specified location.

The XPDL file does not match the XPDL format.

Make sure the given XPDL format is valid.

It is not possible to establish a connection to the CentraSite database.

Make sure the CentraSite database URL and CentraSite user credentials are valid.

The given XPDL file is not supported by CentraSite. CentraSite supports only XPDL 2.x.

Make sure the given XPDL version is 2.x.

There is no process with the specified asset ID

Check the asset ID provided in the request

While parsing the XPDL file, a pool element has been found but the attribute "id" is missing.

Please make sure the specified XPDL file is valid.

While parsing the XPDL, a transition element has been found but the "from reference" is missing in the transition element.

Please make sure the "from reference" element contains a proper value.

While parsing the XPDL, a transition element has been found but the "to reference" is missing in the transition element.

Please make sure the "to reference" element contains a proper value.

While parsing the XPDL, a transition element has been found but the "id" is missing in the transition element.

Please make sure "id" is present in the transition element and contains a proper value.

While parsing the XPDL, a lane element has been found but the "id" is missing in the transition element.

Please make sure the "id" is present in the lane element and contains a proper value.

While parsing the XPDL, a lane element has been found but the "id" is missing in the activity element.

Please make sure "id" is present in the activity element and contains a proper value.