Reporting Services Bing Map – Unable to connect to the remote server

A new feature that is now available in Reporting Services 2008 R2 is the Map report item.  Along with this report item is the ability to display Bing maps.  This is a very neat feature and a very interesting way to visually display information to end-users leveraging their data.  Here is an example that Robert Bruckner put together last year that he made available – RS Maps with Spatial Data and Bing Maps

 

Once you have this created within BIDS or Report Builder 3.0 you are going to want to share this with your end-users, so you will need to deploy this to the server.  Once you deploy it to the server you test it out and you end up with this (not in all cases, but this could potentially happen in your environment)

Bing Map error: “Unable to connect to the remote server”

Hmmm, what is going on?  The report seems to be running, but the map is not being displayed.  After taking a look around it turned out that a proxy was being used, so some additional configurations were needed on the Report Server in order for the Bing map integration to work – Proxy Settings for Map Controls with Bing Maps.

So I went into the Report Server web.config file, which is located in the ReportServer install folder – see image below for the path) and added the proxy information (NOTE: always make sure you make a backup copy of a config file before making a change and utilize a basic text editor like notepad, not an RTF editor like wordpad).

   <system.net>
         <defaultProxy enabled=”true” >
             <proxy bypassonlocal=”True” proxyaddress=”http://myproxy:port”  />
         </defaultProxy>
     </system.net>

Once I had this information added (you will need to replace the ‘myproxy:port: information with the valid information for your environment) I went back and refreshed the report and we were back in business.  No reboot or restarting of the service needed, the Bing map was able to be displayed and everything was back to normal.

About these ads