Import failure, or issues after import

Generally, export files are backward compatible, but you may encounter an issue when importing export files from prior versions of Deployment Automation.

This table includes some examples of the types of errors and ways to resolve them.

Error Type Resolution
You receive an error when you try to import environments that were exported from a prior version of Deployment Automation. Upgrade the primary Deployment Automation server and export the objects again. You can then import them into a target server of the same version.

You cannot import an application from a json file because it was exported while using a different plugin version than the one you have.

For example, you receive an error similar to "Plugin DA Versioned File Storage Version 20 does not exist."

You can use the resolution in the earlier entry.

Or you can edit the exported application json file and try to import again. Open the json file in a text editor and change all occurrences of pluginName and pluginVersion to the name and version of the plugin you have loaded.

In this example, you could change pluginName to DA Versioned File Storage and pluginVersion to 20.

Your import seems to work, but when you try to deploy, you receive a generic run error. This means the structure of the application may have been imported incorrectly.

For example, if you can deploy at the component level but not the application level. There is a structure mismatch in the imported files.

Typically, you can fix this issue by removing and readding the component to the application.