Resolving “The sequence of events was not completed” and duplicate custom properties after a Qlik upgrade

As part of our BizXcel Qlik Sense Administration package, we regularly upgrade the Qlik Sense for our managed systems clients.  After our last upgrade, we encountered an application reload error on two regular applications that reloaded each night. 

 In the QMC, we saw the following error message – “The sequence of events was not completed.  Check engine or script logs.”  However, when we reviewed the script logs, we could tell that the application script was executing correctly.  Initially, we thought this might be a Qlik Sense application index problem, so we deleted the application indexes and reloaded the application.  On this reload, we saw that the indexes rebuilt properly and the applications script executed correctly. 

 The team now focused on advanced troubleshooting.  The team's first test was to try reloading the applications manually in the Data Load Editor, but when they did this, they received an Unknown Error once the scripts finished execution.  A second test they did was to see if they could duplicate the application and replace it with the copied version.  When they tried that, they received a “Conflict” error message in the QMC. 

The team reviewed the Qlik Sense logs in detail and focused on the Repository Audit log, usually found in C:\ProgramData\Qlik\Sense\Log\Repository\Audit.   Within the Audit log found the following error “The custom property value already assigned (HTTP code: 409)”. 

 Using this information, they reviewed the problem applications and found that for the Custom Properties assigned to the problem applications, they had a “(2)” beside them, indicating that they somehow had the property value assigned to them twice.  When they compared these custom properties to the other application on the system, the typical “(1)” count indicated that the property was applied once. 

 The team then tried removing the custom property with the “(2)” and reapplying it.  After fixing the customer property, they reloaded the application, and it worked!  

 With this information, the team wanted to understand the problem a bit more and did some research to find this Qlik article - https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Reload-failing-With-error-Warning-Conflict/ta-p/2034338.  The article suggests to resolve the issue manual database edits are required.  Still, in our efforts, we found that we could resolve the problem using the application properties screen in the QMC. 

 As always, your Mileage May Very.  

 If you are interested in keeping your Qlik Sense system updated, check out our Qlik Sense Administration package at https://www.bizxcel.com/qliksense-administration