Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreWe've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
We have Power BI embedded reports in a .NET web application running on framework 4.5.2 and with Power BI API 2.4
Since yesterday those reports start to failed. The error is in the authentication process with the API, specifically on this line:
var authenticationResult = await authenticationContext.AcquireTokenAsync(ResourceUrl, ClientId, credential);
The error is not giving much information: "The underlying connection was closed: An unexpected error occurred on a send."
I tried to setup a project with the new API v.3.11.1 and the exact same code is running without any issues, the problem is that we will need to updagrade the whole project to framework 4.7.2 and that could take a considerable effort. Are you aware of any possible workaround to keep using v2 until we succesfully upgrade the project?
Hello @carlosmunoz ,
The issue is not caused by the new API v.3.11.1. In the next release of the framework the SecurityProtocolType enumerator got extended with the newer Tls protocols, so if your application can use th 4.5 version you can also use Tls11 and Tls12. So if you are on .net framework 4.5,change the SecurityProtocol .
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls |
SecurityProtocolType.Tls11 |
SecurityProtocolType.Tls12;
Best Regards
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |