Update Failure with Application Deployment - Upgraded from 2.6.0.4 to 2.6.0.6 and lost instances

[Bob_Reas]

System Information

Field	Value
Operating System	Windows - Windows 11 Pro on x86_64
Product	AMPService ‘Phobos’ v2.6.0.6 (Mainline)
Virtualization	None
Application	Application Deployment
Module	ADSModule
Running in Container	No
Current State	Indeterminate

Problem Description

Issue

I upgraded from 2.6.0.4 to 2.6.0.6 and after some UI repair and recover features, I can see the instances, but they’re a generic AMP instance with no configuration. Is there any way to recover the configuration? Or at least set the instance to the appropriate application so a configuration can be re-applied?

Reproduction Steps

• Upgraded AMP
• Checked the datastores
• Clicked repair
• Instances in datastore are available, but with a default blank configuration

Thanks!

[ThePotatoKing]

Run through this update guide, there’s a possibility you didn’t update the ampinstmgr CLI tools, which can then in turn bork out the instances.json file.
(ampinstmgr version in CMD should print out v2.6.0.6)
https://discourse.cubecoders.com/t/how-to-update-amp-to-the-latest-version/2297

If they still don’t show right, go into the datastore and copy the most recent instances.json-xxx.bak files and restore that inside the instances.json file.
Once that’s good to go, run ampinstmgr fixperms in CMD and reboot.

[Bob_Reas]

You’re correct. ampinstmgr version gave me 5.0.12.0. I’m going to have to do some reading on this upgrade procedure. I’ll message back here if I run into problems.
Thanks!