Previous 1 2 3 4 5 6 Next 140 Replies Latest reply: Jan 19, 2015 8:27 AM by Chris Brandt1 Go to original post
  • Pascal_Sartoretti Level 1 Level 1 (0 points)

    I replaced my iMac with a brand new Mac Mini; the problem disappeared, but came back 2 days later.

     

    It seems that 10.8.3 is nearly ready, let's cross fingers...

  • Williamvz Level 1 Level 1 (0 points)

    Another bug report has been submitted...

  • magiclantern Level 1 Level 1 (0 points)

    Just called Apple support on the issue. All they did to help was to read through the various forum posts and tell me that it must be a Microsoft problem and I should search Microsoft's web site and forums for a solution.

     

    Unfortunately, I haven't been able to find any help or mention of this problem except for here on the discussions.apple.com site.

     

    Of course, the problem doesn't exist in MS Outlook, Outlook Web Access, nor on iPhone, nor for me on previous versions of OSX (had 10.6 and didn't have the problem - only have the problem on OS X 10.8). Seems to me a bug in OSX 10.8 Calendar.

  • G. Pasarescu Level 1 Level 1 (0 points)

    That is really disappointing. Not even an acknowledgement that this *might* be an issue on their end. There are enough of us with problems (who, unfortunately, have not found solutions), that there has got to be a way we can escalate this through the ranks at Apple until someone will acknowledge there is a problem with the Calendar App in Mountain Lion and fix it.

     

    Any thoughts?

  • Randall Blank Level 1 Level 1 (35 points)

    magiclantern wrote:

     

    Just called Apple support on the issue. All they did to help was to read through the various forum posts and tell me that it must be a Microsoft problem and I should search Microsoft's web site and forums for a solution.

     

    Oh, and I'm sure Microsoft would love to help us with our Apple software when they could be selling us a copy of Outlook instead.

     

    And since Apple would be happier if we did eveything through iCloud (which I do use for my personal calendars), nobody has an incentive to fix this. Blechhh.

  • Pascal_Sartoretti Level 1 Level 1 (0 points)

    Randall Blank wrote:

     

    Oh, and I'm sure Microsoft would love to help us with our Apple software when they could be selling us a copy of Outlook instead.

     

    Microsoft would surely prefer us to use Windows + Outlook instead; but rest assured that they also make plenty of money with OS X clients, because :

     

    • Apple licenced the ActiveSync protocol from Microsoft, and certainly not for free.
    • Microsoft sells additional CALs (Client Access Licences) to companies making their Exchange Servers open to non-Microsoft clients.

     

    By the way, did anyone in this forum actually contact Microsoft or browse their forums for help ?

  • magiclantern Level 1 Level 1 (0 points)

    I searched the office.com support site, and did a bunch of Google searches. I couldn't find anything from any Microsoft centric sites that addressed or acknowledged the specific problems mentioned in this discussion thread.

     

    If someone else can find something, please share!

  • Csound1 Level 8 Level 8 (39,810 points)

    Pascal_Sartoretti wrote:

     

    Randall Blank wrote:

     

    Oh, and I'm sure Microsoft would love to help us with our Apple software when they could be selling us a copy of Outlook instead.

     

    Microsoft would surely prefer us to use Windows + Outlook instead; but rest assured that they also make plenty of money with OS X clients, because :

     

    • Apple licenced the ActiveSync protocol from Microsoft, and certainly not for free.

    I was not aware that OSX had added the ActiveSync protocol, when did this occur?

  • Randall Blank Level 1 Level 1 (35 points)

    Csound1 wrote:


    I was not aware that OSX had added the ActiveSync protocol, when did this occur?

     

    I assume he was referring to iOS. Microsoft only licenses ActiveSync for mobile use — OS X is stuck with Exchange Web Services, and from what I can tell they don't earn licensing fees from that.

     

    Ironically, Microsoft does have a support article for Current issues with Microsoft Exchange ActiveSync and third-party devices.

     

    I'm looking around in hopes that some obscure article on  EWS issues will offer a clue…

  • Csound1 Level 8 Level 8 (39,810 points)

    That's what I thought, but the OP specifically referred to OSX, so I'm checking.

  • Pascal_Sartoretti Level 1 Level 1 (0 points)

    Randall Blank wrote:

     

    I assume he was referring to iOS. Microsoft only licenses ActiveSync for mobile use — OS X is stuck with Exchange Web Services, and from what I can tell they don't earn licensing fees from that.

     

    Sorry, my mistake, I thought that OS X used ActiveSync also.

     

    Anyway, Microsoft surely finds a way to earn money on the server side for OS X clients using Exchange Web Services...

  • Randall Blank Level 1 Level 1 (35 points)

    Randall Blank wrote:

     

    Microsoft only licenses ActiveSync for mobile use

     

    Well, I have to qualify that now — it turns out that Exchange ActiveSync is used by Outlook 2013 (and the Windows 8 mail client for that matter). So even Microsoft recognizes that the desktop/moble distinction was an artificial one.

     

    (So perhaps OS X 10.9 will support ActiveSync and this problem  becomes moot. We can always hope.)

  • vicko.arocha Level 1 Level 1 (0 points)

    I found a workaround that works fine for me (the procedure in the other answers didn't worked):

     

    - go to Calendar Preferences and delete de Exchange Account.

    - close (Calendar->Quit Calendar) Calendar

    - go to Terminal and delete "rm -rf *" all the files inside username/Library/Calendars/

    - open Calendar

    - go to Calendar->Preferences->Advanced and Turn on time support (if it is already enabled, disable it, close calendar and then re-enabled it)

    - in the upper-right-corner of calendar, select your Timezone (very important to select your timezone before adding the Exchange account)

    - close (Calendar->Quit Calendar) Calendar

    - open Calendar

    - go to Calendar->Preferences->Accounts

    - add the Exchange Account

     

    Problem solved.

  • Randall Blank Level 1 Level 1 (35 points)

    vicko.arocha wrote:

     

    I found a workaround that works fine for me (the procedure in the other answers didn't worked):

     

    OK, I'm game. We'll see how long it lasts.

     

    Note that deleting the contents of ~/Library/Calendars also removes your iCloud calendars. After reactivating iCloud and Exchange in System Preferences, nothing appears to be missing…

     

    Oh, and back up your calendars first (File > Export > Calendar Archive). Just in case.

  • acyclone Level 1 Level 1 (0 points)

    As Randal implied, these "fixes" usually last only a couple days before the error returns.  I'll be interested to see if it holds up for a week.    At least Viko is still trying for a solution...

     

    I've already spent a lot of time moving my calendar entries to Gmal so I'll let others report back before spending the time to experiment.  Please check back in with updates on whether this works!

Previous 1 2 3 4 5 6 Next