Outlook 2013 can not sync SharePoint 2010 Calendar


  • We are using SharePoint 2010 onprem and have Exchange 2010 SP2 and a mix of Office 2010 and 2013.  Many (but not all) of the Outlook 2013 clients cannot sync to calendars on SharePoint 2010.  Outlook 2010 clients do not have this issue.

    On the Outlook 2013 clients that have the issue the error received during Send / Receive is

    Task 'SharePoint' reported error (0x80040102): Outlook cannot connect to the SharePoint List (calendar name).  The server may not be reachable from your location.  Contact the SharePoint site administrator for more information. HTTP 0.'

    On the Outlook 2013 the calendar appears in the view, but is blank (no entries appear).  In Outlook 2010, the same calendar shows the events that were entered and works as it should.

    In looking at forums I though this was permissions.  One user who was having the issue had full rights (owner)to the calendar.  For this person we logged them onto a machine with Outlook 2010.  When he bought up the calendar, it appeared with all the events.  So same user in this case works correctly on Outlook 2010, but not on Outlook 2013. 

    Any assistance would be greatly appreciated.

    Thursday, November 07, 2013 12:27 AM

All replies

  • I´ve got the same issue with all kinds of lists/tasks since weeks now....
    Thursday, November 07, 2013 8:55 AM
  • We had a user with this problem as well.

    Followed the steps in this KB

    Key steps being 4 and 5. Because if the end user just removed the list and synced again, they would experience the problem again.

    Thursday, November 21, 2013 6:25 PM
  • Hi exile_ken,

    I´ve just talked to a MS Supporter:

    This behavior is definitively a bug of Outlook 2013. MS is working on a CU to fix this problem.



    • Proposed as answer by Dirk Suri Monday, December 09, 2013 10:21 AM
    Monday, December 09, 2013 10:21 AM
  • This is exactly what we needed. over 1500 computers, that have this problem, the Microsoft Rep and said we need to purchase SharePoint 2013 in order for it to work....... Then some other excuses.... we are not even close to having our 2013 environment up for now.

    Monday, March 21, 2016 11:13 AM