Unable to Update a Recurring Calendar Event with the new API

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Event evt = CalServ.Events.Get(calId, id).Fetch();
2.Event updatedEvent = CalServ.Events.Update(evt, calId,id).Fetch();/
3.Error 503

What is the expected output? What do you see instead?
I expect the calendar event to update.  All I am doing is fetching an event and 
then calling update on it.  If the event is recurring, it errors out, if it 
isn't it works fine.
the error is "The remote server returned an error: (503) Server Unavailable."

What version of the product are you using? On what operating system?
Code from December 10, 2011. Windows 7.

Please provide any additional information below.

Original issue reported on code.google.com by supp...@sapphiresoftware.com on 25 Jan 2012 at 5:40

[GoogleCodeExporter]

As an update, I tried this in a new project using Calendar version 
1.1.4344.23403 and client api version 1.1.4344.23417 and it worked. I have a 
strongly named assembly, so I cannot use the binaries (unless you have strongly 
named bins somewhere, that would be swell).So I had to download the code and 
compile it.  I don't see a project anywhere for the calendar, so I added the cs 
file to my project.  I suspect something got broken in the translation (or the 
code file from December 10th has issues...)

Original comment by supp...@sapphiresoftware.com on 25 Jan 2012 at 5:51

[GoogleCodeExporter]

Sorry, my test project wan't doing a fetch.  I get this error with the binaries 
from 11/23.  Very simple code.

            Events es = service.Events.List("primary").Fetch();
            foreach (Event e in es.Items)
            {
                if (e.Recurrence != null)
                {
                    service.Events.Update(e, "primary", e.Id).Fetch();
                }
                else
                {
                    service.Events.Update(e, "primary", e.Id).Fetch(); ;
                }
            }

Errors with 503 error if recurring, works fine if not.

Original comment by supp...@sapphiresoftware.com on 25 Jan 2012 at 3:10

[GoogleCodeExporter]

I found a work around.  In order to get recurrences to work properly, you must 
include a time zone on the start and end for the main event.  This should not 
be needed if it is an all day event, and you don't send one down if it's an all 
day event, so that might be something you want to look at at some point. I set 
the TimeZone to UCT for all day events and it works now...

Original comment by supp...@sapphiresoftware.com on 25 Jan 2012 at 11:42

[GoogleCodeExporter]

I'm closing this as a service issue, it appears that the timezones are required 
properties for recurrences.

Original comment by asky...@google.com on 25 Apr 2012 at 7:08

• Changed state: ServiceIssue