Support Article

Issue while upgrading to Pega 7.1.8

SA-14885

Summary



Upgrade from Pega 7.1.5 to Pega 7.1.8 fails with error "system contains hotfixes generated after this release was built".

Error Messages



Verify ML Readiness:
System meets basic requirements for update to 07-10-17
PRPC_Rules build date: 2015-05-20 17.20 EDT

The following rules were updated after this release was built:
pzinskey pxUpdateDateTime
RULE-OBJ-CLASS EMBED-ENV-LISTENER-JMSMDB 2015-07-20 10:26:01.032
RULE-OBJ-CLASS EMBED-ENV-LISTENER-MQ 2015-07-20 10:26:02.239
RULE-OBJ-CLASS EMBED-ENV-MAPPING- 2015-07-20 10:26:02.972
RULE-OBJ-CLASS EMBED-ENV-MAPPING-PARSEXML 2015-07-20 10:26:03.736
RULE-OBJ-CLASS EMBED-ENV-MAPPING-XMLSTREAM 2015-07-20 10:26:04.401

These instances might not be found by rule resolution after updating.
Contact Pega Support to evaluate whether to continue the update process.

BUILD FAILED
C:\114820_P718-UPD\pegaGuiInstallerTemp\build.xml:78: The following error occurred while executing this line:
C:\114820_P718-UPD\scripts\setupDatabase.xml:368: The following error occurred while executing this line:
C:\114820_P718-UPD\scripts\setupDatabase.xml:1483: This update cannot be applied, the system contains hotfixes generated after this release was built.


Steps to Reproduce



Run upgrade wizard, to reproduce this issue.

Root Cause



A defect or configuration issue in the operating environment. Below rules are created or updated post release of Pega 7.1.8. 

RULE-OBJ-CLASS EMBED-ENV-LISTENER-JMSMDB 2015-07-20 10:26:01.032
RULE-OBJ-CLASS EMBED-ENV-LISTENER-MQ 2015-07-20 10:26:02.239
RULE-OBJ-CLASS EMBED-ENV-MAPPING- 2015-07-20 10:26:02.972
RULE-OBJ-CLASS EMBED-ENV-MAPPING-PARSEXML 2015-07-20 10:26:03.736
RULE-OBJ-CLASS EMBED-ENV-MAPPING-XMLSTREAM 2015-07-20 10:26:04.401
 
The above rules have the updatedatetime is post release date of Pega 7.1.8.

When user executes bulk validation for parse-XML rule, it is not getting picked up by rule resolution process in Pega. Bulk validation process updates updatedatetime property with latest date.


 

Resolution



Here’s the explanation for the reported behaviour:

The validation is what updated the updatedatetime and thus these are just false positives. Executing the update script with force option and these rules is replaced with the Pega 7.1.8 version.


Upgrade from IUA

Add below value in setupDatabase.properties
force.ml.update=true



From command line
 
Update.sh/bat -force




 
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.