Troubleshooting
Problem
In IBM Cloud Pak for Business Automation (CP4BA) on Red Hat OpenShift Container Platform (RHOCP) 4.18 deployed on AWS, users encounter an issue where Case Manager layout pages fail to load in the Case Builder console after migrating Case solutions from on-premises IBM Case Manager (ICM) environments. The error manifests as HTTP 404 errors when attempting to load widget resources, with logs showing 'FNRPA0076E: The current REST request cannot be processed because the resource path IBM Case Manager Widget package was not found.' The problem is linked to a mismatch in the case sensitivity of the design object store name configured in the CP4BA CR YAML file and the actual name in the Administrative Console for Content Enterprise (ACCE).
Symptom
The Case Manager layout pages (e.g., Cases, Work) are not loading for editing after migrating legacy on-premises Case solutions to CP4BA. The issue is characterized by HTTP 404 errors when trying to load widget resources, indicating that the resource path 'IBM Case Manager Widget package' was not found. The design object store name in ACCE is in all capitals, which may be causing case sensitivity issues.
Cause
The issue was caused by the design object store name being in all capitals in ACCE, while the same design object name in the CR file is lower letters.
Diagnosing The Problem
- Investigate the design object store name in ACCE to check for case sensitivity issues.
- Enable tracing at the Authoring pod (bastudio) with the trace string =info:com.ibm.casemgmt.*=all:HTTPChannel.=all and reproduce the error.
- Make sure that the name of the design object in the CR yaml file has the same name as one seen in ACCE in step 1.
Resolving The Problem
1. Update the CR yaml file to reflect the case sensitivity of the design object store name to match the same name as seen in ACCE.
2. Re-run the Case init job.
Document Location
Worldwide
Product Synonym
Cloud Pak for Automation
Was this topic helpful?
Document Information
Modified date:
23 May 2026
UID
ibm17273892