After upgrade, MUX build number does not match Classic build number

Products

• Clarity PPM On Premise

Issue/Introduction

After upgrade, the MUX is showing the wrong version that does not match Classic

Environment

Any Supported Clarity Releases

Cause

This may happen if the services weren't properly redeployed upon upgrade. We recommend to fully remove Clarity services before upgrade.

Resolution

Check the install:

• Verify the install.log to ensure the install was complete and successful

Redeploy the services: 

1. Stop and remove all services - note which ones are deployed first
   service stop remove all
2. Add the services back:
   service add app bg beacon nsa
   ---use the exact services that are deployed
   service start all
3. Repeat on all servers in cluster and test.

Check the original package

• Check the timestamp/size of $clarity\META-INF\uif\wars\ppm-ux.war. If it predates the upgrade, the package didn't refresh it, or you redeployed from the wrong/old install dir.
• Look inside it:
  jar tf ppm-ux.war | findstr -i version or unzip and look at the bundle's version JSON - confirm it says the correct target version
• If it's stale - you may need to redeploy the MUX war or redo the upgrade with services removed