This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello
Apologies if this is in the wrong location.
We have an app registered in Azure which allows our software to "import" emails from mailboxes into our software using OAuth; as well as send emails via our software. Since yesterday, we have noticed that emails are getting duplicated in our system as well as connectivity errors for outbound emails. Our development team believe that our attempt to mark the email as "Read" is failing so we import it again during the next scan.
In Windows Event viewer, the below error is occurring;
One of our customers ran msmd.exe and the only error in there is "An internal server error occurred. The operation failed". Have also tried https://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/security/enable-tls-1-2-client but no success. No changes/updates made to our software. Affecting multiple end users across multiple sites. Mailboxes using Basic Authentication are unaffected. Have there been any changes to permissions or changes TLS made?
Azure began deprecating legacy TLS
Are you sure you have 1.2 enabled on the client side?
https://learn.microsoft.com/en-us/troubleshoot/azure/active-directory/enable-support-tls-environment?tabs=powershell#enable-tls-12-on-common-server-roles-that-communicate-with-azure-ad
Ok, looks like enabling TLS 1.2 has resolved those connection issues however, we are still having issues with the duplication issue.
When we try to issue an update command to EWS to mark the email as read, we get an internal error on the EWS side.
Would it be best to raise another post for this?
Hi,
By default TLS1.2 is enabled on the clients and servers , however if someone has disabled it for a reason you can check and enable it enable-support-tls-environment
Also you will need to check .NET version, Update and configure .NET Framework to support TLS 1.2
==
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.
Hi,
Glad to know that issue is resolved for TLS, for the EWS issue I would request you to follow the troubleshooting article and if required create a new post and tag Exchange Q&A community.
tools-and-resources-for-troubleshooting-ews-applications-for-exchange
https://learn.microsoft.com/en-us/exchange/client-developer/exchange-web-services/tools-and-resources-for-troubleshooting-ews-applications-for-exchange
==
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.
Yes please create a new post. thank you!
@Graham Jenkins
Thank you for following up on this and I'm glad that @Andy David - MVP resolved your TLS issue!
If you have any other questions, please let us know.
Thank you for your time and patience throughout this issue.
----------
Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.
Sign in to comment