Hi @PN
I tested my map report and got the same error as yours. I guess there may be an error related to Bing Map. Maybe you can go to the relevant platform of Bing Map to inquire about the situation.
Best regards,
Aniya
SSRS Bing Maps not working - error "The underlying connection was closed: An unexpected error occurred on a send."
This occurred two months ago, lasted for several weeks, then mysteriously fixed itself for myself as well as other users around the world. It appears to be back this morning. Please see prior question reporting-services-2017-report-server-bing-maps-em.html.
SSRS version 15.0.1102.911.
Image of blank map with error (lat/long points are still plotted, but underlying bing map does not appear):
-
AniyaTang-MSFT 12,446 Reputation points Microsoft Vendor
2022-12-12T05:59:47.273+00:00
4 additional answers
Sort by: Most helpful
-
Jane Fleming 11 Reputation points
2022-12-12T17:43:41.44+00:00 Same scenario here on both 2017 and 2019.
Report that has worked for more than a year developed the "underlying connection was closed" error a few days ago. -
PN 141 Reputation points
2022-12-13T18:00:42.597+00:00 I received a quick answer with the work ticket that explains the issue:
On September 21st we decommissioned TLS 1.0 and TLS 1.1 for HTTPS on our APIs. The change was rolled back on September 29th and we just rolled the changes forward again on December 1st.
There are two ways to resolve the issue if this is what you believe may be the cause:
- Start using TLS 1.2 in your environment
- Change your calls to start using HTTP rather than HTTPS
There should be settings in the application to do this.
Thanks so much to the Microsoft Maps Support team!
@Jane Fleming @Aniyatang
-
Jane Fleming 11 Reputation points
2022-12-13T20:15:34.117+00:00 -
IoTGirl 3,126 Reputation points Microsoft Employee
2022-12-13T19:43:46.25+00:00 If you want to know more about TLS 1.2 in Azure/Windows I recommend checking out https://zcusa.951200.xyz/en-us/azure/active-directory/hybrid/reference-connect-tls-enforcement