Hi Everyone, I've received an e-mail address from one person experiencing this problem and have not been successful at finding anything in the logs that would point to the problem. I've also tried various tests on my own and have been unable to recreate it with my any of my accounts. I'm in the process of writing a test that will use a bunch of different test accounts to see if I can find an account that will reliably recreate this issue.
In the meantime-- if there is anyone who is comfortable doing a packet capture and sending me the data from that--- that would be extremely helpful. Please note: if you send me a packet capture with the full Authorization header, the token will have access to your account data. If you (understandably) do not wish to do this, you may edit the Authorization header, but please note if you have done so. Anything that I can do to be able to recreate or document this problem will let us move one step further to finding a solution. BTW - If any of you have sent me private e-mails with more information on this topic and have not yet received a response-- please e-mail again. Lastly -- is this consistently occurring for each of you? Or is the problem intermittent? It would be best if each of you could run the code and give me the last time the code was run and failed. Thanks everyone very much for your patience and detailed debugging information, -Ryan On Apr 26, 11:41 pm, "Kulvinder Singh" <[EMAIL PROTECTED]> wrote: > Any updates ? > > On 4/26/07, Ryan Boyd (Google) <[EMAIL PROTECTED]> wrote: > > > > > Hi Mark, > > > And, actually, if you could check with your colleague and see if you > > can send me the account name that was able to authenticate correctly, > > I'd appreciate that as well. > > > Thanks, > > -Ryan > > > On Apr 26, 8:48 am, "Ryan Boyd (Google)" <[EMAIL PROTECTED]> wrote: > > > Mark, > > > > Thanks for the additional information Mark. > > > > Can you please send me the username (privately if you wish) that you > > > are using when you're not able to authenticate? > > > > Thanks, > > > > -Ryan > > > > On Apr 26, 8:42 am, Mark Milliman <[EMAIL PROTECTED]> wrote: > > > > > Thank goodness someone else is seeing this problem. I have been > > > > experiencing it for a few days now. I have been receiving > > > > authorization failures on an Outlook add-in using .NET and my GDT > > > > calendar gadget. Both are sending me replies that authentication > > > > failed. I knew my user ID and password were correct. I changed my > > > > password, but that did not help. I even logged into another account > > > > and received the same problem. A colleague tried the same tests in > > > > another state and everything worked fine. The only differences that I > > > > could detect was that his UID was his gmail ID and mine was my e-mail > > > > address and he is located in a different state possibly served by > > > > different servers with a different version of the API. > > > > > I tried to authenticate myself and get a token just to retrieve my > > > > calendars and add an appointment. Both failed. The only way I can > > > > view my calendar is to open Firefox and view it. GDT and Outlook are > > > > useless because of this issue. Until last night, I thought that the > > > > problem was on my end. Now I am certain that it is an API issue. > > > > What has changed from Google's perspective? When can we see a > > > > resolution? > > > > > Thanks, > > > > Mark --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Calendar Data 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-calendar-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
