1. Home
  2. Support
Article - CS399676

On a cluster environment Vaults mounts become INVALID randomly in Windchill PDMLink 12.0

Modified: 02-Mar-2026   


Applies To

  • Windchill PDMLink 12.0.2.0 to 12.0.2.15
  • Windchill PDMLink 12.1.2.0 to 12.1.2.6
  • Creo View 9.0 to 11.1
  • Windchill PDMLink 13.0.2.3 to 13.0.2.6

Description

  • For some cad items the viewable are not available (not possible to open it in Creoview)
    An error message appear when we try to open in Creoview "The request action has failed, contact your server admin for more information"
  • On a cluster environment Vaults mounts become INVALID randomly/automatically, e.g. after 24 hours starting.
  • Publishing is failing due to "Invalid" mount status in Windchill PDMLink
  • Even implementing a workaround, the mount status are getting into Invalid state in Windchill PDMLink
  • Vaults in cluster environment change status periodically to INVALID and usually happen every 24 hours. 
  • What is the significance of the property wt.fv.FvMountValidator.waittime
  • If logger wt.fv DEBUG enabled, Method Server log will display below: 
    wt.fv.uploadtocache  - BackupedFile: BackupedFile constructed mountType=null, path=/opt/ptc/vaults/default_cache_vault/folder00237, name=MOUNT_VALIDATION_DATA
wt.fv.uploadtocache  - BackupedFile: BackupedFile constructed path_i=</opt/ptc/vaults/default_cache_vault/folder00237>
wt.fv.uploadtocache  - BackupedFile: getAbsolutePath res=/opt/ptc/vaults/default_cache_vault/folder00237/MOUNT_VALIDATION_DATA
wt.fv.uploadtocache  - BackupedFile: BackupedFile constructed mountType=null, path=/opt/ptc/vaults/default_cache_vault/folder00237/MOUNT_VALIDATION_DATA, name=SITE_208_212_14491780_04<Host1>.WC
wt.fv.uploadtocache  - BackupedFile: BackupedFile constructed path_i=</opt/ptc/vaults/default_cache_vault/folder00237/MOUNT_VALIDATION_DATA>
wt.fv.uploadtocache  - BackupedFile: all files exists res=true
wt.fv.uploadtocache  - BackupedFile: BackupedFile constructed mountType=null, path=/opt/ptc/vaults/default_cache_vault/folder00237, name=MOUNT_VALIDATION_DATA
wt.fv.uploadtocache  - BackupedFile: BackupedFile constructed path_i=</opt/ptc/vaults/default_cache_vault/folder00237>
wt.fv.uploadtocache  - BackupedFile: getAbsolutePath res=/opt/ptc/vaults/default_cache_vault/folder00237/MOUNT_VALIDATION_DATA
wt.fv.uploadtocache  - BackupedFile: BackupedFile constructed mountType=null, path=/opt/ptc/vaults/default_cache_vault/folder00237/MOUNT_VALIDATION_DATA, name=SITE_208_212_14491780_04<Host2>.WC
wt.fv.uploadtocache  - BackupedFile: BackupedFile constructed path_i=</opt/ptc/vaults/default_cache_vault/folder00237/MOUNT_VALIDATION_DATA>
wt.fv.uploadtocache  - BackupedFile: all files exists res=false
wt.fv.FvMountValidator  - All mounts may not be pointing to same physcial path for - site = master folder = folder00237
wt.fv.uploadtocache  - BackupedFile: BackupedFile constructed mountType=null, path=/opt/ptc/vaults/default_cache_vault/folder00237, name=MOUNT_VALIDATION_DATA
wt.fv.uploadtocache  - BackupedFile: BackupedFile constructed path_i=</opt/ptc/vaults/default_cache_vault/folder00237>
wt.fv.uploadtocache  - BackupedFile: getAbsolutePath res=/opt/ptc/vaults/default_cache_vault/folder00237/MOUNT_VALIDATION_DATA
wt.fv.uploadtocache  - BackupedFile: BackupedFile constructed mountType=null, path=/opt/ptc/vaults/default_cache_vault/folder00237/MOUNT_VALIDATION_DATA, name=SITE_208_212_14491780_04<Host3>.WC
wt.fv.uploadtocache  - BackupedFile: BackupedFile constructed path_i=</opt/ptc/vaults/default_cache_vault/folder00237/MOUNT_VALIDATION_DATA>
wt.fv.uploadtocache  - BackupedFile: all files exists res=false
wt.fv.FvMountValidator  - All mounts may not be pointing to same physcial path for - site = master folder = folder00237
wt.fv.FvMountValidator  - Marking all mounts for folder invalid folderid = SITE_208_212_14491780
This is a printer-friendly version of Article 399676 and may be out of date. For the latest version click CS399676