Issues when restoring a backed up Galaxy (CAB file) in SP2023R2

Hi Jakob, would you please provide a screenshot with the error message?

Regards,

Klaus

Hi Klaus,

attached screenshots from log, and also from IDE, 

Hi, Does this work on 2020 ? If it does , i would suggest to create a new name in the 2020 version, take a backup and try to recover in the same version ( 2020 ), see if throws any error 

Also I'm working as a distributor in a different country, maybe we can help you immediately through our consultancy

Hi Rainer,

A support case is being opened for this, but thank you for your help.

Let me know what the resolution is / problem was when you do get to the bottom of it 

Let me know what the resolution is / problem was when you do get to the bottom of it 

Basically, there is a template in the galaxy that has a problem.  Finding it, and rooting it out can be painful.  It is recommended that you open a support ticket and work with a support engineer to get it resolved.  

In this case, it looks like there was a problem with the previous version, and a template that had an issue was left in the Galaxy.  The problem could be labeled corruption, and it is not easy to get it removed.  I have opened a ticket for Jakob, and will get a copy of his galaxy and attempt to root out the problem template here on my machines.

For others, another course would be to rebuild the galaxy at the older version, and then migrate it.  You could export all the templates, objects, etc, and just not bring the problematic template with it.  In that new rebuilt galaxy, you can then take it to the new version and migrate.

One problem there though, is finding the problem template.  Using some steps we have here, it has been identified in Jakob's galaxy, and once we see it, the problem makes since due to the history and previous problems with the template in question.  For others that may see this issue in the future, it may be a template that appears to be just fine, and you are unaware of any problem with it, except for this.  This is a very rare situation.  There are only a handful of cases dating back to the 3.x versions of Application Server.

Hi DAvid, thanks for your reply