SSIS Dynamics CRM - The underlying connection was closed:

Problem

Sometimes you may see following error when running SSIS Dynamics CRM Source or Target

Unable to download the authentication policy from WSDL "https://yourhostname.api.crm.dynamics.com/XRMServices/2011/Organization.svc?wsdl". ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

Cause

Possible reason for this could be your system is still using older SSL Protocol and you have not applied this patch and your API calls are made using TLS 1.0 Protocol rather than TLS 1.2. 

You can validate this by using FREE web debugging proxy tool Fiddler (See failure when TLS 1.0 is used by system.

Solution

Here is the fix for this problem. Basically we have to set SSL Protocol to 3.0 or Higher before we call any Dynamics CRM Component.

1. Goto control flow > Right click in the designer surface > Click Properties > and set DelayValidation=True
2. Goto data flow task (with CRM Source or Target) 
3. Right click in the the designer surface > Click Properties > and set DelayValidation=True
   
   
   
4. Now go to Control Flow again Drag ZS REST API Task from Tool box.
5. Enter URL as https://httpbin.org/get  (Or you can call any website with https://)
   
   
6. Goto Advanced Tab (Change HTTPS protocol to SSL v3.0 or Higher)
   
   
7. Now connect REST API task to before calling CRM Component like below.
   
8. Run the package and verify see it works. You can also confirm Fiddler see which protocol being used after the change.
   

Contact Us

If you have more question(s) feel free to contact us via Live chat or email to [e-mail]

https://zappysys.com/support/