Question
Verizon Sourcing LLC
Last activity: 26 Nov 2018 8:21 EST
Deployment Package Running Older Version
I have made changes to one of my existing automations and I have redeployed the package and placed it both on my sever and my remote desktop. For some reason, even though I have updated the package multiple times and move the package to multiple spots, the automation is still running the older version of the automation. I have delete the packages and tried it again but its still running the older version. If I run the automation in studio on my own PC the automation runs the newer changes. Both my studio and runtime are on the same versions. Any one have any ideas whats going on?
***Edited by Moderator: Pallavi to update platform capability tags***
Accepted Solution
Pegasystems Inc.
US
The deployment version value is stored in .osproj file - make sure this file is not read-only. If you use source control then check out project before deployment and then check it in back after deployment.
Pegasystems Inc.
US
How startup project is assigned in your environment? Did you set StartupProject in RuntimeConfig.xml or using Robot Manager or created shortcut?
Please double-check that path to deployment package is correct (if not using Robot Manager). Also make sure that deployment version is higher than current version that is loading. Also, check Runtimelog, it may have some details (current version, used path for packages or exceptions at startup).
Verizon Sourcing LLC
I created a desktop icon on the desktop sever and I am simply double clicking that icon. I double checked this path to make sure its correct and even dropped the package onto the desktop and changed the path in the icon with no luck. Like I said in my previous post, the versions are exactly that same, Pega Robotic Studio 8.0.168 and Pega Robotic Runtime 8.0.168, but I can try upgrading if you think its a version issue?
Pegasystems Inc.
US
I mean deployment version, not version of Runtime or Studio. Deployment version is assigned during deployment process and should be incremented with each new deployment:
If the old package has deployment version 1.0, newer one should be 1.1 or higher, otherwise Runtime does not recognize the change.
Updated: 7 Nov 2018 8:37 EST
Verizon Sourcing LLC
Ah yes, that does seem to be the issue. Its stuck on 1.94 regardless if I make changes or not. Any ideas why this is happening?
Accepted Solution
Pegasystems Inc.
US
The deployment version value is stored in .osproj file - make sure this file is not read-only. If you use source control then check out project before deployment and then check it in back after deployment.