Dynamics CRM V9 connection Error in Pluging/Console or Custom Web Application/Report Viewer in VS

Recently faced a strange issue in CRM v9 while connecting to Org Service. It was perfectly working before last night. Issues faced  in different scenarios. Am trying to consolidate all here . If any one faces any of the below issue then try the solution given below.

ISSUES:

Not able to login Plugin registration tool (Keep popping up for Credentials)

Not able to see custom entites in Plugin Registration tool

Connection to CRM from Custom Web application & console failed

Can able to retrive data in DataSet in Report rdl but not able to Preview

ROOT CAUSE:

Its all because of the latest update in the Microsoft TSL(Transport Security Layer) Protocol in SDK assemblies..Microsoft allowed the TSL connection 1.0  and 1.1 for the browsers or client to connect the CRM org.Now Microsoft will support only TSL 1.2 or above going forward(Reference) . If you are connecting your org with the old version of plugin registration tool , then you may face this issue.

HOW TO IDENTIFY:

Use fiddler to check the your server request TSL Version. Install fiddler https://www.telerik.com/download/fiddler

SOLUTION:

1.For Plugin Issue: Update latest SDK from the Plugin Registration Tool 

or Download tools from NuGet

2.For Report: Uninstall Report Authoring Extension and install the latest.(Make sure Installed dll is the latest SDK 9.0). if this doesnt resolve the issue then follow the below step.

On the machine where VS is installed go to the start menu, then type run and then enter. Type in regedit and then OK.

Once the Registry Editor is open, go to: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319
Right click on the name of the folder (the v4.0.30319 folder) and select New, then DWORD. Give it the name of SchUseStrongCrypto and the Value of 1. Exit the Registry Editor, then restart your machine. 

3.For Custom Application or Console App : Include the below reference to your project(to global config file the line before where your client credentials is configured) and change the .Net framework to 4.6.1 and rebuild 

"ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls11 | SecurityProtocolType.Tls12"

If you can't update you project to the latest assembly version (4.6) then follow the step give by Mr.Massoud in the comment.

IMPORTANT:

4. Modify using TSL to 1.2 through Fiddler . Keep open the fiddler after modifying and try to connect if you dnt have latest SDK or if you were not able to connect with the above methods.

FOR END USERS:
Please upgrade all your browsers(IE,Chrome,Firefox,Safari) which supports TSL 1.2 and  can send the secure request to all your client applications