This is an issue that people here and elsewhere have documented. Below I've copied a couple of workarounds and tips for dealing with the issue.

In summary, the problem is with synchronizing a WM 6.1 device with two different PCs. The PCs will report the following error: "active sync encountered a problem on the desktop Support Code 86000107."

One workaround, posted at Microsoft Connect, is as follows:

There is much discussion of the WM 6.1 error 86000107 on the various PDA and smart phone forums. A sucessful (but temporary) work around is to:

* Deselect all synchronization items within ActiveSync then disconnect the device and resync with the "empty list".
* Disconnect the device and delete the partnership on the PC.
* Reconnect the device and restablish the partnership.
* Next, enable synchronization of ONE ITEM AT A TIME then synch it.
* Disconnect the device and repeat the enable & synch for each item that you wish to synchronize.

The synchonization of Tasks seems to be the source of the fault for many (including myself) so it is recommended that you DO NOT enable synchronization of tasks. These steps seem to fix the problem either permanently or for a few days (PC1 sync -> PC2 sync -> PC1 sync)

 Another workaround, provided by Adam Z Lein, is this one:

For me it was the Calendar that had the problems... namely recurring auto-generated Birthdays.  Most of them were created years and years ago.  So what I ended up doing was syncing the WM 6.1 device with both Exchange and my home PC's non-Exchange connected Outlook at the same time, while keeping my separate Tablet PC or work computer connected to Exchange via Outlook 2007.

Then I deleted all of the birthdays in the calendar and recreated them by going to the Contacts section, changing to list view with a Birthday column visible... then cut each birthday out, switch to a different contact to save, switch back and paste the birthday back in.  Then switching to another contact again recreated the birthday in the calendar.

 And finally, Laura Rooke provides these tips for troubleshooting the issue:

You might also want to run a scan of your .pst file..

"scanpst.exe" is located in:

"C:\Program Files\Common Files\System\MSMAPI\1033\SCANPST.EXE"

double click on Scanpst.exe and it will ask you to select your Outlook.pst file

 

To find Outlook.pst file...................................

from OUTLOOK , click on File, Data File Management

Then click on Personal Folders (I have 2, one is the Outlook backup file) - it should say 'Mail Delivery' in the Comments column.

Now click on Settings

On this next screen it will show you the Filename of your Outlook.pst file - use the forward arrow to see the complete file name.

 

for example, my file is called

C:\Documents and Settings\Laura\Local Settings\Application Data\Microsoft\Outlook\Microsoft\Outlook\Outlook.pst

 

hi there. I have spend countless hours over the past week researching and troubleshooting this error. I am synching two pcs with my new Palm Treo 800w (native WM v1.6).  The syncing worked for about a week then 86000107 occurs.  I am on my 3rd iteration of trial-error. I probably spent over 16 hours debugging this.

 Is this an issue Microsoft will be fixing anytime soon? This is a big waste of customers (me included) time when you canNOT sync. My 86000107 occurs mainly with Contacts (I have 2350 contacts).  It may have occurred with Calendar once, I forget.

 

Hi, Winger, and welcome to the Connection. With the help of a number of forum members in this thread, we've been able to identify this as a bug with WM 6.1. According to the development team, the bug is related to syncing when over 100 items have changed - this could be Contacts, Calendar items, etc. A fix for the issue was incorporated into the AKU 1.2 release, which was sent to OEMs toward the end of August. At this point, it's up to the manufacturers to offer the fix.

Thanks Bill for the welcome and info. I just forwarded your post to Sprint's Advanced Technical Support for Treo devices. He has a possible solution which I am going to try. It is to go to the PDA's settings...connections...USB-to-PC icon... uncheck the "Enable advanced network functionality" It would be great if some of the users can try this to see if the 86000107 error is fixed for them. At a minimum on a good day, it takes me about 24 hrs to go from my home pc to the work pc and back to the home pc to see if the issue occurs. If others can test this suggested solution faster, it would help. Here is some background info: I used AS for three years now starting w/ Windows Mobile 5.0 (HTC PPC6700 PDA phone-Sprint, and Treo 700wx-Sprint). I just migrated to Treo 800wx Windows Mobile 6.1-Sprint and started having this issue with both computers. Here is my setup Home Treo800w (WM6.1) ---- Laptop (Windows XP) ----- FileServer (Windows 2003 Server) Laptop running MS Office Professional 2007, Outlook Outlook .PST file containing data resides ONLY on FileServer Work Treo800w (WM6.1) ---- Laptop (Windows XP) ----- Exchange Server (OS unknown) Laptop running MS Office Standare 2003, Outlook Outlook .PST file containing data resides on laptop AND Exchange Server, BUT AS setup to sync ONLY with Laptop. On both computers, I am only syncing: Calendar (3 months worth of data) Contact Tasks Notes File The syncs worked for about a week (or shy of) on both computers, then showed up when syncing at home. I tried a solution found on an online forum, that is to choose only to sync Calendar, then only sync Contact, etc... then ask to sync all entities (Calendar, Contact, Tasks, Notes, File) - basically back to normal way I want to do things. This fixed the issue for syching at home. The sync at work still worked as expected the next day. However, the following night at home, I experienced same issue again sync at home...The next day, I see when syncing at work.

Winger -

The tip you mention is a good one, and it does resolve some sync issues. It's a great first step when someone runs into sync issues. However, we've had a number of people test disabling advanced network functionality in relation to this problem, and it didn't help. At the moment, Microsoft does not have any standalone remedy for the problem - the only fix is available in the AKU 1.2 software, which you can only get from your device maker. 

