Question

3
Replies
103
Views
Close popover
Brian Johnson (BrianJ9608)
CenturyLink

CenturyLink
US
BrianJ9608 Member since 2018 2 posts
CenturyLink
Posted: February 24, 2020
Last activity: March 5, 2020
Closed
Solved

ASO.db file after Runtime upgrade

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***

Pega Robotic Desktop Automation Robotic Process Automation Support Case Created
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.