Article - CS18476
Status of vault folder becomes 'Invalid' when Windchill is configured as Windows Service in Windchill PDMLink
Modified: 14-Jan-2024
Applies To
- Windchill PDMLink 9.1 to 12.1
Description
- Status of vault folder located on network drive becomes 'Invalid' when Windchill is configured as Windows Service in Windchill PDMLink
- Using Windchill start command to startup Windchill, the vault folder located on network drive shows 'valid', while it changes to 'Does Not Exists' after start Windchill with Windows Service.
- Running mount validation action fails with the error
Some of the mounts are not valid
- Error is thrown in Method Server log
ERROR [RMI TCP Connection(39899)-x.x.x.x] wt.fv.FvMountValidator - java.nio.file.AccessDeniedException: \\computername\drive$\folder_location Nested exception is: java.nio.file.AccessDeniedException: \\computername\drive$\folder_location, for additional information search for following string in logs 55965cb9-170f-4687-8f25-1e802cfcdb1f wt.fv.FvException: java.nio.file.AccessDeniedException: \\computername\drive$\folder_location Nested exception is: java.nio.file.AccessDeniedException: \\computername\drive$\folder_location at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:83) at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97) at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102) at sun.nio.fs.WindowsFileAttributeViews$Basic.readAttributes(WindowsFileAttributeViews.java:53) at sun.nio.fs.WindowsFileAttributeViews$Basic.readAttributes(WindowsFileAttributeViews.java:38) at sun.nio.fs.WindowsFileSystemProvider.readAttributes(WindowsFileSystemProvider.java:193) at java.nio.file.Files.readAttributes(Files.java:1737) ... ERROR [ajp-nio-127.0.0.1-8011-exec-6] wt.fv.StandardFvService wcadmin - Some of the mounts are not valid java.nio.file.AccessDeniedException: \\computername\drive$\folder_location Nested exception is: java.nio.file.AccessDeniedException: \\computername\drive$\folder_location, for additional information search for following string in logs 55965cb9-170f-4687-8f25-1e802cfcdb1f
This is a printer-friendly version of Article 18476 and may be out of date. For the latest version click CS18476