“Active Sync encountered a problem on the server. Support code: 0×86000108″

This posts investigates the ActiveSync error: “Active Sync encountered a problem on the server. Support code: 0×86000108″. This post consists of what causes the ActiveSync support code: 0×86000108 error, the work around and the permanent fix.

The Cause of ActiveSync support code: 0×86000108:

From Microsoft KB this error is caused by the following: “Microsoft Office Outlook 2007 changes the alert message from the IPM.Note type to the IPM.Sharing type. Additionally, Exchange ActiveSync does not support the IPM.Sharing message type. Therefore, the Windows Mobile based-device cannot synchronize the alert message from Exchange 2003. “

Having access to one of the Smartphones not knowing about this error I initially performed the standard troubleshooting. Checked the ActivieSync settings, checked to ensure the Date and Time were set correctly, verified that the username/passwords were inputed correctly and ensured the Smartphone had the SSL certificate. All seemed alright however when performing a sync, ActiveSync initializes makes a connection with Microsoft Exchange 2003 but quickly performs the sync. At first glances it looked like it did a complete sync but the Smartphones reports the sync time didn’t change (last sync was at 8am and it was already close midday during the troubleshooting)

After reading the Microsoft KB I opened the users’ mailbox to confirm the cause mentioned. I filtered the emails in the Outlook Inbox by Received Date and went straight to the emails around the time after the last successful sync. Most of the emails were from internal users. The emails I concluded that were preventing the Smartphones fron synching and generating the support code: : 0×86000108 were email alerts generated from Sharepoint (MOSS 2007 in our case).

The work around ActiveSync support code: 0×86000108

Having established which emails were causing the problem I created a rule to dump all these email Alerts into another Folder.

Once these Alerts were out of the Inbox I performed another sync from the Smartphone and instantly updated the phone.

The permanent fix

Follow steps outlined from the Microsoft KB to request for a patch and install on your Microsoft Exchange Server 2003.

This fix applies to Smartphones running Windows Mobile5.0 and connects to Micrsoft Exchange Server 2003.

I hope you found this article relevant and useful. Please provide comments below.

Related posts:

  1. ActiveSync Error: ActiveSync was unable to reach the server. Check that the server address and proxy settings are correct. Support Code:80072f78
  2. How to unlock i-mate Smartphones for emails
  3. How to set up i-mate Smartphone to receive emails from Microsoft Exchange
  4. Smartphones versus Blackberry
  5. GPRS Access points for Telstra, Optus and Vodafone Austrlia for Smartphones

8 Comments

  • 1
    Tom Irwin
    April 21, 2008 - 9:47 pm | Permalink

    This problem also occurs with Windows Mobile 6.0, Exchange 2003, and Sharepoint Services 3.0. Alerts had been set in a Sharepoint site, and when these alerts which showed up in the Exchange inbox, they prevented ActiveSync on the WM 6.0 device from working with email messages. I removed the alert message from the inbox in Outlook, and ActiveSync started working again on the WM device. Thanks for posting the solution! I will ask the system admin. to install the hotfix.

  • 2
    April 21, 2008 - 11:27 pm | Permalink

    Tom,

    I’m glad the article helped!

  • 3
    Branin Lippincott
    October 30, 2008 - 10:48 am | Permalink

    Almost helped. Indeed, once I installed the hotfix, ActiveSync started working on my WM6 device (against Exchange 2003 and MOSS 2007). Unfortunately, when I would click on “Edit this task” in the workflow email from SharePoint in Outlook 2007, I started receiving a “The task could not be updated” error. It seems like the choices are either have ActiveSync work or have workflows work correctly.

  • 4
    November 5, 2008 - 5:16 pm | Permalink

    Woot!
    Thankyou!

  • 5
    John
    November 27, 2008 - 7:13 am | Permalink

    I too have the same issue, exchange 2003 sp2, sharepoint services 3, office 2007 sp1. This issue only occurred when we rolled out Office 2007. Amazingly, I found the KB article, went to download the hotfix, was told onscreen its no longer public, phoned microsoft, they say the hotfix has been regressed so they can’t provide it, but that it will be included in exchange service pack 3!!! Microsoft representative could not give a release date for sp3 for exchange!!!! Even the MS rep was somewhat surprised to see the hotfix had been pulled and we are left for god knows how many months before sp3. So as of yesterday, our entire organisation cannot rely on sharepoint/mobile devices for business processes!!! Microsof are no longer offering any current solution to this issue unless your organisation is a premier business customer. I thought Vista was the most ludicrous microsoft experience to date, but they sure have topped it this time

  • 6
    Judy
    October 30, 2009 - 7:57 pm | Permalink

    Thank you thank you thank you. Neither Sprint nor Motorola nor my internal help desk figure this out, but once I deleted all of the sharepoint stuff I could sync again. Yay!

  • 7
    Kadmike89
    July 23, 2010 - 1:43 pm | Permalink

    Thanks, Tom! Over 2 years later your solution still works :)

  • 8
    W.R. Greenwell
    June 1, 2011 - 9:27 am | Permalink

    I receive this error when trying to sync an HTC touch 2 pro (win 6.1) with my hotmail account (MS managed Exchange Server). Error occours when syncing contacts. Syncs fine if I only sync the cal. Only trying to sync contacts and cal. , nothing else ie. not email or task. I do not think it would be the server patch. So what gives?

    Thanks

  • Leave a Reply

    Your email address will not be published. Required fields are marked *

    *

    You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>