Currently Being ModeratedFeb 14, 2013 2:42 AM (in response to Waspy9999)
Apple opened a similar Case for exception to a recurring calendar event:
When you respond to an exception to a recurring calendar event with a Microsoft Exchange account on a device running iOS 6.1, the device may begin to generate excessive communication with Microsoft Exchange Server.
Currently Being ModeratedFeb 25, 2013 10:51 AM (in response to Waspy9999)
In dealing with events missing either only on my iPhone or home computer, I have realized that it is mainly with recurring events that I am having issues since the push of the last OS last week or so.
Has anybody noticed this?
Appple People: Do you know anything about it?
Thanks in advance!
Currently Being ModeratedMar 6, 2013 7:41 AM (in response to fordfamily)
I think my issue is that, if I make a change to a single occurance of a recurring meeting, the change to the single occurance is not reflected on my iPhone calendar.
Any work around for that?
Currently Being ModeratedMar 7, 2013 5:51 AM (in response to Waspy9999)
Thanks very much! My problem was different, the sync issue was persistent for all types of events. However, disabling PUSH did the trick!
@ Apple support, is there an explanation to this 'defect' in the PUSH functionality?
Currently Being ModeratedApr 10, 2013 10:50 AM (in response to Waspy9999)
@Waspy - Thanks for the trick of turning off "Push". I was having issues with recurring meetings that were forwarded to me on behalf of someone else but this fixed it. I didn't have to recreate the meeting invite... I was able to turn off "Push" in my phone settings then Right Click the meeting in Outlook and select "Accept" for the Series and Do Not Send a Response. The meeting appeared on my phone and nobody else had to know anything
Currently Being ModeratedDec 3, 2013 9:14 AM (in response to bartopiola)
A simple solution for me.
Many of these issues are much more techy-y than my little calendar issue, but my solution might work for some of you.
I have Windows 7, MS Outlook 2010, iPhone 4, iOS 6.
For me it was birthdays, anniversaries and anything that was created with a "yearly recurrence" pattern (in Outlook), and "no end date" that would all be one day late on my iPhone. Go into Outlook, open a "yearly recurring" item (open the series, not just "this occurence"), click on "Recurrence". Change the "Range of Recurrence" from "No end date" to "100 occurences". Or whatever you want - you can go up to 999. I figured 100 would outlast me, my relatives AND my Outlook. I went through and changed one month at a time, refreshed and good so far. Just remember that any new yearly event needs an end date.
Currently Being ModeratedJan 16, 2014 1:39 AM (in response to Eric Q Public)
So we are comming up to the 5 year anniversary, from 3.0 to 7.0.4, of this bug with no general solution, which really makes the iPhone unusable as a business phone since you can never trust it. Oh how many times I have been stranded after one meeting not knowing where the next is and there has been a few close calls where I nearly forgot about important meetings.
Personally I have tried all the tricks in this thread (those available to the end user) and nothing has worked.
Currently Being ModeratedJan 20, 2014 3:18 PM (in response to BillNicholson)
I have to agree with Bill here. It is a scandal that Apple has not fixed this problem over all the years. Early December 2013 when accepting a recurring event on my iPhone 5 running iOS 7.0.4, without knowing it, my iPhone generated so much traffic it crashed one of my company's exchange servers crashed and it seems my account alone generated a 5Gb log on the server. The only thing I noticed was that my phone ran excessively hot and that my provider texted me the next day I exceeded their fair use policy and my data was disabled the rest of the month. Great, it was early December. IT/Exchange support of my company was also not pleased, because 6,000 colleagues were without mail for 2 hours because of my iPhone.
Worst is, I continue using Apple products. Because otherwise I love them. I am typing this from my brand new iPad mini retina, and reason I searched and found this forum is because 80% of the appointments in my calendar won't appear in my iPad agenda. Tried all the tricks in the book.
My company (26,000 employees spread on 5 exchange servers) is not happy with this at all. They changed policy now, all company phones are now Nokia's running Microsoft. Too bad Apple, this is what you get when not solving your bugs!
Currently Being ModeratedMar 13, 2014 7:29 AM (in response to fordfamily)
I've had similar issues - although my email and contacts were syncing with Exchange without issue, in iOS7 I developed a one-way problem with calendar sync.
Appointments created on my iPhone were syncing fine to my Exchange server, and were then visible in outlook on my PC.
However items created in Outlook were not syncing to the iPhone.
I'm running iOS 7.1 on an iPhone 5; plus Outlook 10 on a Windows 8.1 machine connecting to Exchange on Small Business Server 2003.
I found a solution here.
On the PC, go to your calendar and right-click the Calendar folder. On the Permissions tab, change the default Permissions from "none" to "Reviewer". Apply changes.
Then on the iPhone, remove and add back the calendar in Settings.
I have 3 separate calendars on my exchange server and had to do this for each one. When I only did it for one calendar at first, this was the only one which appeared on the iPhone. So, it seems to me that this was definitely the culprit.
Interesting that this problem only reared it's head since the iOS7 update. Calendar was working just fine for me in iOS6.
Currently Being ModeratedApr 15, 2014 5:45 PM (in response to BillNicholson)
We experience this issue randomly with some our executives as well. It seems a calendar item that is changed by an assistant is not always synced. It is totally random and has been difficult to diagnose which meetings will be affected by this bug. I really cannot believe that this issue has been happening this long with NO SOLUTION! As an IT professional, it is very frustrating to have an issue that can have major negative implications, not addressed and be completly out of your control. Apple, PLEASE fix this!