If the service runs at a different location from where the VaultData folder is stored, ensure that the VaultData folder was installed with a UNC path, not a mapped drive. Update the vault installation by running the setup again using the UNC path for the VaultData folder. If the service still does not start, it is likely a service-related permissions problem.
To troubleshoot permissions, change the service login user from the “Local system account” to a user account with RW permission on both the server and the remote location. This user must have full permissions for the VaultData folder. When the VaultData folder is on a different machine, this account must exist on that machine. A common user is a user in the current Windows domain of both computers.