Corrupted snapshot file

Symptoms

Error message

or

or this exception:

java.lang.IllegalStateException: Unable to find model version in file /cust/app/jira/temp/activeobjects.xml860047787519460231snapshot.tmp.xml
at com.botronsoft.jira.rollout.model.util.EcoreCustomUtil.getModelVersion(EcoreCustomUtil.java:92)
at com.botronsoft.jira.rollout.model.migration.impl.ModelMigrationServiceImpl.migrate(ModelMigrationServiceImpl.java:138)
at com.botronsoft.jira.rollout.impl.ModelLoader.loadModel(ModelLoader.java:50)
at com.botronsoft.jira.rollout.impl.JiraConfigurationResourceServiceImpl.loadModel(JiraConfigurationResourceServiceImpl.java:36)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

Cause

Failures in EcoreCustomUtil.getModelVersion are caused by uploads of a non-snapshot file or a corrupted one (via incorrect manual modification or due to a problematic transfer/download).

Resolution

1. Ensure the file type is correct (zip, xml, bin). CMJ expects a zip archive. Configuration-only snapshots could also be deployed as a single xml or bin file.

2. Make sure you're uploading a valid snapshot file that is not incorrectly manually edited or in any other way corrupted (copying snapshots between VMs or downloading very large files is a common cause for this).

3. Try to download the snapshot file again. If the file is with a bigger size you could choose to exclude the attachments as described in this wiki page: Moving attachments.
4. If the problem persists validate the integrity of the ZIP file (the actual steps depends on the operating system of the client machine).
5. Search the atlasian-jira logs for error details (stacktrace is logged).
6. See this article to find out what is packaged in a snapshot.
7. Other workarounds:

• •  Downloading the snapshot directly from the source Jira server, they are located in %JIRA_HOME%\export\snapshots.
  •  Also, it's possible to use application links and deploy the snapshot directly from the source instance, this way CMJ handles the transfer.

Manual editing of the snapshot

If you do need to edit the snapshot manually:

• Convert the snapshot files to xml from CMJ's advanced menu
• Carefully modify the xml file contents. This is not encouraged, as it may easily lead to deployment errors. We cannot provide assistance for issues with edited snapshots.
• Zip the snapshot folder.
• Make sure not to change the original snapshot file structure.

Need help?

If none of the tips above help, contact our support team at Appfire's Support Portal. Attaching a support zip from the target instance and the snapshot will help our support team a lot.

Related KB article

Moving attachments