This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Hi guys, anyone have problems connecting to an email external source based on office365?

With the latested version of M-Files we have a problem connecting to an external email source, based on an source email of office365.

This occours since 1/october and the error returned is

CoSnapInComponent.cpp, 900, Communicating with the mail server "outlook.office365.com" failed. (0x800400EC)
CoSnapIn.cpp, 981, Communicating with the mail server "outlook.office365.com" failed. (0x800400EC)
Item_ExternalLocation.cpp, 213, Communicating with the mail server "outlook.office365.com" failed. (0x800400EC)
Item_ExternalLocation.cpp, 263, Communicating with the mail server "outlook.office365.com" failed. (0x800400EC)
Item_ExternalLocation.cpp, 631, Communicating with the mail server "outlook.office365.com" failed. (0x800400EC)
RPCMethodCallWithRetry.h, 177, Communicating with the mail server "outlook.office365.com" failed. (0x800400EC)
RPCMethodCallWithRetry.h, 177, Communicating with the mail server "outlook.office365.com" failed. (0x800400EC)
RPCExternalLocationsAdmin.cpp, 885, Communicating with the mail server "outlook.office365.com" failed. (0x800400EC)
RPCExternalLocationsAdmin.cpp, 286, Communicating with the mail server "outlook.office365.com" failed. (0x800400EC)
RPCExternalLocationsHelper.cpp, 1747, Communicating with the mail server "outlook.office365.com" failed. (0x800400EC)
RPCExternalLocationsHelper.cpp, 1747, The IMAP module returned the following error: (0x8004380E)
RPCExternalLocationsHelper.cpp, 1844, The IMAP module returned the following error: (0x8004380E)
EasyMailWrapper.cpp, 339, The IMAP module returned the following error: (0x8004380E)
CoEmailIMAP4Session.cpp, 112, The IMAP module returned the following error: (0x8004380E)
EasyMailHelper.cpp, 567, The IMAP module returned the following error: (0x8004380E)
EasyMailHelper.cpp, 567, 100 NO LOGIN failed. (0x80043813)
(M-Files 22.9.11816.9 2022-10-14T16:16:07.897Z)

Any help?

Parents Reply
  • One thing you could check is to make sure the server is using TLS 1.2 when trying to connect to Microsoft services, this support article has more information: Azure AD TLS 1.0 and 1.1 Error It shouldn't crash M-Files Admin but just to rule that one out as a possible cause.

    If that doesn't help, I recommend raising this with our technical support. You may find additional information in the Windows application log on the server: if there are any error messages related to the crash, please include them in your message to the support team.

Children
No Data