Options
  • State Suggested Answer
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 14 subscribers
  • Views 299 views
  • Users 0 members are here
Related

Exchange Online Mail Source Error

jason.ross@etu.nz

Hi

I have an existing connection to Exchange Online that the client secret has expired. I have created a replacement but when I go to apply it I get the errors for the TLS. 

I have made the changes for the TLS, however I'm now getting the following error and cant find a solution for it.

MPropertyPage2.cpp, 100, Authentication failed. (0x80040162)
MPropertySheet2.cpp, 142, Authentication failed. (0x80040162)
PropertySheetExternalLocation.cpp, 397, Authentication failed. (0x80040162)
PropertySheetExternalLocation.cpp, 590, Authentication failed. (0x80040162)
ExternalMailSourceClient.cpp, 232, Authentication failed. (0x80040162)
ExternalMailSourceClient.cpp, 232, Silent Microsoft authentication failed. One or more errors occurred. An error occurred while sending the request. The underlying connection was closed: An unexpected error occurred on a receive. The client and server cannot communicate, because they do not possess a common algorithm (0x80040162)
(M-Files 24.8.13981.4 2024-09-04T21:52:30.070Z)

Any advice would be helpful.

  • 0

    I found an earlier support case with the same error and this was our support team's guidance:

    This error most likely indicates that one or more of the following does not match between the client and the server (in this case "client" is the M-Files Server computer, and "server" is the Microsoft Entra ID server cluster):

    • TLS protocols are not only 1.2. Sometimes TLS 1.2 needs to be explicitly enforced by, for instance, disabling older and newer protocol versions. You can read more in Azure AD TLS 1.0 and 1.1 Error: "Silent Microsoft authentication failed" even though the error does not match exactly the examples mentioned in the article.
    • Ciphersuites are explicitly set on the client and the ones it has listed are not the ones the server supports (or, rather, accepts). Or, the client OS is old (such as Windows Server 2012) and simply has an old set of ciphersuites and needs an upgrade.

    This error is system-wide - it will affect all http traffic on this machine.

    I hope this gives you some ideas on how to continue the troubleshooting. If you can't get it working, I suggest reaching out to your M-Files reseller or Microsoft support for assistance.

M-Files
M-Files Support


© 2024 M-Files, All Rights Reserved.