We use the CloudAppPublisher (PB2022 Build 1878) to distribute 3 applications internally.
To date, the webserver has resided on a Windows 2012 R2 box and has been rock solid reliable. Unfortunately with the imminent demise of support for the OS, I've had to migrate onto a newer webserver running Windows Server 2022.
I installed the CloudAppPublisher and the 3 applications to the new webserver. On my local machine I uninstalled the applications using the Uninstall link, and then reinstalled them using an http link to the new server. Everything went fine.
However, since then I've made some changes to the 3 applications and updated the release version on the server.
On running 2 of the 3 applications on my local machine, I receive the pop-up message that the local version has expired. On clicking the OK button to update the application, I see the updating flash screen and the application opens, but it's still the old version and hasn't been updated. I can see in the www logs that the application is getting the apprun.json, deploylist.ini.zip and appconfig.json.zip files, but no further files are requested.
The third application updates fine.
If I install any of the applications on a fresh computer, the new version is downloaded and installed without a problem.
How do I go about troubleshooting this?
Many thanks,
David
- You are here:
-
Home
-
Q&A
-
Q&A
-
PowerBuilder
- CloudApp update problem after server move
-
David Sowray
- PowerBuilder
- Thursday, 7 September 2023 15:44 PM UTC
The deploy was definitely to the correct server. The successful install of the latest version to the fresh machine came from that server, so that part I'm sure about. My local machine was also definitely talking to the new server, as I could see the requests on the log of the new server. Also in the logs in C:\Users\username\AppData\Local\CloudAppLauncher_V2\log referred to the new server. Unfortunately there were no error or information messages in the CloudAppLauncher logs which could point me in the right direction. In addition, I received the messagebox about the new version, which I wouldn't have seen if there wasn't one to pick up from the new server.
Apologies for such a stupid and annoying problem - it's probably a trivial fix if I could just work out the cause, but I'm stumped for a solution at the moment.