topic Re: PrintTask: Unable to connect to Microsoft Bing service in ArcGIS API for Silverlight Questions

PrintTask: Unable to connect to Microsoft Bing service

JaredA — Mon, 22 Apr 2013 22:21:47 GMT

I'm using PrintTask and PrintParameters to create a PDF of my map services. Recently the PrintTask fails with this error "Unable to connect to Microsoft Bing service. Authentication failed".

Any suggestions on how to get the PrintTask / PrintParameters to authenticate the Microsoft Bing Server?

Re: PrintTask: Unable to connect to Microsoft Bing service

ChrisSaylor — Wed, 15 May 2013 17:49:28 GMT

I had the exact same problem. Monitoring web traffic showed that it was attempting to connect to serverapi.arcgisonline.com/veadaptor, and receiving an authentication error from that as well. Pasting the JSON created by the PrintTask into the rest endpoint fails, i.e.

   "operationalLayers":[
      {
         "opacity":1,
         "visibility":true,
         "type":"BingMapsRoad",
      },

However, if you modify this and include your Bing key

   "operationalLayers":[
      {
         "opacity":1,
         "visibility":true,
         "type":"BingMapsRoad",
         "key":"<insert key here>"
      },

it works fine and the map is exported correctly. I talked to ESRI support and they said that Bing authentication procedures is changing rather quickly. Unfortunately, right now the JSON created by the PrintTask doesn't include the key. They logged it as a bug [#NIM091676 Bing layer JSON needs to include key and made it sound like this is a pretty time-sensitive fix and that it should be included in the next release.

Re: PrintTask: Unable to connect to Microsoft Bing service

StevenHumphries1 — Thu, 27 Jun 2013 17:57:19 GMT

Yes. Same problem here too. Would be pleased to hear if there is a work around. A flex viewer using the same export service works ok.

Re: PrintTask: Unable to connect to Microsoft Bing service

StevenHumphries1 — Fri, 28 Jun 2013 08:47:52 GMT

Also discovered that the Silverlight printing tool that was working until recently continues to work when connected to one of ESRI's test servers rather than my own server. Does this suggest that its a local server problem? Sorry couldn't find a record of the registered bug on the system. Are ESRI seeking a solution?