outlooksyncclient.exe error - FIX/SOLUTION - due to iPhone Calendar bugs

[dritchie]

I’ve noticed a lot of discussion on a lot of boards from iPhone users relating to outlooksyncclient.exe problems.
Before you try any of the draconian solutions suggested of reinstalling iTunes, MS Outlook, changing time zone settings or wiping your entire iPhone, it might be worth reading on.
I’ve had the problem for a number of weeks now and only just managed to resolve it. Basically the iPhone calendar seems to suffer from two major bugs:
1) First it allows the creation of events that go back in time! I’m not 100% certain how it happens but I think it’s if for example you create a 2 day event starting on a Thursday and ending on Friday, and then move the start day from the Thursday to a Saturday. For some reason the end day stays as the Friday, even though it appears (in 'List' view) on your iPhone as the Sunday. Clearly you can’t have an event that starts on one day but ends the day before!

2) The second problem is that all of the recurring events I had (weekly, monthly & yearly) although appearing fine on my iPhone , on closer inspection after clicking on an event in MS Outlook I realised that they all had a message saying “all instances of this event occur in the past”. Clearly this cannot be the case for recurring events that have no end date!
Anyway, the bottom line is that you just have to go through your calendar in Outlook a day at a time and open EVERY event to make surely it doesn’t fall into one of the above two categories, then delete it. Naturally it’s simple enough to re-create a single event or series if needs be, which should then be fine. The caveat is to check EVERY event – single or series – don’t assume and make sure to check everything….it’s took me two days going back to the date in the calendar that I bought my iPhone to check & re-check until I was sure I hadn’t missed anything.
No idea if it’s a Microsoft or Apple issue but this has worked for me so I thought I’d let folks know as no one else seems to have posted a (sensible) 100% guaranteed solution.
Regards
Dave