Troubleshooting
Problem
System application EAR files seem to not be showing they are upgraded to the current version although profile upgrade was successful. The application build version doesn't show the expected value for your product version:
WSVR0203I: Application: IBM_BPM_Teamworks_WCSingleCluster Application build level: BPM8600-20250606-065036
After upgrading BPM or installing a new application, you find one of the following issues even though the upgrade or deployment was successful.
-
ClassNotFound or NoSuchMethod errors for classes which should exist in the system applications or newly installed application.
-
FileNotFound errors related to files which should be part of the system application or installed application EARs.
-
ServletException errors for one of the system apps related to missing application metadata or files.
-
Behaviors which suggest an old version of the application code is still running.
We find the the problematic behavior only occurs on a particular node and other nodes work fine.
Errors can be seen when reviewing syncNode.log found at profile_root/logs/ for a recent syncNode command execution or in node agent logs for the impacted profile.
ADMS0036E: The configuration synchronization failed. ADMU0005E: Error synchronizing repositories com.ibm.websphere.management.exception.AdminException: ADMU0005E: Error synchronizing repositoriesDocument Location
Worldwide
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
22 June 2026
UID
ibm11079157