About to attempt an in place upgrade next week.  Did you ever get an answer to this and/or figure it out?

No. Actually not. I worked my way through and got to a point where I had fixed too much and I activatede the roll back of the server image from the day before.

Little things that made my setup complex (but i works):

1. tomcat and other 2 services run as a service user other than default
2. https is enabled
3. fme_ressources is not in same place/drive as default
4. SSO with SAML is enabled

All of these topics has been added since last upgrade and I think my game plan for the upgrade was not well updated accordingly. I think maybe item 3 was solved in an alternative way that caused more trouble later. Therefore I got back to the FME Flow 2023.1 that I was running before. 

 Now I’m gathering currage to do the whole thing again :)

​@worjak 
Sorry that you didn’t get some guidance on this when you posted. I am just seeing it now.

I just want to make sure since you didn’t mention a critical step… if you did do it and that was related to the encryption key from 2023.1? It was uploaded to 2024.2 prior to attempting the restore?

Also, are you loading the file a shared resource? /resources/data folder or are you uploading it directly from your client system?

If you try the upgrade and run into this again, I do invite you to reach out to Safe Support and create a support ticket.

Regards!

Steve