Sync Problems with WM 6.1 & ActiveSync 4.5

[chicagotech]

I am unable to synchronise with new mobile device with two PCs; home and office [both Windows XP]. Both have ActiveSyn 4.5. The device I bought recently is HTC Touch Diamond and runs OS Windows Mobile 6.1.



I was able to sync between both PCs previously with my old devices of WM 5.0 and WM 6.0 but the new device which has WM 6.1 gives me the following error message and only allows me to sync with one of the PCs.




===================

ActiveSync encountered a problem on the desktop.

Support Code: 8600107

===================



It fails to sync Outlook components: Calendar, Address, Notes, etc.



Refer to the following forum link for other users with the same problem, all running WM 6.1, on various mobile devices:



http://forums.microsoft.com/windowsmobi ... &SiteID=65

[chicagotech]

There are at least 2 causes for this. One that we are tracking now has to do with one partnership being created on a 64bit OS. Then a partnership is created with another computer - doesn't matter if it's 32bit or 64bit. After creating the 2nd partnership, you see an error (86000107) when you try to sync with the 1st computer - does this sound familiar to anyone?

What we know about this particular issue is not much yet other than it appears to be an issue with the desktop sync code.

There is another sync with multiple desktop issue that involves the changing of more than 100 PIM items (contacts, calendar, etc). This was fixed in a latter build - check to make sure you've got the most recent ROM update from your Mobile Operator and OEM. If you have the fix then I believe that the last digits of your ROM build # would be 1.2.6 or greater (found under settings within About).

One note - Maintenance Releases (MRs) aren't always available. The Mobile Operator and the OEM work together to decide if they are going to make one available for a particular device or not. It's very possible in some cases that MS has resolved an issue and delivered that in an update, but that doesn't mean that the update is available to the users. Of course, it could also be that we, or the OEM, haven't addressed the issue.