Skip to main content
K
KC_112531907-Bedrock
7-Bedrock
August 12, 2024
Solved

Invalid Vaults When Rehosting From Non Clustered To Clustered Instance

  • August 12, 2024
  • 1 reply
  • 726 views

Version: Windchill 12.0

 

Use Case: Using Windchill 12.0.2.7. and undergoing a rehost procedure from a source to a target instance. The source is not clustered and the target is clustered.


Description:

File vaults will not validate when set to the proper UNC path instead are defaulting to the local vault instance. I am under the impression that vault configuration data may be stored in the database and may have been wiped, potentially looking at how to restore the proper settings. Looking for any documentation on the procedure to follow in this environment configuration. Thank you.

Best answer by KC_11253190

Update: was able to find error logs on slave instance. when validation is attempted on the master, a log is generated on the slave:

wt.fv.FvMountValidator - please check the access permissions (read/write/update) to the path: 

wt.fv.FvMountValidator - 27

wt.fv.FvMountValidator - java.nio.file.AccessDeniedException

 

Would this be because the windchill service account does not have access to the UNC path to the vault?

This article seems to be related:

https://www.ptc.com/en/support/article/CS284372

 

Solution: I was able to fix this problem by adding the windchill windows service account to the appropriate active directory permissions group.

1 reply

K
KC_112531907-BedrockAuthorAnswer
7-Bedrock
August 13, 2024

Update: was able to find error logs on slave instance. when validation is attempted on the master, a log is generated on the slave:

wt.fv.FvMountValidator - please check the access permissions (read/write/update) to the path: 

wt.fv.FvMountValidator - 27

wt.fv.FvMountValidator - java.nio.file.AccessDeniedException

 

Would this be because the windchill service account does not have access to the UNC path to the vault?

This article seems to be related:

https://www.ptc.com/en/support/article/CS284372

 

Solution: I was able to fix this problem by adding the windchill windows service account to the appropriate active directory permissions group.

    Terms & ConditionsCookie settingsAccessibility statement