Error: Unable to connect to Vault 'VaultName'. History: No file access

The error message "Unable to connect to Vault 'VaultName'. History: No file access" sometimes occurs when the service account running Meridian services has lost local admin rights. For example, this can occur due to a GPO change, where the server was moved under another OU.

When this error occurs, access to any Vault is lost. Administrator does not display any Vaults under the EDM Server menu. The event viewer log for BC Application events shows the following error: "Access denied (ht5) (HTE_No_File_Access=128) D:\BC-Meridian Vaults\<VaultName>\<VaultName>.hdb"

Solution

Confirm that service account that is running the Meridian services has local admin rights on the server. If it does have local admin rights, contact Accruent Support.