Skip to main content
jonathank23936802
jonathank23936802
Participant
August 22, 2015
Question

Receiving error #2032 when using maps on ticketmaster.com

  • August 22, 2015
  • 2 replies
  • 2205 views

I have tried IE, Chrome, and FF.  This is on a Windows 7 Pro system.  Did usual steps of clearing cache and reinstall of Flash.

    This topic has been closed for replies.

    2 replies

    D
    dcampagna72
    Participant
    October 25, 2015

    This is still an ongoing issue for me with the Ticketmaster website. I have tried everything, including removing every single Adobe product, from the entire CS3 package to Adobe Reader, and reinstalled Flash. It didn't make any difference at all. I am using Mac OS El Capitan 10.11.1 and the issue is cross-browser, Safari, Chrome and Firefox. This is incredibly frustrating.

    jonathank23936802
    jonathank23936802Author
    Participant
    August 24, 2015

    Additional info - some testing this morning shows the feature as working so possible it was their issue.  I did do some Google Chrome browser tests with the "more tools" option of java console on.  it showed an error trying to pull a source but getting a 404 not found. See attached image.  This may have been the cause.  I was hoping someone would be able to provide a true "root cause" so I would be able to better understand this in case it happens again.

    W
    WhoopsieDayze
    Participating Frequently
    August 25, 2015

    I got a reply on my 2032 thread from Adobe to clear my cache and try it, it should be fixed.  I did so and my 2032 errors seem to be gone. 

    jonathank23936802
    jonathank23936802Author
    Participant
    August 25, 2015

    Thank you for the reply.  Greatly appreciated.  So far the site seems to be working normal and the maps show.  I had tried the clearing cache as well with no luck.  The issue was seen on several wkstns. using different browsers.  The theory I am working on since it was random is that perhaps they had an issue on tier end with one or more of their servers and depending on when it was contacted by a client and whatever load balancer it hit would direct to a bad one and cause the error.  I would find it hard to believe that so many of they systems here would have a problem and we did not do any patching/updates to change the setups.  Other sites that use flash were working fine.  Fingers crossed that we do not encounter it again.  If I get more info on the issue I will post it here.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices