Salta al contenuto principale

Error code when deploying, after upgrade to 1656

Thread needs solution

I am getting this error code when deploying after i have upgraded to 1656.

What to do ?

Cannot deserialize the object due to its meta info inconsistency. It is possible that the versions of the product’s components are incompatible with each other or that the object was created by an incompatible version.

    Error code: 0x9C0002
    $module = "patcher_remote_vs_1656"
    Tag: 0x7E90832CFF02937A

0 Users found this helpful

I have exactly the same error.  I spent about 90 minutes on a call with Acronis support yesterday and I am waiting for them to get back to me.  I've just tried completely uninstalling and re-installing the very lastest version to no avail.

Same Issue here.

If you got a Backup try rerolling files to "C:\Program Files (x86)\Acronis" (Standard Path) and overwrite the new files. This worked for me, the first Deployment is running (with old Version 1416). If you have to reinstall ASD5 completely try moving this Folder and the second Acronis Folder (C:\ProgramData\Acronis). Be carefull these Folders contain all the Logs and Data from the License Server and so forth.

This seems to be a major Problem with the new Version, so this should not be made public.

Hello,

The issue has been tested and was not reproduced on our environment. 

Can you please give some clarifications?

1. What Windows version do you use?

2. The previous build installed on your system was 1416, right?

3. Did you use  "Typical" or "Custom" installation of the previous build?

4. Was it installed to the default location ("C:\Program Files (x86)\") or custom location (e.g. other disk/volume/folder)?

5. Did you update all components of Acronis Snap Deploy?

6. Did you use PXE server to deploy target machines? Make sure that all components of Snap Deploy were reuploaded to PXE.

 

Best regards.

1. Windows Server 2008R2 

2. previously Build 1416 had been installed and was running fine (except some known minor Bugs)

3. Install Method of Build 1416 should have been "Typical"

4. Due to the typical Installation C:\Program Files (x86)\ is the Path for the ASD5 Installation 

5. With Build 1656 all Components had been updated, alswo the PE Parts within ASD5. The Server had been restarted. 

6. The Client had been booted via PE Boot, Image Deployment was not possible to the Bug described above. 

 

I am getting the same error. My deploy server and management console are an HP tower with Win 7 Pro 64 bit. I did typical install when I installed the new version. I tried to deploy an image today and get the same error message. I have the checkbox to use PXE checked. I was going to do a uninstall/clean reinstall but I do not want to lose all my settings, templates et cet and I see no option in Snap Deploy to backup configuration.

The realy important Files (Licensing Server & Templates) are located in C:\ProgramData\Acronis\DeployServer\Configs / C:\ProgramData\Acronis\License Server. In general you can find alle the importand Data in C:\ProgramData\Acronis (like Logs etc.).

So making a copy of this is always good. If i`m right an uninstallation of ASD5 does not impact this Folder, so this might be a way to get back to 1416 if you need the ASD up and running soon. Otherwise you will have to wait untill this Issue is fixed. 

Cause this is not the first time with minor or major Issues after an Update i am running automatic Backups every Day, so that i can reroll the ASD Program Files easily. 

1. What Windows version do you use?

Windows 7

2. The previous build installed on your system was 1416, right?

Yes 1416

3. Did you use  "Typical" or "Custom" installation of the previous build?

Typical

4. Was it installed to the default location ("C:\Program Files (x86)\") or custom location (e.g. other disk/volume/folder)?

Yes default folder used

5. Did you update all components of Acronis Snap Deploy?

Yes all updates are updated

6. Did you use PXE server to deploy target machines? Make sure that all components of Snap Deploy were reuploaded to PXE.

I am not using PXE, i am using USB keys and they have been updated.

I think, I've found the reason. There is an old issue (ticket ASD-2923) related to the Default template settings. If the default template settings have been configured on b1416, then it is impossible to create a deployment template after update to b1656.

Please try to remove the file DefaultOptions.xml from the folder C:\ProgramData\Acronis\DeployServer\Settings

All should work after that (Note: Default deployment options that were configured on the previous build will be lost after deleting the above file).

Best regards.

I just upgraded to 5.0.1, 656 and had this same issue.
Deleting the DefaultOptions.xml file worked for me.
Thanks!

I had to uninstall the program completely including hidden folders within ProgramData. Reinstalled and it works now.

do you have a list of what i need to uninstall / delete... i'm kinda in a real pickle with this... 

Uninstall Snap Deploy in Control Panel. Reboot. Go to C:\Program Files X86 and make sure the Acronis folder is gone, if not delete it. Show hidden folders in Windows Explorer and delete the Acronis folder if it is still there. Reinstall Snap Deploy using the latest 656 vers. Also, just an fyi, I had to re-create all my deployment templates. Not a huge deal. You also have to reimport machine licenses.

Rebooting the fileserver is not as easily done as said... wish they would do a better job on stuff like this before releasing it... if upgrading isn't going to work they should build in the uninstal into the new install... 

templates aren't huge... but the license thing might be... 

Yea, sorry man. Luckily for me I have a Windows 7 standalone workstaion that acts as my Snap Deploy server. I agree, I am surprised it broke existing installations.

Rick Peterson wrote:

do you have a list of what i need to uninstall / delete... i'm kinda in a real pickle with this... 

Hello, Rick

It is not necessary to delete/uninstall the whole product to fix this issue. Please have a look at my above comment.

Best regards.