We are currently running Pega Robot Runtime 19.1 in production in conjunction with Sync Server and Robot Manager.
The current production package is built on 19.1.11. We recently pushed a new release to a UAT group that was built on 19.1.22. A fatal exception is presented as soon as the package begins to load. See attachment.
It is related to the ASO.db file. If we delete the ASO.db file before running the new package, no error and a new ASO.db file is generated. Of course, users must enter credentials again after starting up runtime.
The loader and Sync server are working correctly in downloading and swapping the runtime version based on the package downloaded. I have taken the original production package built in 19.1.11 and upgraded it to 19.1.22 with no other changes and I get the same error anytime I swap between running packages built on different runtime versions if I do not remove or rename the ASO.db. We just downloaded 19.1.29 to ensure it was not something corrected in a more recent runtime release, and we see the same thing when changing between any of the 3 versions.
Surely this is not an expected error when upgrading runtime versions, right? Should I open an SR for this issue?
***Edited by Moderator Marissa to update SR Details***
In case anyone else searches for this issue and finds this thread, here are the results.
There was a bug introduced in 19.1.21 which prevented runtime from reading a previously existing ASO file. This was resolved in 19.1.27.
We have successfully tested upgrades from 19.1.11 to 19.1.29 and the error does not occur. Unfortunately, we have some users already on 19.1.22, so those will have to be addressed by deleting the ASO.db when we upgrade those packages.
So, if you are on a runtime version prior to 19.1.21, upgrade to 19.1.27 or beyond. Otherwise you will encounter this error and be forced to remove the ASO.db file.
Posted: 2 years ago
Posted: 5 Mar 2020 14:48 EST
Marissa Rogers (MarissaRogers)
Senior Knowledge Management Specialist