Frequently Asked Questions
Frequently Asked Questions
Compliance Kit or Vault Application Cannot Be Installed
Posted by Ramez Mohsene (M-Files) on 08 February 2019 06:44 PM


1     Impacted Products and Versions

M-Files version 11.3.x.254 and older. Issue does not occur in M-Files 12.0 and newer.

2     Symptoms

When attempting to install a vault application, an error is seen stating:

Could not load file or assembly <filepath> Operation is not supported. (Exception from HRESULT: 0x80131515) (0x80131515)

3     Cause and Reason

Due to bug number 142873, it states that when utilizing a network file path for file storage of a vault, Windows loses track of the proper temp path when a vault application is installed. The vault application process decompresses files from the .mfappx file and references are lost during this operation. This bug has been fixed in 12.0 and newer versions.

4     Solution / Workaround

There is a registry key to specify a direct temp location path, that can be implemented on the M-Files Server:

Key name: HKEY_LOCAL_MACHINE\Software\Motive\M-Files\<version>\Server\MFServer\VaultOptions\<vault-guid>

Value name: TempPath

Value type: REG_SZ

Value data: <path>


If "TempPath" is not specified, the temporary files of the vault will be placed in the default temp location of the vault, which is the "Temp" folder under the file data location of the vault.

(0 vote(s))
This article was helpful
This article was not helpful

Help Desk Software by Kayako case