1. Home
  2. Support
Article - CS19027

WinDU task "CabinetBasedDataContainerAlignmentReport" reports "Container mismatch. Cabinet and Data are in different containers" in Windchill PDMLink

Modified: 25-Jun-2026   


Applies To

  • FlexPLM 10.2 to 12.0
  • Windchill PDMLink 9.1 to 13.1

Description

  • Pre-upgrade WinDU task CabinetBasedDataContainerAlignmentReport reports "Container mismatch. Cabinet and Data are in different containers."
  • Post-upgrade WinDU task CabinetBasedDataContainerAlignmentReport reports "Container mismatch. Cabinet and Data are in different containers."
  • WinDU options - CabinetBased Data Container Alignment report potential issues "Container mismatch. Cabinet and Data are in different containers."
  • CabinetBasedDataContainerAlignmentReport.log contains "Container mismatch. Cabinet and Data are in different containers"
  • Following type of error is reported: 
    Data: wt.epm.EPMDocument:XXXX
Container: Site, Organization - MyOrg, Library - MyLib
Cabinet: wt.folder.Cabinet:yyyy Container: Site, Organization – MyOrg
AdministrativeDomain: Site, Organization - MyOrg, Library - MyLib2 /Default
    Or  
      Total number of Folder Misalignments in the System: #
 -----------------------------------------------------------------
 Container mismatch #0. Cabinet and Data are in different containers.
 Data: com.lcs.wc.foundation.LCSLogEntry:####
 	Container: Site
 Cabinet: wt.folder.Cabinet:####
 	Container: Site, Organization - <orgname>
 AdministrativeDomain: Site, Organization - <orgname>, Library - <libName>/Default/RFA/LogEntry
  • WinRU task reports: "There is not enough information to fix. Further investigation is needed"
  • WinRU task CabinetBasedDataContainerAlignmentRT shows the error "There is not enough information to fix. Further investigation is needed" after upgrade
  • WinRU task CabinetBasedDataContainerAlignmentRT fails with error: 
    java.lang.Exception: Exception of type 'wt.pom.PersistenceException' was generated on the server with message 'Message:  Resource bundle/Message key = wt.pom.pomResource/0'
 	at wt.pds.SQLDatabasePds.processSQLException(SQLDatabasePds.java:4144)
 	at wt.pds.SQLDatabasePds.executeCall(SQLDatabasePds.java:2108)
 	at wt.pom.PersistentObjectManager.executeCall(PersistentObjectManager.java:1898)
 	at wt.pom.PersistentObjectManager.executeCall(PersistentObjectManager.java:1843)
 	at wt.epm.FTValidatorTransactionListener.validateObjects(FTValidatorTransactionListener.java:815)
 	at wt.epm.FTValidatorTransactionListener.beforeCompletion(FTValidatorTransactionListener.java:714)
 	at wt.pom.TransactionManager$BeforeCompletionTransactionListener.fire(TransactionManager.java:1577)
 	at wt.pom.TransactionManager.fireTransactionListener(TransactionManager.java:1526)
 	at wt.pom.TransactionManager.beforeCompletion(TransactionManager.java:555)
 	at wt.pom.TransactionManager.commitTransaction(TransactionManager.java:439)
 	at wt.pom.BasicTransactionMonitor.commitTransaction(BasicTransactionMonitor.java:64)
 	at wt.pom.PersistentObjectManager.commitTransaction(PersistentObjectManager.java:404)
 	at wt.pom.Transaction.commit(Transaction.java:725)
 	at wt.fc.StandardPersistenceManager.update(StandardPersistenceManager.java:1188)
 	at wt.folder.CabinetBasedDataContainerAlignmentRT.fixFoldered(CabinetBasedDataContainerAlignmentRT.java:222)
 	at wt.folder.CabinetBasedDataContainerAlignmentRT.fixMisalignedObject(CabinetBasedDataContainerAlignmentRT.java:135)
 	at wt.folder.CabinetBasedDataContainerAlignmentRT.iterateMisalignedObjects(CabinetBasedDataContainerAlignmentRT.java:86)
 	at wt.folder.CabinetBasedDataContainerAlignmentRT.executeRepairTask(CabinetBasedDataContainerAlignmentRT.java:40)
 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
This is a printer-friendly version of Article 19027 and may be out of date. For the latest version click CS19027