Frequently Asked Questions
Frequently Asked Questions: M-Files
.NET Framework 4.6 causes incompatibility with M-Files for certain operations
Posted by Lassi Lehtinen (M-Files) on 01 June 2015 03:04 PM

Applies to:

  • M-Files versions prior to 2015 SR1 (11.0.4300.34)
  • Microsoft .NET Framework 4.6

 

Symptoms:

.NET Framework 4.6 causes some compatibility issues with M-Files.

In practice, this means that federated authentication (SAML V2.0, AD FS, OAuth, Azure AD sync) and replication via cloud storage do not work in the M-Files versions mentioned, 

if the computer has .NET Framework 4.6 installed prior to installing M-Files.

 

This happens because certain modules of M-Files require .NET Framework 4.5 to be installed in order to be registered.

Version 4.6 is an "in-place upgrade" over 4.5, and after the upgrade M-Files assumes that 4.5 is not installed. As a result, M-Files does not register the modules that depend on .NET Framework 4.5.

The error message from M-Files is "Class not registered".

Note, however, that the "Class not registered" error message is a generic error message and may appear in several other unrelated circumstances, too.

 

Solution:

  • Install a newer version of M-Files that detects .NET Framework 4.6 as an acceptable version. Fixes were done to M-Files 2015 Service Release 1.
    • You can download the latest version of M-Files from here.

 

For any additional questions regarding this topic, please contact M-Files Customer support: http://support.m-files.com

 

2015 M-Files Customer support team, http://support.m-files.com

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

Help Desk Software by Kayako case