---
title: "Corrupted snapshot file"
canonical: "https://support.appfire.com/space/SUPPORT/80118134/Corrupted%20snapshot%20file"
format: markdown
---
### Symptoms


#### Error message

![image](media://253241ea-eb6c-4ccd-a879-7c10552ca61c)

or

![image](media://152f9f8d-e9ce-4051-99dd-aca58fc0d24b)

#### or this exception:


```java
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

<span style="color: #212121">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).</span>

### 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](https://apps.appf.re/dc/cmj/doc/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](https://appfire.atlassian.net/wiki/spaces/CMJ/pages/657692189).
7. Other workarounds:

> Macro (legacy-content)

#### 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](https://apps.appf.re/sfjsdc/support/portal). Attaching a [support zip](https://confluence.atlassian.com/support/create-a-support-zip-790796819.html) from the target instance and the snapshot will help our support team a lot.

### Related KB article

[Moving attachments](https://apps.appf.re/dc/cmj/doc/Moving+attachments)