Frequently Asked Questions
Frequently Asked Questions: M-Files
Generic Error - No such interface supported
Posted by Ondas Santos (M-Files) on 08 January 2019 08:52 PM

Overview

The purpose of this article is to resolve issues on error "No such interface supported" showing in different objects in M-Files.

Impacted Products and Versions

M-Files version 9 and later.

Symptoms

Having more than one M-Files version installed at the same time and system throwing a generic error that include "No such interface supported" in the stack trace in situation that either has worked fine before or works fine in another vault.

Sample Case

Having M-Files Server version 18.9 along with M-Files Client version 18.11 on the same server producing similar "No such interface supported" error situation. An automatically calculated property value is failing and throws an error stack:

CoScriptObjectFactory.cpp, 265, Calculation of the automatic value of the property "M-FilesPartIdentificationPictureURLONLY" failed. (0x80040107)
ScriptErrorHelper.cpp, 96, Calculation of the automatic value of the property "M-FilesPartIdentificationPictureURLONLY" failed. (0x80040107)
MDispatchExImpl.h, 665, Calculation of the automatic value of the property "M-FilesPartIdentificationPictureURLONLY" failed. (0x80040107)
MDispatchExImpl.h, 812, Calculation of the automatic value of the property "M-FilesPartIdentificationPictureURLONLY" failed. (0x80040107)
MetadataCardAction.cpp, 386, Calculation of the automatic value of the property "M-FilesPartIdentificationPictureURLONLY" failed. (0x80040107)
MetadataCardAction.cpp, 570, Calculation of the automatic value of the property "M-FilesPartIdentificationPictureURLONLY" failed. (0x80040107)
MetadataEditor.cpp, 2575, Calculation of the automatic value of the property "M-FilesPartIdentificationPictureURLONLY" failed. (0x80040107)
MetadataModel.cpp, 4157, Calculation of the automatic value of the property "M-FilesPartIdentificationPictureURLONLY" failed. (0x80040107)
MetadataModel.cpp, 4508, Calculation of the automatic value of the property "M-FilesPartIdentificationPictureURLONLY" failed. (0x80040107)
ElectronicSignatureUIHelper.cpp, 229, Calculation of the automatic value of the property "M-FilesPartIdentificationPictureURLONLY" failed. (0x80040107)
MetadataModel.cpp, 11556, Calculation of the automatic value of the property "M-FilesPartIdentificationPictureURLONLY" failed. (0x80040107)
CoVaultMountingDocumentOperations.cpp, 3052, Calculation of the automatic value of the property "M-FilesPartIdentificationPictureURLONLY" failed. (0x80040107)
DocumentCache.cpp, 10156, Calculation of the automatic value of the property "M-FilesPartIdentificationPictureURLONLY" failed. (0x80040107)
DocumentCache.cpp, 10266, Calculation of the automatic value of the property "M-FilesPartIdentificationPictureURLONLY" failed. (0x80040107)
DocumentCache.cpp, 17558, Calculation of the automatic value of the property "M-FilesPartIdentificationPictureURLONLY" failed. (0x80040107)
RPCMethodCallWithRetry.h, 35, Calculation of the automatic value of the property "M-FilesPartIdentificationPictureURLONLY" failed. (0x80040107)
RPCMethodCallWithRetry.h, 35, Calculation of the automatic value of the property "M-FilesPartIdentificationPictureURLONLY" failed. (0x80040107)
RPCDocumentOperations.cpp, 10664, Calculation of the automatic value of the property "M-FilesPartIdentificationPictureURLONLY" failed. (0x80040107)
RPCDocumentOperations.cpp, 6722, Calculation of the automatic value of the property "M-FilesPartIdentificationPictureURLONLY" failed. (0x80040107)
MCallInLoop.h, 349, Calculation of the automatic value of the property "M-FilesPartIdentificationPictureURLONLY" failed. (0x80040107)
RPCDocumentOperationsHelper.cpp, 6181, Calculation of the automatic value of the property "M-FilesPartIdentificationPictureURLONLY" failed. (0x80040107)
RPCDocumentOperationsHelper.cpp, 5845, Calculation of the automatic value of the property "M-FilesPartIdentificationPictureURLONLY" failed. (0x80040107)
RPCDocumentOperationsHelper.cpp, 36784, Calculation of the automatic value of the property "M-FilesPartIdentificationPictureURLONLY" failed. (0x80040107)
RecalculateProperties.cpp, 444, Calculation of the automatic value of the property "M-FilesPartIdentificationPictureURLONLY" failed. (0x80040107)
RecalculateProperties.cpp, 444, No such interface supported. (0x80004002)
RecalculateProperties.cpp, 1581, No such interface supported. (0x80004002)
RecalculateProperties.cpp, 1429, No such interface supported. (0x80004002)
RecalculateProperties.cpp, 1648, No such interface supported. (0x80004002)
RecalculateProperties.cpp, 1364, No such interface supported. (0x80004002)
VaultScriptSessionTemplates.cpp, 98, No such interface supported. (0x80004002)
ScriptSiteCache.cpp, 147, No such interface supported. (0x80004002)
ScriptSiteCache.cpp, 216, No such interface supported. (0x80004002)
PropValCalculationScriptSession.cpp, 81, No such interface supported. (0x80004002)
VaultScriptSessionTemplates.cpp, 607, No such interface supported. (0x80004002)
(M-Files 18.9.6801.16)

 

Cause and Reason

Having multiple versions of M-Files software on the same computer and having an API registration conflict.

When newer M-Files version is being installed (even just client or server tools) it will register newer API that comes along with that version. Quite often even a minor version update will change the API registration and causes any application that is run from older version to fail even in trivial API calls. This situation causes from the API point "No such interface supported." error.

Solution / Workaround

The fix is to register correct version of API and restart M-Files Server service, and/or reboot the computer after registering the correct version API.

To register API run command prompt as an administrator and run following commands:

Regsvr32.exe "C:\Program Files\M-Files\<version>\Common\MFilesApi.dll"

Regsvr32.exe "C:\Program Files\M-Files\<version>\Common\MFilesApi64.dll"

Notes

In production environment it is recommended not to have M-Files Client installed in the computer running M-Files Server service for the end users.

If you have multiple versions of M-Files installed in the same computer, first stop the currently running version M-Files services, then register desired M-Files version APIs and start the desired M-Files version services. Additionally, it is good practice to keep the other M-Files versions services manually started up to avoid conflicts.

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

Help Desk Software by Kayako case