Reporting Services 2017 Report Server: bing maps embeded in report error : the underlying connection was closed: An unexpected error occured on send.

Dejan Milic 41

We have a report deployed on an "On-Prem" SQL Server 2017 Report Server instance.
The Bing map layer is not displaying when we call the report from the Report Server portal:

However if we debug the same report in Visual Studio from the same hosts it works:

We have this same report running just fine on a legacy SharePoint 2010 integrated mode instance:

We looked in Report Server logs, but nothing obvious caught our intention.

It does not seems to be a httpProxy issue either:

PN 141 Reputation points

2022-09-28T16:21:58.69+00:00

I am facing the same issue. It began last Thursday and I've been trying to test where I can. Our on-prem server is version 15.0.1102.911. It also occurs inside of report builder when I run the RDL from the server or from a local file.

I don't normally work with these files in VS, but found the same thing. When opened in VS, the map loads in preview mode.

We also have no proxy issue.

I had a friend with another agency try the same thing and found the same result. I double checked and we did not take any updates around last Thursday that would have caused this.

I was able to switch a couple of reports over to Google static maps API, but I'm also looking for a solution to this for some of my more complicated mapping products.

Accepted answer

PN 141 Reputation points

2022-10-05T12:08:14.003+00:00

@Dejan Milic @AniyaTang-MSFT @Jane Fleming

Maps began working in my reports again this morning. To be clear, the only change I have made in the past 24 hours is that I added a file share account in the report server, which should be completely unrelated to this issue.

The maps looks a bit different. More clear? Perhaps Bing maps was going through an update.
Please sign in to rate this answer.
Dejan Milic 41 Reputation points

2022-10-05T12:57:29.047+00:00

@PN Indeed the issue vanished itself

PN 141 Reputation points

2022-10-05T13:20:43.29+00:00

@Dejan Milic

I'm glad it's working again, but frustrating that this happened with no explanation.

AniyaTang-MSFT 12,321 Reputation points Microsoft Vendor

2022-10-06T01:17:43.743+00:00

That was good! Thanks for your feedback.
Sign in to comment

5 additional answers

AniyaTang-MSFT 12,321 Reputation points Microsoft Vendor

2022-09-29T02:01:50.893+00:00
Hi @Dejan Milic
Can you access the report server on IE? Is the TargetServerURL you deployed correct? Did you configure a TLS connection?

If everything is correct and you are not running SSL, you can try changing the SecureConnectionLevel in the configuration file.
The method is as follows:

Find the rsreportserver.config file, it may be in such a path: C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer;

Copy a backup of the file;

Then open the original file, find SecureConnectionLevel, and set this value to 0;

After saving, restart SSRS to check whether the file can be deployed.

For more details, you can refer to this link: the-underlying-connection-was-closed-an-unexpected-error-occurred-on-a-send-ssrs-2008.
Best regards,
Aniya
Please sign in to rate this answer.
PN 141 Reputation points

2022-09-29T13:00:04+00:00

I'm not the original poster, but I am also having this issue. I am running SSL and need to due to reports embedded in intranet webpages. My secure connection level is set in the configuration file to zero already.

These reports have run for months without issue. No changes were made to them. No updates were taken to the server or my local machine. Overnight the map layer stopped working. This feels like an issue on the map server end.

It just started a week ago and I'm glad to see that I'm not the only one experiencing it.
Sign in to comment
Dejan Milic 41 Reputation points

2022-09-29T10:26:46.843+00:00

Hi @AniyaTang-MSFT

The reports are deployed just fine, It does not look like a server URL issue.

The server is not running SSL

and the SecureConnectionLevel is set to "0"

Regards,

Dejan
Please sign in to rate this answer.

1 person found this answer helpful.
PN 141 Reputation points

2022-09-29T16:34:11.337+00:00

Are you still receiving the same error? At some point today mine switched over to " The request was aborted: Could not create SSL/TLS secure channel."

AniyaTang-MSFT 12,321 Reputation points Microsoft Vendor

2022-09-30T08:15:10.717+00:00

Hi @Dejan Milic
Did this method work? Or are there other problems?

PN 141 Reputation points

2022-10-03T12:08:55.14+00:00

No, this method did not work. Both @Dejan Milic and I have seen the error change to "The request was aborted: Could not create SSL/TLS secure channel."

Something has obviously changed on the server side. What are the next steps?

Jane Fleming 11 Reputation points

2022-10-03T16:52:20.733+00:00

Same issue here - SQL 2017 on Windows Server 2016.

Has also changed from a single error line to the mosaic shown in @Dejan Milic 's screen shot.
Our server is serving TLS and chrome verifies that our browser connections are TLS 1.2

But that's what we're SERVING.
It does not give any indication as to what the SSRS engine is using when it's behaving as a CLIENT accessing the maps on Bing.

I moved the same report to an instance of PBIRS running SQL 2019 on a Windows Server 2019 host and that same report works fine on that environment and generates without the errors.

The issue with the SQL2017/Windows2016 report started about 2 weeks ago, after this report had been running fine for more than 2 years.
Sign in to comment
Dejan Milic 41 Reputation points

2022-09-30T12:49:45.95+00:00

Hi @AniyaTang-MSFT

The settings were good in the first place, so It did not help.

However, I'm now getting the same errors as @PN , Although I did not change anything in the settings:
Please sign in to rate this answer.

1 person found this answer helpful.
AniyaTang-MSFT 12,321 Reputation points Microsoft Vendor

2022-10-04T01:40:44.323+00:00

Hi @Dejan Milic @PN
The request was aborted: Could not create SSL/TLS secure channel. This error can occur if you are working on an application which will securely connect with another application using SSL/TLS certificate. It basically says, "the SSL/TLS/HTTPS connection initialization failed for one of many possible reasons".
It looks like you are using a TLS connection. The method I mentioned cannot be used under running TLS connections. Please return your backup file.
May I ask whether this error "The underlying connection was closed" occurs only in this report containing map, or in all reports. If it only occurs in reports with maps, this may be a problem with the map. If it occurs in all reports, please check that your TLS connections are configured correctly and the certificates are not expired. You can refer to this link: configure-ssl-connections-on-a-native-mode-report-server.

PN 141 Reputation points

2022-10-04T14:01:21.42+00:00

@AniyaTang-MSFT @Dejan Milic

This is happening for me on all reports that have maps. The other parts of the reports work fine. I am able to pull in images via the Google Maps API, but native SSRS maps (Bing) do not work.

I used the link you provided and checked the TLS configuration. My certificates are not expired and the links in report server manager work as expected. We are not running IIS on the same machine. We have checked all of the boxes.

Are there any other steps that I can check?

@Jane Fleming appears to be reporting an identical issue. These reports ran fine for the past year, no changes were made to the server, no upgrade taken, and suddenly two weeks ago the maps stopped working. The error changed the same day as @Dejan Milic reported from "connection was closed" error to TLS error. Evidence points to something going on with the interface used between SSRS and Bing, and not limited to my environment.
Sign in to comment
Dejan Milic 41 Reputation points

2022-10-04T06:00:52.607+00:00

Hi @AniyaTang-MSFT

Thank you for your feedback.

To my limited knowledge, nothing points to the conclusion that the SSL/HTTPS connection is configured or in place on this Report Server.

The secure channel error occurs only with Bing Map layer component of the report, all other report parts are rendered with no issues at all.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment