today a patient entered my clinic with a problem that seem to be well known already.
During the upgrade to BPM 8.6.0 2018.03 BPMUpdateSystemApp failed with
[2/5/19 16:51:01:596 PKT] 00000001 ImportFileHel I File /bpmapp/bpmuser/IBM/WebSphere/AppServer/BPM/Lombardi/imports/content-integration-toolkit.twx failed.....
[2/5/19 16:51:01:597 PKT] 00000001 ImportFileHel I No entry for toolkits/2064.304ac881-16c3-47d2-97d5-6e4c4a893177.zip
[2/5/19 16:51:01:600 PKT] 00000001 ImportFileHel E CWLLG2015E: An unexpected runtime exception occurred. See exception for more details. Error: No entry for toolkits/2064.304ac881-16c3-47d2-97d5-6e4c4a893177.zip.
com.lombardisoftware.core.TeamWorksException: No entry for toolkits/2064.304ac881-16c3-47d2-97d5-6e4c4a893177.zip
This sounded familiar and very similar to a desease we could cure by removing the toolkit that failed to be upgraded from
as described in another posting (Dmgr Profile fails to start with NPE after installing BPM 8.5.6 CF1)
However, this time removing the twx from the twximport.properties file just brought us one step further until for the next toolkit we got the same error. Receiving the same error for the process-portal.twx I became very suspicious and started a deeper investigation looking at the complete history of the update.
I asked the patient to provide the complete history of the problem by providing all documents requested in https://www-01.ibm.com/support/docview.wss?uid=swg21506937
Going back to Dmgr’s BPMUpdateSystemApp.log created during the Update process I found that the first attempt apparently had not been finished successfully.
As some toolkits have already been updated successfully the solution here was to apply a backup and restart the update process again.
What can be seen from this sample is : it is important to look at the very first failure that occurred to be able to cure the patient
As you can see, the last record in this log is
16:08:51:626 ] MutableSnapsh W CWLLG0523I: Ignoring identical dependency PODependency(source=TWProcess.ed8d1a03-7895-4126-ac69-e94ea4349be8, sourceReferenceLocation=Coach:2025.3b7ce7d2-b133-40b9-91bc-8543896da95b/CoachView:/64.ad2b879f-ee68-4bc9-9b1b-fb7c0856a48e, reference=Ref[/CoachView.ad2b879f-ee68-4bc9-9b1b-fb7c0856a48e]).
before it stopped ?!
The only explanation for this appears to be the BPM database may have been corrupted during the initial BPMUpdateSystemApp run. If the Toolkits are not upgraded properly, there is a potential problem with mismatch between the System Application, installed binary and toolkits in the database.
And finally, how we could resolve the problem ?
Well, the user decided to revert the system back to the time before they started the upgrade so they applied a backup of the database and the BPM binaries (that's the reason why I always remind my user to have a BPM backup available, if there is ever any need !) and start the complete upgrade process again.
What can be seen from this sample is : it is important to look at the very first failure that occurred in the log files to find the real cause and be able to cure the patient.
And if this does not help, take two of these and call me in the morning.
Your Dr. Debug