SSRS Bing Maps not working - error "The underlying connection was closed: An unexpected error occurred on a send."

PN 141 Reputation points
2022-12-09T12:54:32.947+00:00

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):
268955-capture.jpg

SQL Server Reporting Services
SQL Server Reporting Services
A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.
2,806 questions
Windows Maps
Windows Maps
A Microsoft app that provides voice navigation and turn-by-turn driving, transit, and walking directions.
245 questions
Accepted answer
  1. AniyaTang-MSFT 12,316 Reputation points Microsoft Vendor
    2022-12-12T05:59:47.273+00:00

    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.
    269514-2.png
    Best regards,
    Aniya

    1 person found this answer helpful.
    0 comments

4 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. 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.

    1 person found this answer helpful.
    0 comments
  2. 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:

    1. Start using TLS 1.2 in your environment
    2. 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

    1 person found this answer helpful.
    0 comments
  3. Jane Fleming 11 Reputation points
    2022-12-13T20:15:34.117+00:00

    @PN @IoTGirl

    Thanks!

    Changing both registry settings from the link provided by IoTGirl (the .NETFramework stuff and the SCHANNEL\Protocols stuff) brought our maps back to life!

    Now I can hardly wait for TLS 1.3 !

    1 person found this answer helpful.
    0 comments
  4. IoTGirl 2,976 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://learn.microsoft.com/en-us/azure/active-directory/hybrid/reference-connect-tls-enforcement

    0 comments