Skip navigation

Devices running iOS 6 are cancelling calendar appointments sent to distribution lists

38173 Views 79 Replies Latest reply: Jun 11, 2013 10:41 PM by lachlanfrommelbourne RSS
  • Collaboration Calculating status...

    We opened a case with Apple and Microsoft as well.  Apple needs to step up to the plate and fix all of these calendar issues. That arrogant stance is not sitting well with Enterprise customers.  Fix is Apple!!!

  • Turismon Calculating status...

    Yeah, really, this isn't the only iPhone bug either, I've had plenty of magically dissapearing calendar entries from meeting updates etc. crop up and it always ends up being the persons iPhone causing the problem.

  • Small1ng Calculating status...

    I might have found a temporary solution that worked for a day now. Excuse me for my bad English, but this is what we have done:


    On the settings menu go to Email, contacts and calander.

    Scroll down to Calander's and check if 'New invitation alerts' is activated (On).

    If so, disable it.

    Scroll down a bit further to 'Shared calendar alerts' and disable it.


    We're testing this settings since yesterday on 3 of the 5 users with calendar problems. Today we will configure the other iPhones. One of them cancelled an appointment last night. Just like the bug we know since ios6.

  • LisaNB Calculating status...

    We starting having this same issue on Friday, October 5, 2012.  We are running Exchange 2003 and Exchange 2010. Users declined the message in Outlook and cancellations were sent to everyone and the organizer was changed to them.  It's now missing from people's calendar's and the "new" organizer is getting the replies.  It seems to be spreading and really starting to mess things up!  They did not accept or decline the appointment from idevices but they do have iPhones and iPad that were updated to iOS6.  I'm currently working with Microsoft but no resolution yet.

  • singebad Calculating status...

    For those of you who have Apple cases open, can you please reply back with the case number? I'm in communication with my contacts at Microsoft and Apple is asking for case numbers. I have not personally opened a case with Apple support.


    If you can supply these, it may assist in getting more exposure on this issue.



  • Shaggy2002 Calculating status...

    I have gone through the checklist provided by BishopTJ and I found that only 5 users in my organization are not set to automateprocessing.  One of the 5 users is the only user so far that appears to be affected by this bug of cancelling other meetings that other people are organizers to.  This particular user also has a delegate that responds to all of his meetings for him.  I have updated that user to now autoupdate rather than none and hope that this will correct the issue.  Thanks for your help BishopTJ!

  • Turismon Level 1 Level 1 (0 points)

    Would love to get my hands on that caldiagviewer but the download link doesn't work and can't find it online .

  • fausttiger Calculating status...

    This is very similar to an issue we have under iOS5...  Exchange 2010...


    1) Person from outside your organization sends an invite to someone inside your organization

    2) someone forwards the invite to you

    3) you respond

    4) YOU are converted to be the organizer...

    5) and now being the organizer, everyone gets a reply from you... as the organizer.   Then they start replying to you!


    For Exchange invites from outside our organization (as opposed to internal meetings),  we mostly use Outlook 2011 to accept... or risk corrupting up the invite for all.



    Note to BishopTJ:

    So... If your people also being converted TO THE ORGANIZER... hence, when you decline, you cancel the invite for everyone?    Since when you cancel (delete) your now own meeting, it sends a cancellation notice to everyone on the list.

  • atlauren Level 1 Level 1 (0 points)

    We had a similar event occur at my site.  In this case it was between two Exchange installs, on different GALs.  Both orgs are on Exchange, on CAS and Mailbox servers.  The user who sent the cancel was invited via a valid SMTP address that happened to *not* be his windowsemailaddress.


    I'm chasing a theory that this is actually an iMIP/iTIP issue in Exchange, and not necessarily an iOS issue.   It could be that Exchange permissively allows EAS clients to do something in appropriate, but fundamentally the calendar system should NOT permissively allow the hijacking of meeting organizer.


    If you've seen this happen:


    Are organizer and user-who-cancels on the SAME Exchange org and GAL?

    Was the invitation sent to their windowsemailaddress?

    (Or perhaps another proxyaddress?  or a valid Sendmail address that is NOT their windowsemailaddress?)




    higher ed IT guy

  • fausttiger Level 1 Level 1 (5 points)

    Andrew /atLauren


    While it happens on my iOS 5.x iPhone... I believe it also happens on Lion iCal and/or Mail.   So not necessarily iOS.  However Outlook 2011 Mac appears safe to accept invites from outside your Exchange.     Receiving a 'forwarded' invite also appears to be a factor, but not clear that's the only case.


    So  sender and replier are NOT in the same Org.


    I should note again my experiences are all with Exchange 2010.

  • fausttiger Level 1 Level 1 (5 points)



    per your Microsoft TAM



    This is also known as an “organizer hijack” and it only happens to attendees synchronizing their mailbox with iOS6 devices and who do not have a delegate.  The organizer information in Outlook and Outlook Web App is not changed in this scenario.  If actions are taken on an appointment item by using an iOS6 device, when “the organizer information is lost,” the device might incorrectly assume that the current mailbox user is the organizer.  This particular user sends meeting updates and responses as if this user was the organizer.


    Well... this also happens under iOS 5.x... the organizer hijack. 


    And it also happens with Office365 , which is Exchange 2010 managed by Microsoft.  (the only exchange we're using right now)

  • atlauren Level 1 Level 1 (0 points)



    If your sender and receiver are NOT in the same org:


    Was the receiver invited via the SMTP address that is the SAME as his windowsemailaddress?  (aka Exchange's primary SMTP address?)




  • fausttiger Level 1 Level 1 (5 points)

    Well, sorry for a long answer, but let me state the setup:


    This is an Office 365 setup, so the Exchange 2010 server is maintained by Microsoft.


    The receiver is OS X Lion mail/iCal   and/or iPhone iOS5.x ... so only Mac users have seen this (when they are not regularly using Outlook 2011).


    We don't have problems if the invite is received/replied via Outlook 2011, apparently even if the user has an iPhone.


    We have all our organization's email addresses in our Office 365 / Exchange 2010 directory, but people are mostly not syncing all their external contacts.


    So, often when I've seen this... the invite has been FORWARDED to the problem receipient..  so technically their windowsemailaddress (if that applies in this case) was not in the original invite (since someone forwarded the invite).

  • singebad Level 1 Level 1 (0 points)

    Has anyone tried Step 2 or Step 4 of the workarounds posted by BishopTJ? I'm not sure what the impact of enabling the Exchange Calendar Repair Assistant for our affected mailboxes would be, but intend to perform some testing soon. Has anyone used this?


    Also, from what I've heard, this issue has been around since iOS 5... but it appears iOS 6 has been a catalyst for more of the same issue(s).




More Like This

  • Retrieving data ...

Bookmarked By (11)


  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.