Sync Service error for one user - "running error count=1" & "Free Busy Range Months must match"

[skr...@systemsbiology.org]

I have an issue with the Web Service for only one user. All other
Google Apps Calendar users’ free/busy information is viewable by
Exchange users. I get the below information in the SyncServer.log
file.

2009-04-23 14:09:55,073 [Sentinel Thread] INFO
Google.GCalExchangeSync.Library.SchedulePlusFreeBusyWriter - Creating
F/B message. [User=us...@systemsbiology.org]
2009-04-23 14:09:55,073 [Sentinel Thread] INFO
Google.GCalExchangeSync.Library.Util.BlockTimer - [Timer] -
WriteFreeBusy - Total Execution Time: 0 ms.
2009-04-23 14:09:55,073 [Sentinel Thread] ERROR
Google.GCalExchangeSync.Library.GCalSyncProcess - Error occured while
executing sync process for user 'us...@systemsbiology.org'. [running
error count=1]
System.Exception: Free Busy Range Months must match
at Google.GCalExchangeSync.Library.FreeBusyConverter.AddDateRange
(Dictionary`2 result, DateTimeRange r)
at
Google.GCalExchangeSync.Library.FreeBusyConverter.ConvertDateTimeBlocksToBase64String
(DateTime startDate, DateTime endDate, List`1 freeBusyRanges, List`1
monthData, List`1 base64FreeBusyData)
at
Google.GCalExchangeSync.Library.SchedulePlusFreeBusyWriter.ConvertEventsToFreeBusy
(ExchangeUser user, AtomEntryCollection entries, DateTimeRange
coveredRange, List`1 busyMonthValues, List`1 busyBase64Data, List`1
tentativeMonthValues, List`1 tentativeBase64Data)
at
Google.GCalExchangeSync.Library.SchedulePlusFreeBusyWriter.SyncUser
(ExchangeUser user, EventFeed googleAppsFeed, ExchangeService
exchangeGateway, DateTimeRange window)
at Google.GCalExchangeSync.Library.GCalSyncProcess.SyncUsers()

Any ideas what is causing this error and preventing this user’s free/
busy information from being viewable by Exchange users? Setting the
logging level to debug gives the same set of errors as shown above.

Thanks,
Scott

[John Leen]

Hmm… this is interesting, and it certainly sounds like a bug in the Sync Service code. Thanks for the logging info.

Does the user in question have any particularly long events in their calendar, possibly one spanning multiple months? Or perhaps a shorter event, but one which crosses a month boundary? The crash seems to be occurring in the code that handles those cases. If we could figure out the event that's causing the error, we could try to isolate and fix the bug—and in the short term, work around it by breaking that event into two or more events that don't cross month boundaries.

Sorry you're hitting this bug. Let's see if we can track it down.

Thanks!
John

[Scott I. Kraft]

John,

 

I wanted to follow-up on this issue.  I worked with the user and we could not identify any event as you described and left this project alone until this week.  We are now no longer receiving the error and we are able to see this user’s free/busy information.  I suspect that whatever event caused the error is either I the past or has been deleted.

 

Thanks,

Scott

[John Leen]

Scott,

Thanks for following up. Glad to hear it's working now! It does sound
like there must've been a particular item that the Sync Service didn't
like. If it happens again, please let me know—maybe we can narrow it
down.

Thanks!

John


On May 15, 3:42 pm, "Scott I. Kraft" <skr...@systemsbiology.org>
wrote:

> John,
>
> I wanted to follow-up on this issue.  I worked with the user and we
> could not identify any event as you described and left this project
> alone until this week.  We are now no longer receiving the error and we
> are able to see this user's free/busy information.  I suspect that
> whatever event caused the error is either I the past or has been
> deleted.
>
> Thanks,
>
> Scott
>
> From: google-calend...@googlegroups.com
> [mailto:google-calend...@googlegroups.com] On Behalf Of John
> Leen
> Sent: Friday, April 24, 2009 10:33 PM
> To: google-calend...@googlegroups.com
> Subject: Re: Sync Service error for one user - "running error count=1" &
> "Free Busy Range Months must match"
>

> Hmm... this is interesting, and it certainly sounds like a bug in the

> Sync Service code. Thanks for the logging info.
>
> Does the user in question have any particularly long events in their
> calendar, possibly one spanning multiple months? Or perhaps a shorter
> event, but one which crosses a month boundary? The crash seems to be
> occurring in the code that handles those cases. If we could figure out
> the event that's causing the error, we could try to isolate and fix the

> bug-and in the short term, work around it by breaking that event into