There is a workaround, however - since the issue occurs specifically when synchronizing data with more than 100 changed records, simply avoid trying to sync when you have more than 100 changes to your Contacts, Calendar, etc. Sorry it's less than an ideal solution, but that's the only workaround Microsoft has if AKU 1.2 is not available to you.

To remind folks,last night I cleared out my Treo800w and two computers' parnerships to the Treo800w. I then sync'd Treo800w->homepc last night. This morning I deleted all workpc's contacts, task, note and files (leaving calendar) sync'd Treo800w->workpc....

After the sync at workpc, I had to delete numerous duplicate meetings (on the PC's outlook) that resulted form the Treo 800w sync. NO contact changes were made.

 OK, I just got home and eagerly tried sync to the home PC. From AS's status, I see 201 Calendar changes (these were due to need to delete non-private duplicate meetings when I synced at work PC).  Immediately it hit the 86000107.

 I also unchecked that USb-to-PC Advanced Connections 

OK. How do I get AKU 1.2 (what is that???) on my Sprint Palm Treo 800w ???  It's only 2 weeks old : ( 

*** Sprint advanced treo tech, I hope you are seeing this.  I look fwd to receiving you callback Friday 1-2PM PST.

 

 

 

UPDATE 2008Nov6 AM  -  Based on the item that OEM's have the AKU1.2, I called Palm tech support this morning via chat. I pointed them out to a forum post (below) talking about Microsoft's input to AKI1.2:

https://forums.microsoft.com/WindowsMobile/ShowPost.aspx?PageIndex=5&SiteID=65&PageID=5&PostID=1823006

I was given a Palm Voice Channel tech support # to call. I will followup as time allows and post my findings here.

Has anyone here asked Palm about this?

Hi, Winger -

Thanks for following up on this. I got in touch with Palm's regular tech support, and they acknowledged that the 86000107 problem is a known issue with 6.1. However, they asked their engineers about any updates, and had no additional information. I'm hoping to hear more directly from their engineers if there's any more news about the issue. But in the meantime, their suggestion was to periodically check the official Palm blog - apparently it's the first place updates are announced.

I listened in to my coworker contact level 3 tech support at Palm. This is the group who contacts engineering. I won't go into the specifics of the convo, but the gist is this - MSFT AS is meant for most people who only uses sync to one computer, level 3 does not know of this issue, they need to check with Palm engineering to see if they are aware of msft patch, they have this thread and another one over at microsoft.com, they will get back to my coworker next Fri (or sooner if info comes available) for an update, even if this is a known issue and engineering has some patch from msft, no guarantee fix will be implemented or if will be included in a release, no guarantees when. Bottom line, I am trying to fix this myself my doing alot of extra data manipulation and more trial-error next week. To say the least, this issue and run-around most folks have received on this issue is a b!itch, to say the least. Support (or lack of) has been unacceptable. Worst however, is how the heck did this pass MSFT testing? How does my wife's Palm Desktop work flawlessly across 2 computers and MSFT has seemingly downgraded AS's sync capabilities to only one computer? Sell Microsoft stock - that company canNOT get their act together. Big dreams but cannot implement the small details.

Winger, your persistence on this issue is very much appreciated. I as well as several others are following up independently with carriers and manufacturers, too. This is a really troublesome issue for many - you're not alone in your frustration. However, I'm hopeful that given the interest here and elsewhere in fixing this, we'll see more information soon. Thanks again.

My coworker, who is also experiencing this issue, got back to me today. Apparently has some news to report from Palm Technical Support. Tech Support has confirmed Palm Engineering is aware of this issue. The update will unfortunately require a ROM updated and this is likely the 'hitch' here. ROM updates require a fair amount of analysis and testing time to ensure carriers' devices are NOT impacted. If (and my coworker did not confirm one way or another) this issue is truely a WM 6.1-specific issue (versus device-specific), then this issue affects devices across all the major US carriers (VZ, TM, AT, and Sprint) and of course requires more careful analysis and testing before the ROM can be released (in any form). Palm Tech Support could NOT (this is the bad news) confirm that Engineering will be releasing this fix. Thus, no dates can even be anticipated at this point. Sorry for the bad news.

I'm seriously considering rolling my HTC Mogul back to WM 6 until this is fixed or until I retire, whichever comes first.

And forget about buying a new device with WM 6.1 before then.

Winger, thanks again for pursuing this issue. You and Kathleen and everyone else who have looked at this issue here have helped tremendously with understanding the situation. it's disappointing that we dont have a solution yet, but i feel confident that we'll be among the first to know.

Hello all, add another to the list. I have not seen anybody mentioning this phone... I bought the new Samsung Epix pre-loaded with 6.1, and after the 1st sync between my laptop and my workstation, I got the dreaded error. On the upside, at least it's not my new phone!

I hope Microsoft responds to this issue faster than they are known for. It really sucks to buy into the "upgrade" only to end up with less functionality than you had previously. Hmmm, that kinda sounds familiar, doesn't it??

Welcome to The Connection, JoeDrummer.

Hi, add me to the list of dissatisfied users.  I've tried the workaround where I'm supposed to uncheck and recheck the items.  The problem with that is that it clears the saved information from the PDA when I do that, so in effect, I am not really syncing between the two PCs, just with the last PC I connect to.  Any more thoughts?  Anyone?