none
500/Internal Error requesting Infrared weather layer tiles RRS feed

Answers

All replies

  • Hello Kevin,

    We are checking on this issue internally and update you as earliest.

    I just tried to repro the issue which you have mentioned above and not observing any 500 error messages.

    Which browser are you using? Please refer to the steps How to Verify Your MSDN/TechNet Forums Account So that You Can Post Images and Links.

    Tuesday, January 21, 2020 7:04 AM
    Moderator
  • Hi Ashok,

    Maybe it's an issue with servers for our region? We're in Dublin Ireland.

    Browsers we're seeing this issue on are (basically every browser we tried):

    * Ubuntu, Chrome 79.0.3945.117 (64-bit)
    * Ubuntu, Firefox 72.0.1 (64-bit)
    * Windows 10, Chrome 79.0.3945.130 (64-bit)
    * Windows 10, Firefox 73.0b7 (64-bit)

    Re. account verification: as per instruction in link you sent, I've sent an email to fissues [at] microsoft [dot] com but it hasn't been processed yet.

    There's a HAR file from the demo page above at: https://www.dropbox.com/s/dcqbo816tk0gzf6/azuremapscodesamples.azurewebsites.net.har?dl=0

    Regards


    • Edited by Kevin_Flood Tuesday, January 21, 2020 4:38 PM
    Tuesday, January 21, 2020 9:25 AM
  • Hello Kevin,

    Thanks for the additional information. We will check and update you. Appreciate your patience in this regard.

    Tuesday, January 21, 2020 9:48 AM
    Moderator
  • I've just noticed that this seems to be time-based. 

    For example, one request that failed was:

    GET https://atlas.microsoft.com/map/tile?subscription-key=tTk1JVEaeNvDkxxnxHm9cYaCvqlOq1u-fXTvyXn2XkA&api-version=2.0&tilesetId=microsoft.weather.infrared.main&zoom=4&x=4&y=5

    I copied the same url to another tab and it worked:


    Could it be be hitting 429/Too many requests somewhere internally but is being wrapped in a a generic 500/Server Error response?

    Tuesday, January 21, 2020 4:57 PM
  • There is an active service issue with the weather tiles that the Azure Maps engineering team is investigating. 
    Wednesday, January 22, 2020 4:20 PM
  • A fix for this issue has been deployed. 
    • Proposed as answer by Ricky_Brundritt Wednesday, January 29, 2020 10:51 PM
    • Marked as answer by Kevin_Flood Thursday, January 30, 2020 8:23 AM
    Wednesday, January 29, 2020 10:51 PM
  • Working fine now. Thanks, Ricky.
    Thursday, January 30, 2020 8:24 AM