Skip to main content
J
jfrankovich12-Amethyst
12-Amethyst
August 27, 2026
Question

PrincipalRepairFailedException after rehost (rename) of legacy WC 11.2 system

  • August 27, 2026
  • 1 reply
  • 8 views

We have an older WC 11.2 system that was shuttered, but now we want to move it to a new domain in the unlikely event that we have to retrieve any unmigrated data from it.
The rehost using the Rehost Utility seems to have worked and updated the configurations, but during startup we get errors about Principal Repair Failure, repair of users being unsuccessful, a related disconnected participant, and then failures due to a rollback. Ultimately the MS shuts down and then retries again with the same errors.

I found some support articles related to the repository table in the database but it isn’t clear what it “should” look like after the rehost.
Article - CS51791 - After rehost MethodServer fails to start with error Cannot process participant xxx because a related disconnected participant wt.org.WTGroup:<ida2a2> exists in the database in Windchill PDMLink
Article - CS109367 - Error updating repository table for JNDI Adapter: ORA-00001: unique constraint (PDMLINK.REPOSITORY$UNIQUE50) violated in Windchill PDMLink

The issues still seem like they apply to current versions of WC. Has anyone experienced anything like this following a rehost?

John

1 reply

B
BryanK17-Peridot
17-Peridot
August 27, 2026

have a look at the Repository table in the DB. there will be a few rows in there. Check that the rows have the correct ldap name. 

This call should explain what you should be looking for.

Article - CS109367 - Error updating repository table for JNDI Adapter: ORA-00001: unique constraint (PDMLINK.REPOSITORY$UNIQUE50) violated in Windchill PDMLink

Terms & ConditionsAccessibility statement