web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / D365 - 9.0 - An existi...
Microsoft Dynamics CRM (Archived)

D365 - 9.0 - An existing connection was forcibly closed by the remote host

(0) ShareShare
ReportReport
Posted on by Alduzzen1985 65

Hi Guys,

since today we are getting the exception "An existing connection was forcibly closed by the remote host" for different projects and Microsoft portals. We have seen that the problem is related only to CRM 9.0

We have updated the SDK  Version ( now we are using the 9 ) but nothing has changed. We are working with D365 Version 1612 (9.0.0.3172) (DB 9.0.0.3172) online.

Has someone get the same error ?

Thank you in advance

*This post is locked for comments

I have the same question (0)
  • Rickard Norström Profile Picture
    Rickard Norström on at

    I'm getting a similar error when I try to use the OData endpoint of a Dynamics 365 Customer Engagement Enterprise Edition as of January 2 at 21.30 UTC+1. That's the inner exception of the inner exception of the inner exception (I think). The more outer exception is "one or more errors has occurred" and on a slightly higher level it says that {"The underlying connection was closed: An unexpected error occurred on a send."} and "An error occurred while sending the request".

    This is mighty annoying since it's an integration for one of our customers and it was running between Dec 22 and Jan 2 slightly earlier than half past 9 in the evening UTC+1.

  • Rickard Norström Profile Picture
    Rickard Norström on at

    Hi again,

    If you're doing this by code you're probably not using TLS 1.2 as described in this article blogs.msdn.microsoft.com/.../updates-coming-to-dynamics-365-customer-engagement-connection-security

    It didn't work for me by just moving to .NET 4.6.2, I had to add the line "System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12;" in my code before I did any calls to Dyn 365.

    Hope that helps you!

  • Alduzzen1985 Profile Picture
    Alduzzen1985 65 on at

    Hi Rickard,

    I was expecting the change in March and not in January ( https://blogs.msdn.microsoft.com/crm/2017/09/28/updates-coming-to-dynamics-365-customer-engagement-connection-security/  ) . What I did to solve the problem is very simple, I've updated all SDK dlls to last version (9.0) and I've recompiled the projects with the .NET framework 4.6.2. 

    About the all my Microsoft Portal projects to avoid to change the .NET framework, I've added in the OrganizationService.cs class and Method

    protected virtual IServiceConfiguration<IOrganizationService> CreateServiceConfiguration(CrmConnection connection)

    the follow line :

    ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;


    Now everything is working correctly.

    Tack så mycket Rickard

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans