Skip to main content

Error E00640009

Thread needs solution

I have recently moved our Acronis software (Snap Deploy Build 3329) to a virtual server and all appears to be working well apart from re-using a template. I can create a template and use it to deploy an image successfully, but if I want to return to that template and edit it to use a new image for example, I get the "Error E00640009. Failed to load archive file in the template" message. We currently hold the images on a shared network drive, rather than the virtual server.

0 Users found this helpful

Hello Heath,

Thank you very much for your post. I will do my best to assist you.

We have no known issues such as this and at the moment we need additional information please.

For troubleshooting purposes, do you think you can try reproducing it with the image located on an internal hard drive, so that we can eliminate any network problems. Are all the templates created with the current version of Snap Deploy 3 build 3329 that you are running?

Just in case, if you need immediate assistance, you can always contact our support directly.

Please let me know if you have additional questions.

Thank you.

Hi Anton,
We had an older version of Acronis on a physical machine, but when we started virtualizing our servers I downloaded the latest updated version of Snap Deploy (3329) and installed it on a vanilla virtual server. I created new templates still using images stored on the original physical server. I could use these new templates once created and with image attached, but once an image had been rolled out I couldn't then return to edit that template.
I did copy one of these images to the virtual server, and could then edit the template, however, as your pdf states,

"Acronis OS Deploy Server can deploy images located:
- in network shared folders
- on the deploy server internal hard drive
- on USB and FireWire (IEEE-1394) storage devices (hard drives, flash drives) attached to the
deploy server
- on DVD+R/RW, DVD-R/RW, CD-R/RW loaded in the deploy server media drive."

So I'm still puzzled.

Hello Heath,

Thank you for replying.

First of all, you are correct, deployment of images stored in network shared folders is supported by Acronis Snap Deploy 3. Since the initial deployment of images works, it appears this can be related either to an unknown issue with our software or specific network shared folders settings.

We will need to investigate this further and I would suggest to submit a support request so that we can fix the problem.

However, can please check several things so that we have a full picture of your environment.

1. When editing the template and selecting a new image, do you select the same network share or a different one on the same computer? Or it is a totally different network share on another computer?

2. Do you get any credentials prompts when selecting an image file during template editing?

We may have to send this issue to our Testing Lab so that we can try and reproduce this problem.

If you need additional help or any other issues, please let me know.

Thank you.

I've been having the exact same issue. So I've been trying to figure out where the templates are stored by default. Any help would be much appreciated.
Thanks!
Jenn

Hello Jennifer,

Thank you for posting and welcome to the forum. I will definitely assist you.

The templates are stored by default in this folder, depending on the OS, for example XP, that would be here:

C:\Documents and Settings\All Users\Application Data\Acronis\DeployServer\Configs

Please let me know if you have additional questions.

Thank you.

Hi there, we've been having the same issue - with an image stored on a network share, we can deploy it once, but we get "Error E00640009. Failed to load archive file in the template" message when we try to use the template again.

We can only use the template again by rebooting the machine running the Snap Deploy Management Console. (restarting management console does not solve the problem.)

Templates that are referencing image files stored on a local drive work fine.

Was the original poster's problem fixed in the end? What was the solution?
I assume it was something to do with network shares?