Sync Service reports success, but Exchange Calendar not updated

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Stopped Google Calendar Sync Service.
2. Deleted log and xml files.
3. Started Google Calendar Sync Service.
4. Reviewed resulting SynchService.log (attached).  Everything contained 
indicates successful synchronization to Exchange. 

Note that test was conducted for only a single active directory user (filer 
cn=Scott Spamalot).

What is the expected output? What do you see instead?

Expected to see appointments for test user that were created in Google Calendar 
successfully viewable within Exchange. Instead, I see none of the Google 
Calendar created appointments viewable in Exchange (from Outlook or Webmail).

What version of the product are you using? On what operating system?

Google Calendar Syncy Connector MSI 1.3.1 running on Windows 2008 DataCenter R2.
Exchange 2003 SP2 running on Windows 2003 Standard SP2.

Please provide any additional information below.

- Google Web Service connector is working and running fine.
- Diagnostics.aspx Ran successfully for all 4 tests.
- Included log snipet from IIS log.  First response is 401, second one 207.  
Assumed if this was an authentication issue it would have bombed out and not 
returned the 207?  
- Certainly feels like WebDAV to Exchange portion of transaction is not 
completeing successfully...but don't know where to go look?

Beating my head against the wall.  Guidance on where to look appreciated.  
Thanks.

Original issue reported on code.google.com by Scott.Li...@eaglecounty.us on 23 Mar 2011 at 5:50

Attachments:

• ex110323.log
• SyncService.log

[GoogleCodeExporter]

OK...as expected, the answer is as follows:

- Synch service did work successfully, my testing was flawed (stupid, stupid me)
- Had to take the time to understand exactly how flow of information for 
Free/Busy store works in Exchange 2003 (kind of contorted).
- Individual end user appointment data and the Exchange free/busy data store 
are distinct and separate (depending on timing and circumstances, might give 
two different answers).  Free/Busy store in Exchange 2003 is published 
periodically by individual Outlook clients to the Exchange Free/Busy store.  
The publication is a complete overwrite each time (not an incremental update 
--- this is important to understand).  
Issues with my two test accounts causing me grief:
1. Had my dummy account suppressed in AD with "Hide from Exchange" check box 
which precluded me from getting free/busy information returned.  Once I 
unchecked this box, making free/busy information available to AD, testing 
results we're as expected.
2. When logging into Outlook and testing as myself...my Outlook appointment 
data (the pre-Google synch version) would synchronize to the free/busy store, 
thus overwriting my Google synch data and making it look like the Google synch 
didn't work.  Using yourself for testing this process is a bad idea.

Lastly, don't proxy an Exchange/Outlook user's "calendar" directly (as you 
won't see the Google Calendar information there, that's not what Google 
connector synchronizes).  As indicated previously, the free/busy store lives 
distinct and separate from individual calendar appointment information.  We're 
planning on turning off all end user delegated Exchange Calendar permissions 
for our pilot users, so that remaining Exchange users don't get confused by 
attaching directly to Exchange calendars.

Scott

Original comment by Scott.Li...@eaglecounty.us on 30 Mar 2011 at 2:44