Huge forehead slap! At some point someone started sending out a new QA URL - http://kaiser-perm-com.tmpqa.com/
Previously the URL was sent around as http://kaiser-perm-careers.tmpqa.com/ Realizing that there was a discrepancy someone added the new host headers to IIS - not realizing the issue it could cause on the locations page. Google Maps is domain specific. So when the developer generated a new key, he did it for the –com version. That’s why all users using the –careers version suddenly got this error. *Sigh* Occams Razor strikes again. Thank you for your help. Larry. On Feb 16, 6:14 pm, "[email protected]" <[email protected]> wrote: > On Feb 16, 2:41 pm, Larry Viezel <[email protected]> wrote: > > > A new issue cropped up on a QA site and I really can use some > > guidance. > > >http://kaiser-perm-careers.tmpqa.com/locations.aspx > > > We started getting the following error on *some* user's machines: > > > "This web site needs a different Google Maps API key. A new key can be > > generated athttp://code.google.com/apis/maps/."; > > > I stress *some* in that it was happening on two of my developer's > > machines and one of my project manager's machines by not on any other > > developers machines or any of the testing machines. > > I get it here on IE6. > > > > > > > > > It was not browser specific. It was happening on these machines in > > both IE and FF for example. And it was not server specific: The > > machines were connected to the same server in the QA cluster as the > > machines it was working on. When we compared the two machines using > > view-source, the source was the same. > > > One of the developers regenerated the API key using a different Google > > account and put it into the web.config and it fixed the problems for > > the developers that were having the problem. But now the problem is > > happening for the other developers. It appears that the user groups > > have switched - the ones having the problem before are fine now, and > > the ones who were fine before are getting the error message now. > > > The old key was: ABQIAAAAVdoSW9XrzLC03RKrnwizJRQpeQ5lSlF- > > eedjn8uF4XBE4AWDUhRZ1HV--acV9vECATj6Q_lr1x59Yw > > > The new key is: > > ABQIAAAASxYceLW_fyBetNOoPSxsQhTzq9PrtfPI2cwhANwEFSJnKMkiaBSsAj2eZ8ss7QtiqEQ > > X9mwBn7Mt_w > > > We have to launch this site to production in the next few days and I > > fear that any changes we launch might promote this problem as well. I > > am scratching my head on this one and really have no clue why this > > would happen. Any help would be appreciated. > > We need more information. > > 1. What URL did you submit for the keys above? It looks to me like > they were generated for different URLs. > 2. What URL are your developers accessing when they get the error > message? Is window.location.host the same? > > A key for kaiser-perm-careers.tmpqa.com or tmpqa.com should work for > all pages on the domain. > > -- Larry -- You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en.
