Resources for IT Professionals >
Forums Home
>
Windows Phone Forums
>
Activesync / Windows Mobile Device Center
>
Error 0x86000107
Error 0x86000107
- I end up getting this error on my WIndows Mobile 6.1 Pro Activesync after I establish a second sync partnership on my HTC Touch Pro with my Vista 32bit laptop and then try and re-sync through my first partnership with my desktop Vista 64bit PC.
I have worked around the problem by deleting both partnerships and starting again with just one, but I would like to use a second partnership and Activesync purports to support this.
Community forum posts suggests a lot of different smart phone users encounter this error. An MVP claimed at the following link that Microsoft had identified the cause of the problem and sent the OEMs the information necessary to write a fix for the problem. I have contacted HTC and they deny receiving any such information.
It seems clear that there is a bug in the operating system software. Have Microsoft fixed it, and if not, when are they going to?
All Replies
- Hi Shaun,
In fact after seeing this issue on a variety of threads in these forums I contacted my contact at Mivcrosoft and asked if it was a know issue and was there a fix in the works. My contact did some research and did come back to me letting me know the same thing that was referenced in the link you gave.
In fact, I was told that they have come up with a fix for the issue and have have delivered the fix to the OEMs. It is the device vendor that provides updates to their customers.
I will again forward this thread to verify that the info that I got was in fact correct. I'll need a few days but I expect I should have an answer to verify one way or the other.
Jack
http://www.experiencemobility.net - Just as an FYI, here is the text of the email I received regarding this issue Shaun:
This is a known issue and was fixed in AKU 1.2. The customer would need to contact the OEM to see if they are providing the fix.
Action:
Customer upgrades to Windows Mobile 6.1
Customer normally sync's with two PC's and when trying to sync with the second PC sync fails.
Results:
Error code 86000107
Sync fails
Cause:
The issue is talking about deleting more than 100 contacts. However, it’s not specific to the delete operation. As long as there are more than 100 changes in one data type to be synced to the desktop, you can hit this issue.
Resolution:
The fix is available to the OEM's (device manufactures) and the customer will need to contact them to see if they have an update available.
http://www.experiencemobility.net - Thanks for your reply Jack.
Unfortunately I am receiving conflicting information from Microsoft.
I too had read about AKU 1.2 on user forums. I confronted my OEM about this and they specifically denied having received AKU 1.2.
I contacted Microsoft (Australia) by telephone to confirm the information. Initially they confirmed verbally that AKU 1.2 had been forwarded to OEMs in late November 2008. I requested they confirm that information in writing because my OEM, HTC, disputed it. After an hour of being passed back and forth between their "information" and "support" departments, I was finally told that they could NOT confirm that AKU 1.2 had been forwarded to HTC, although other OEMs had certainly received it.
So it seems to me that the likely situation is that Microsoft have NOT forwarded a fix for this problem to HTC, manufacturer of one of the leading Win Mobile Pro smartphones on the market. And so my question remains unanswered (and was not answered by Microsoft Australia): when are they going to?
And by the way, I cannot seem to find ANY email address via which I can take this issue up directly with Microsoft. Instead I have to contend with call centre operators. Can you suggest an address?
- No I can't suggest an email address that would be a good lead for you but I have again sent a note to my contact at Microsoft asking if they can get someone to reply to this thread to put it to rest (so to speak). I am confident thatthere was a fix and I am confident that it has been provided to the OEMs. They just may be choosing to "play dumb". Hopefully we will get another reply.
http://www.experiencemobility.net - Shaun - Can you share your OEM ROM version from your device?
(Start > Settings > System > Device Information) - Shaun, your OEM ROM version info is important if you can pass it on.
Jack
http://www.experiencemobility.net - Hi Mary and Jack,
ROM version: 1.90.861.8 WWE
Radio version: 1.08.25.20
Protocol version: 52.44.25.24U
It is the most recent ROM upgrade available for the device in my area (Australia).
A more recent ROM upgrade is available for overseas models, and for the Touch Diamond, however, the notes that accompany those upgrades do not list this issue amongst the fixes.
Presumably this is because HTC insist they have never received a fix from Microsoft.
Thanks. I away your reply.
- Thanks. We'll reply soon with further information.
- Thanks Shaun
Mary Alice is forwarding that information to the appropriate source. Hopefully we will have a good result come back. Hang in there a bit ...
http://www.experiencemobility.net - Hi,
There is no option to install AKUs separately from an updated rom from the OEM. Unfortunately, you will need to wait and see if the OEM offers a rom update for your device. The OEM decideds when to create a new rom based on the feedback from customers so make sure they have your request documented.
Chris De Herrera, http://www.pocketpcfaq.com, http://www.pocketpctalk.com - Hi Chris
Thanks for your reply but if you read the thread carefully you will see that that information does not address my problem.
The problem is that I have so far been unable to establish whether my OEM is in a position to issue a ROM upgrade that fixes the error, because I have been unable to confirm that Microsoft has actually supplied the AKU to my OEM. - Hey Shaun,
There is a lot of confusion around this and what is supported and what is not. So what I'd like to do is this.. I'm going to post some info on what is supported in terms of sync'ing with 2 PCs and what is not. Can you please take a look a the table and confirm that what you are attempting to do is supported? Your feedback will help me track down whether this is a bug and whether or not it has been fixed?
Secondly, HTC has received all of the AKUs, but their Mobile Operator partner may have not requested the update - take a look at the table and let me know what case you fall into - or how what you are seeing is different. It could also be that what you're seeing is different then what was addressed in the AKU.
I will examine the bug report to see where the breakdown in information is. Sound like a plan to you? What looks to be happening, is your partnership is becomming corrupt. This error code is not from the device side, but it's coming back from the desktop. I believe that the person that you are working with in Australia has also escalated this issue. I'll post the table that I spoke of before, and how to capture desktop airsync logs.
- Here is the table that I mentioned - although you still should not be seeing the error code that you are seeing, and that error is coming back from the desktop.
Cases where we won't sync with 2 PCs for one info source.
Config 1: Device <->Exchange
In this case the user sets up the source to be an exchange server using the servers account credentials. The device can connect to the server ‘over the Air’ using either cellular or a wireless Access point, or it can connect using desktop pass through which uses the PCs Ethernet connection while the device is cradled. In the Device to Exchange configuration the device is communicating directly with an Exchange server.
Config 2: Device <->Outlook<->Exchange
In this case the user is syncing to Outlook on a PC that is backed by an exchange server. The user does not have to configure the Exchange settings since Outlook is already configured. Syncing in this configuration is limited to when your device is tethered to the PC.
Config 3: Device <-> Outlook (stand along or backed by Pop/IMAP)
In this case the device sync to Outlook which has its data in a PST that the user has either entered by hand or has downloaded from hotmail or another online mail service. This sync only works when the device is tethered to the PC.
This chart shows which combinations work and which are blocked. Column one was added for completeness.
No Second Config
Config 1
Config 2
Config 3
Config 1
Works
Blocked
Blocked
Works
Config 2
Works
Blocked
Blocked
Works
Config 3
Works
Works
Works
Works
- Hi 2GrokMobile
Firstly thankyou for your replies. It is great to have finally broken through the many layers of obstruction that Microsoft place in the way of a person who needs to speak to them directly about an issue. Thanks Mary and Jack for helping me to do that.
Regarding your table, I am not completely sure I understand it, but I think my situation falls into config 3. I am not using Microsoft Exchange. What I am basically trying to achieve is to keep my Outlook contacts, tasks and schedule syncronised on my desktop, smartphone and laptop. Activesync does not appear to support a desktop <-> laptop partnership so I am using my smartphone as a "go between" and I want to keep the smartphone sync'd as well.
I tried to achieve my goal by publishing my calendar using the service Microsoft provide (forget what it is called). But this didn't really do what I wanted.
The sequence of what I did to produce the error is described in my initial post, sufficiently clearly, I hope.
If I understand your table correctly what I am trying to do is supposed to be supported. Indeed, Activesync on my smartphone has no problem with establishing the second partnership (smartphone <-> laptop) and describing the laptop as "PC2". Where I have the option of specifying which device prevails in the event of a conflict, I set it to desktop, in the case of the first partnership, and smartphone, in the case of the second partnership. So it looks like it should work, and it does sync using both partnerships initially, until I go back and re-sync with the desktop. Then I get the error.
I think that is all the information I can provide about what went wrong and how it happened. Let me know if you require any furthe information.
Finally, regarding your statement "HTC has received all of the AKUs", are you able to provide more detail? On what date was AKU 1.2 supplied to HTC? By whom at Microsoft and to whom at HTC? And can you expressly confirm you speak on behalf of Microsoft? Unless I am able to confront HTC with those particulars then I will end up again in a "yes they did" vs "no they didn't" conversation with HTC. There will be no prospect of AKU 1.2 being incorporated into a ROM upgrade whilst that kind of conversation continues.
Kind regards
Shaun Ginsbourg - Sounds like you're right Shaun. Let's enable desktop logging to find out why your partnership has become corrupt. If you're still working with Microsoft Australia then they will tell you how to do this. If not, please go to http://pocketpcfaq.com/faqs/wmdc/debug/ and follow the insturctions for enabling logging via WMDC.
- And sorry for persisting with this, but are you able to give me the information I requested about the delivery of AKU 1.2 to HTC? Here is the correspondence I have had with HTC about the matter:
"
Dear Shaun,
Thank you for contacting HTC Service Support.
We still haven't received any updates from Microsoft regarding AKU 1.2.
Once we have the fix from them it will be surely incorporated to our
roms.
Unfortunately, we don't have a time frame on when it will be released.
We suggest you visit the website from time to time for updates on this
matter.
Thank you for your continuous support of our products and services.
Should you require further assistance, please do not hesitate to contact
us again.
Best Regards,
Sofie
Customer Service Executive
HTC Corporation
Customer Service Hotline (Australia): +1300-482-482
Website: www.asia.htc.com
-----Original Message-----
From: Shaun Ginsbourg [mailto:sginsbourg]
Sent: Wednesday, January 28, 2009 9:30 AM
To: anz_service
Subject: RE: HTC SUPPORT
Dear Morgan
Thank you for your email.
I have since found a statement from Micrsoft that they sent a fix to
OEMs which is known as "AKU 1.2" that deals with this issue.
Could you please advise whether:
1. HTC has received AKU 1.2 from Microsoft2. Whether it has been incorporated into any ROM upgrade3. If not: (a) why not; and (b) when will this occur?I look forward to your reply.
Shaun Ginsbourg
From: anz_service@htc.com [mailto:anz_service@htc.com]
Sent: Wednesday, 21 January 2009 4:59 PM
To: sginsbourg
Subject: HTC SUPPORT
Dear Shaun,
Here is your e-mail as promised.
Regarding your inquiry for synchronization error 0x86000107, I have
verified this with our technical department and they have confirmed that
there is no known fix yet for this error. Microsoft has not notified us
that they have a devised a fix for this issue.
Thank you for your continuous support of our products and services.
Should you require further assistance, please do not hesitate to contact
us again.
Best Regards,
Morgan
Customer Service Executive
HTC Corporation
Customer Service Hotline (Australia): +1300-482-482
Website: www.asia.htc.com
________________________________
From: Shaun Ginsbourg [mailto:sginsbourg@]
Sent: Friday, January 09, 2009 2:20 PM
To: anz_service
Subject: Telephone case reference 1091399 - Error code 0x86000107 in
ActiveSync
Recently I rang HTC about the above error code I was receiving when
attempting to sync my Touch Pro handset with a Windows Vista 6bit PC
I have successfully sync the machines in the past, however this error
message appears from time to time. I am usually able to get rid of itby deleting and re-establishing my partnerships, but this is time
consuming and usually results in loss of data. Often it leaves mewithout my contacts on my mobile for a period of time, which is
unacceptable.
Recently the error re-appeared when I attempted to establish a second
partnership between my Touch Pro and laptop - a function which
activesync is supposed to support.
I found the following link:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=mi
crosoft.public.pocketpc.activesync&tid=519e43d9-9524-43ed-b8a0-15b5ab4ad
c5e&cat=&lang=&cr=&sloc=&p=1
I note that Kathleen Anderson, a Microsoft MVP, claimed on 21/11/08
that: "Microsoft has determined what the problem is, and they
have delivered the fix to the OEMs (the companies that make the phones).
It
is now up to the OEMs to provide an update to their customers that will
fix
the problem."
Your operator suggested that HTC were aware of the issue and were
waiting for Microsoft to address the issue.
Obviously your operator and Kathleen Anderson cannot both be right. Sowho is wrong?
Your faithfully,
Shaun Ginsbourg
- Actually, I don't seem to have any log files to send you. I have looked in .../Windows/Temp/ and they are not there, even though, if I understand the instructions at http://pocketpcfaq.com/faqs/wmdc/debug/ correctly, that is where they should be.
I am generally ignorant about these things but I just read somewhere that Vista does not use text log files any more and I need to use the Event Viewer program instead. Could that be the reason the instructions at the link you referred me to does not seem to work?
- You should definitely have the log files. Two things to check - 1) did you reboot your computer, reconnect your device, and then attempt to sync? Lastly, the files should be in your %TEMP% directory - are you looking there for WMDC.LOG and WMDHOST.LOG?
While we continue to investigate the issue that Shaun is encountering, I just want to make sure that everyone understands officially, that HTC has received the AKU. However, it is up to HTC and the Mobile Operator to determine if a Maintenance Release makes business sense to them. Newer devices should have the fix contained in the AKU.
Thank you
Hi 2GrokMobile
Debug Log
I have double checked the instructions and still have no log files.
I have saved the two config files to .../Windows/WindowsMobile/, rebooted my PC, connected my device and sync'd it, and then checked .../Windows/Temp/. There are no .log files in that directory or anywhere else on my hard drive. I am happy to send you screen captures showing you this if you like.
Are you sure that this works on a 64bit Vista PC? Is there some other way of creating the debug logs?
AKU sent to HTC?
I notice that you have not responded for my request for more details about the transmission of the AKU to HTC. Are you not able to provide that information? Since posting you last time I came across this link -http://www.windowsmobiletraining.com/Connection/forums/p/1718/8826.aspx
- which seems to indicate that HTC might be a special case as far as this issue is concerned.
Today I spoke to a senior technician at HTC who told me he had spoken to a senior contact at Microsoft Australia. That person (from Microsoft) had verbally reported that as far as he was aware Microsoft had not delivered the AKU to HTC yet, but he was double checking that information.
Please don't think me disrespectful or unappreciative of your assistance: I am just trying to get to the bottom of this issue and I am receiving a lot of conflicting information!
Regards
Shaun Ginsbourg- Hi again 2GrokMobile
I am embarrassed to say that I have now managed to find the log files in a hidden folder AppData\Local\Temp\, and I have reproduced the error. The file contents are too long to post. How can I get them to you? Could you send me a contact email at shaunginsbourg@hotmail.com?
- Hi Shaun,
Other than the official statement, and my unofficial statement, I won't provide more details of the AKU transmission, but I have spoken with more than one source familiar with how AKUs get distributed, and sources that work with HTC that have stated that they have received this AKU. No disrespect taken.
Now, of course just because they received the AKU, that doesn't mean that they would automatically create a Maintenance Release, or ROM update for your device or Mobile Operator.
I'd like to avoid getting hung up on the AKU issue for now, and focus on resolving your problem. Shaun, for this issue, can you send your log files to GrokMobile@Live.com so we can take a look?
Thanks - Shaun,
Thanks for sending the logs. Someone is taking a look at them now. I hope to have an answer for you soon. - Thanks for chiming in on this 2GrokMobile. It has been a long standing issue that has affested a variety of folks. Hopefully you guys can dicipher something from Sean's logs.
http://www.experiencemobility.net - You bet! Hey Shaun,
Can you tell me what the build # is on your device? You should find it in parenthesis under Start, About.
There was a problem with deleting, or making 100 or more changes to one data type that needed to be sync'd to the desktop. Do you fall into this category when you hit this error? This is the issue that was fixed in AKU 1.2.6 - your build # should tell us if you are running that or something earlier.
We're still looking into this, but can you try to run ScanPST on your computers. This has worked in one case. And we will continue to investigate. - Shaun, any thing new on this?
http://experiencemobility.net http://mobilitysite.com - Sorry for delay in replying ... if someone can tell me how to get message alerts sent to my regular email rather than to my hotmail address that would help!
GrokMobile, I have CE OS 5.2.19965 (Build 19965.1.2.3). - I share your email alert request Shaun! I too have to check personal email (hotmail) in addition to my regular business email (Exchange/Outlook) to see the alerts. I'll submit this as a forums infrastructure change request and will let you know if the infrastructure team is able to address this. Regarding your build information, thanks for sharing and that should be helpful for GrokMobile...
- Shaun - I just got an answer to the email alert request capability request. Please try this:
to route alerts to a non-Hotmail account you should associate your existing email address to use liveID (link provided below), validate your email address, and subscribe to alerts.
- As an observer in the same position, I appreciate your detailed effort and dedication toward solving this issue. Shaun, that you for everything.
Please know you are not alone, and I look forward to seeing some options for resolving this issue posted. I'm like you, hoping that someone, somewhere, will come up with a patch. I really want to love my HTC phone -- but right now I hate it and everything involved with it! I'd downgrade back to my old phone if my mom hadn't laid claim to it! - Thanks MaryAlice, let's just hope Grok can come through for us all. Another person I was dealing with at Microsoft Australia about this problem seems to have gone AWOL ...
- I'll ping Grok again too to see how his work is progressing...
- For what it's worth, I too have been seeking an answer to allow me to sync my Motorola Q9h with my work computer and home computer. I'm getting the same error codes and have tried most of the remedies mentioned here and on several other sites. I'm close to giving up on a Windows device because of the lack of support. It used to be a good product that synced every time with minimal effort...now it appears to be garbage that does not perform its basic function. Kinda like a fancy car without a motor!
- Well thanks to Shaun and you all, I have some light to shed on this SNAFU. All was well Sync wise [Contacts, Calendar, Tasks, Notes, Favorites] until both my Office computer and Home computer were upgraded to Vista 64, clean installs.
For 2 weeks I've been successfully syncing at the office and getting "problem on the desktop error 0x86000107" at home. Last night, for the 3rd. time, I deleted the partnership at home, recreated the partnership and synced successfully. However, this morning at work, "problem on the desktop error 0x86000107". I am confident that when I delete the work partnership, work will sync, but home will fail.
My Samsung i-760 was upgraded to Mobile 6.1 at Samusng's behest some time ago with the understanding that I couldn't go back to ActiveSync etc.
At this point if I knew of a third party program that worked, I'd buy it. I can't imagine Samsung accepting the burden of fixing this Microsoft SNAFU.
MOXIEKAUFNOSKI - Thanks for the build # Shaun. They believe that there was an issue that was fixed in AKU 1.2.6. I'm seeking more detail on what that issue was so we can make sure that's the issue that you are hitting and that it's not something else.
The additional feedback from Moxie was also helpful - thank you Moxie! - Thanks to all of you also. I was beating up on my IT guy at work, but to find out that it's a Windows Mobile 6.1 issue helps to know it's not my IT guy. I recently updated my Verizon xv6900 (HTC Touch) phone and like all of you I can't sync my home and work computers on my phone.
I know I was able to sync both computers when I had the 6.0 version on my phone. Could we all install 6.0 on our phones? However, the downside would be that the phone companies may void their warranty since the OS is changed. Anyone know?
Glad my input was usefull. Would it be helpful to know that I have 3 Bluetooth devices paired with my Samsung i-760 SmartPhone. One is a dongle that syncs with the work computer. The other two are for my Plantronics headset and my in car Bluetooth hands free. To use my headset I must REFRESH it and allow it to show in first position. If I do nothing after that the Bluetooth in the car announces "Phone is Off, Phone is Off" until I refesh its pairing and it comes into first place.
Any chance this behavior is related to the Mobile 6.1/ActiveSynch behavior of not being able to work with two different partnerships?
Thanks in advance for your help.
MOXIEKAUFNOSKI- Shaun - also let us know if you had a chance to route alerts to your non-Hotmail account by associating your existing email address to use liveID (link provided below), validate your email address, and subscribe to alerts.
- Mary Alice, I have followed those steps which ended up requiring me to set up a new account and link the email for that account with this one. I validated the email and subscribed to alerts for this thread but I don't seem to be getting any.
Grok, I am assuming you understand that I already know about AKU 1.2.6 and that my hope in submitting the error logs to you has been that you will be able come up with a fix to the problem despite Microsoft and HTC's conflicting claims about whether the former has delivered AKU 1.2.6 to the latter. - Hey Shaun,
I wanted to update you on what's happening with your issue. There was an issue with deleting, or changing, 100 items. This particular issue was fixed in an AKU, but based on the logs that you were able to supply, you aren't running into this issue.
There was another issue that was fixed in AKU 1.2.6 - I'm attempting to gather details on what that issue was to see if that is the issue you are running into. Based on your build #, you are not running that build on your device.
The current thought is that you are running into a bug at the partnership level that prevents the desktop from partnering with the device from partnering with the 1st computer after partnering with the 2nd. This also squares with what Moxi posted earlier. - Grok - You have the problem identified perfectly.
If it helps, my Samsung i-760 shows: CE OS 5.2.19202 (Build 19202.1.0.0).
Finally, as I expected, connecting at work after successfully connecting at home also resulted in "error 0x86000107". Deleting and restoring the work partnership made the problem go away. Alas, the problem now exists at home.
Thanks for your support.
MOXIEKAUFNOSKI - A follow-up...HTC believes that the issue Shaun is experiencing is related to the 100 deletion/changes bug. Based on the logs Shaun submitted, I and others don't. I couldn't find any issues that mentioned problems with a 64bit OS, 2 desktops and WMDC - I suspect that this is a new issue, so we're going to treat it as such.
Thanks for your patience around this - I know it's been tough! - Thanks for the confirmation MoxieKaufnoski!
- Shaun, I just wanted to pass on this little tidbit about the dreaded 86000107 error.
Up until today, I had never experienced it but for what ever reason it started to appear on my HTC Touch PRo. I sync with two PCs and I kept getting an error. I tried a myrid of solutions but I kept getting it. I hard reset my device three times and deleted the partnerships on the PCs and it still appeared.
Finally I decided to sync it with my desktop and this time with a different laptop. Perfect sync! I'm wondering what caused the good sync. I was syncing a Vista Business laptop with a Vista Home Premium. Now I'm syncing with a Vasta Home laptop.
Just thought I would share that ... clearly you are not the only one and now I can say I have experienced it (sadly).
http://experiencemobility.net http://mobilitysite.com - Ah, so that's what Microsoft call a "premium experience", it is Jack? The plot thickens! lol
Thanks to everyone who is weighing on this ...
And Mary Alice I am now getting alerts, thanks to your tip ...
We're all counting on you, Grok! - I had to laugh Shaun! I never experienced errors before I became active here in the forums. Interesting that we are both using Touch Pros and got the error. I wonder if there is a relationship there?
http://experiencemobility.net http://mobilitysite.com - Jack - Are both your Vista Synchs V64 or is one or both V32? In my case I've got V64 in both places.
MOXIEKAUFNOSKI - All mine are 32 bit machines. I'll start getting 64 bit machines in the fall when we start seeing Windows 7 (unless I can convince my wife I need to spend money now and in 6 months as well .... naw, that won't happen. lol
http://experiencemobility.net http://mobilitysite.com - I feel Shaun's pain however I have an existance proof.
The HTC Touch Pro ships with AKU 1.2.3, ergo HTC has received AKU 1.2.3.
Unfortuantely there is conflicting information out there about which update contains the fix in question. Some think it is 1.2.3 and some that it is 1.6.2.
There also appear to be two separate bugs. One associated with more than 100 sync items when a device has two partenrships (the fix everyone is discussing) and another one which seems to be independent of the number of items.
Having spent almost three decades working for hardware and software vendors, I can tell you with a high degree of certainty that asking support folks in subsidiaries whether party A product group has provided party B product group with an item covered by a contract between the two parties is not likely to yield a believable answer. Particularly when party A is Microsoft. The support folks simply are not in a position to know and they can ask all they like but they will be ignored (at best) or told to go away.
The answers from HTC may nor may not be correct - they don't say they havent' received 1.2.3, they say they haven't received an update regarding 1.2 which could mean anything. They also say there isn't a fix from Microsoft, which could also be true if they are talking about the second problem (independent of the number of items) rather than the first. Human communication is such a flawed thing. If it is precise it is unintelligible.
-mark - we examined the logs Shaun was able to provide. This issue appears to be connected with the desktop sync code as oppose to the WMDC portion. Unfortunately we haven't been able to narrow it down further than that. I've asked another group to create a local repro, and I'm waiting on their decision to accept the issue. Not very helpful, but I wanted to update you - progress is being made - slow progress. I will keep you updated as more info becomes available.
- Thanks for the update, Grok
- Thanks for that update 2GrokMobile
http://experiencemobility.net http://mobilitysite.com - Hi All
Just letting you know that our MS contacts assure me that as we speak, their boffins are assidously toiling away to banish the xxx107 error from HTC handsets forever. Success is not guaranteed. They will post an update soon.
We shall prevail! - assidu ously, I should have said ...
anyhow, they reckon they're doin' their darnedest! - Bet ya dollars to donuts that they fix it in Mobile 6.3. Some of our people are due back tomorrow from a MSDN Conference on 6.3 etc. I asked them to keep their ear to the ground.
MOXIEKAUFNOSKI - I for one hope that the fix doesn't leave me hanging out for HTC to do another ROM upgrade!
- You are not the only one Shaun!
http://experiencemobility.net http://mobilitysite.com - 2GrokMobile and I just communicated again about this thread and this issue, but I don't yet have any further updates. I know he's been working hard, toiling away and will let us know as soon as he has anything to report.
- Used to have an HTC Touch with this problem. Now have a Samsung Omnia with the same problem. I'm at 20276.1.3.3. This problem is beyond the HTC circle.
- I'm sorry to hear you're experiencing this issue CV27 but appreciate your sharing this additional piece of information. It's helpful to understand the full range of devices impacted.
Thank you from the Microsoft Windows Mobile Team
http://www.WindowsMobile.com/TotalAccess - CV27, as this thread is now approaching its six month anniversary, let's hope that news of your misfortune can inspire Microsoft to move more quickly towards a solution than the glacial pace they have set so far
we examined the logs Shaun was able to provide. This issue appears to be connected with the desktop sync code as oppose to the WMDC portion. Unfortunately we haven't been able to narrow it down further than that. I've asked another group to create a local repro, and I'm waiting on their decision to accept the issue. Not very helpful, but I wanted to update you - progress is being made - slow progress. I will keep you updated as more info becomes available.
2GrokMobile,
I, as well as all the 0x86000107 prisonners, appreciate whatever effort is being made.
I've had a novice look at the log files generated and find nothing obvious. The wmdc.log has very few entries. I did find 2 unusual entries in the wmdhost.log:
1- A reference to an old device id I don't have anymore, where it is "Adding new tombstone"
2- "StoreType = ExchangeServer" is being declared for one of my partnerships (the one at work versus the one at home). Although my office runs Exchange, I am syncing from a local PST (on my laptop at work).
I'll gladly submit my logs if useful.
Given that, in my case at least, this problem is repeatable, one would think this is a great opportunity for debugging. The 'local repro' you have proposed internally is great, but how long will it take to set up, if accepted, and what are the chances that it matches all the conditions we users have? What about using remote control of my desktop and have all the fun you want ?- Thanks CV27 - this has been a painful process. The issue has been prioritized for investigation, by the team that is responsible for working with Mobile Operators (MOs) and OEMs to get Windows Mobile to work on a particular MOs network. This process is called commercialization, and is done through AKUs or Adaptation Kit Updates. The bottleneck, or resource contention is that this same team is working on the 1st commercialization pass. I've asked for a timeline, and I will share it with you when I get one. Hang in there 86000107 prisioners, and thanks for your assistance in trying to tackle this nasty bugger.
I don't know if we will get new bits, but I'm hoping that based on the identified cause we will be able to provide information that will help you avoid this problem.
CV27, I may take you up on your offer regarding the logs - can you send them to GrokMobile@live.com when you get them. Having multiple logs may help narrow down the cause of this issue.
Thank you! - I'm hanging in there, Grok, but my fingers are slipping ... any news?
- Sign up another victim. This is worse than irritating, it is costing me a lot of time. I realize now I should have gone RIM or iPhone. This is supposed to be a serious OS for professionals with PDA's...
My config: Samsung Omnia; ROM=S:i910.10 V.BJ28.2027; WinMo build = 20276.1.3.3. At work, I'm sync'ing via USB to an XP laptop running ActiveSync 4.5. It is connected to an Exchange server (ie: config 2 above). At home, USB to Vista Pro 32bit under a user acct.
I've been running WM 2003 forever and syncing on both ends with only the normal ActiveSync problems (ie: it usually ran fine, but every once in a while it forgot it knew one machine or the other). As soon as I "upgrade" to the new Omnia running WM 6.1, I started having the "problem with the desktop" (now THERES a helpful message) aka Error 0x86000107 problem. This was always on my home (Vista) box.
I discovered on my own the "uncheck everything and recheck 1x1" which is not a fix by any means.
After spending endless hours lurking in a dozen forums, I came to the conclusion it is WM6.1 and I've tried about everything (I think):
1. Ran ScanPST on both boxes. No dice
2. Deleted all Contacts, Tasks, Notes, and Calendar (3 Months) on Vista box, re-synced. Nope.
3. Deleted all partnerships on both machines and re-create. Nope.
4. Deleted all partnerships on both machines, re-synced at work, created a NEW OUTLOOK PST file on the Vista box, re-synced. This WORKED... for about a week. Now it is back.
I'm willing to send log files if it will help, because I need this problem fixed. I feel like I bought a pig in a poke and the joke is on me.
Any news? Any help? Any idea when or how this will be solved? - I believe Microsoft won't fix this bug until Mobile 6.next is out. This bad behavior makes Microsoft look a lot like General Motors who didn't get it either.
In the meantime, I have partial relief. I too connect to a Web enabled Exchange Server. Thus, I gave up sinking with the Vista64 Work desktop and the Vista64 home desktop and use my unlimited broadband connection to synch with Exchange via the Web. Our system won't sync Notes so I just hide my notes inside Tasks using the memo field.
MOXIEKAUFNOSKI - Hmmm. Nice trick, but I don't get it: the main problem is that you can't sync with 2 machines. If you are willing to give up syncing with your home desktop, you should be able to do a full sync (including Notes) with your work desktop, si?
- Alas, synching one desktop is insufficient and often doesn't work. Going to Exchange at least keeps my desktop and smartphone on the same page. When I'm home and need to set an appointment or such, I sign-on to Exchange. Told you it was partial relief, but it is reliable.
MOXIEKAUFNOSKI - Exchange is all very well if you are part of an organisation that is big enough to justify the cost. It is not a solution for individuals and small businesses who just want to share a calendar with two or three machines.
The real solution to this problem would be to replace the lame, published calendar concept on Outlook (which does not seem to permit full access by multiple machines using it as a primary calendar) with an online calendar facility. Outlook Connector / Windows Live is moving in this direction but presently the online calendar format is, as far as I can see, less rich than the Outlook format and cannot be synced. Moreover, Mobile Outlook needs to have the same ability to sinc with the online calendar for this to work. If this is put in place syncing can be a seamless, automatic, background process that relieves us of having to muck around with usb cables and the unreliabilities of bluetooth and Activesync / SyncCentre / Mobile Device Centre.
But given I have waited two years, without success, for Microsoft to hear my and many others' request for left-handed scroll bars on Windows Mobile, and six months, without success, for this problem to be solved, I have little faith in Microsoft to deliver software that actually meets people's needs. - I wanted to update you with the progress on the cause of 86000107 error. The issue is in a pipeline for an engineering team to take a look at. Unfortunately, in front of this particular issue, are issues that Mobile Operators and OEMs have asked the team to look at so that the MO & OEMs can get their early 6.5 devices through Technial Acceptance.
Thanks HeiDO for the additional information, I've added that to the issue. I may indeed take you up on receiving logs from you. The more info regarding this, the better. Would you still be able to send them - from both machines?
As painful as this wait has been, I wanted to make sure you knew what was going on, and that we haven't forgotten about this issue. - Thanks for that update 2GrokMobile
Jack Cook
http://www.experiencemobility.net
http://www.mobilitysite.com - I am so upset about this. I am in the same situation as Shaun, I have searched for an alternative to Microsoft Outlook in the past and will continue to do so.
My carrier is Verizon and the technical support there was of no help what-so-ever, they are clueless and there is no way to speak to anyone who does have a clue.
With Google and Firefox biting at Microsoft's heels, when will they learn to treat their customer's with respect and realize that the first chance we get we will migrate elsewhere and your company will be gone. Stop worrying about the OEMs and start paying attention to US!
Tom - Notwithstanding my frustration I want to akcnowledge and thank 2GrokMobile and my contact at MS Australia, Rick, who have been hammering the support programmers to resolve the issue.
Unfortunately it would seem that their influence has limits and for the time being the cynical approach being taken by MS is to give greater priority to getting a new working product out on the market for sale that to fixing the malfunctioning product that their customers have already paid for. I am assured that MS haven't abandoned coming up with a fix for people like little ol' me but I am not holding my breath.
Rick has mitigated my frustration to some extent but drawing my attention to the My Phone software at myphone.microsoft.com. It offers a limited ability to keep your smartphone's calendar, contact and other data online. If your smartphone is synced with your PC then effectively this puts your PC's calendar and contact data online as well, and enables read/write access from any other web-connected PC. The downside is that automatic syncing only occurs once a day, and you have to view the online data through MS's web portal, which has extremely limited functionality compared to Outlook and lots of annoying advertisements. Presumably the advertising is the reason why the service is free, and also the reason why MS haven't integrated this service with Outlook.
- Hi all,
This issue is being reviewed now, and the tester wants to confirm the repro steps. I've listed them below - can you confirm that this are correct? It's also interesting to note that the first time through - they didn't generate the error but they did run into a certificate issue. Take a look at the repro steps and let me know if they're right/wrong, or if anything is missing. One question I have for you off the bat is, was your partnership created 1st on a 64bit machine, or on a 32bit machine and then taken to the 64bit machine?
Thanks for your patience....
Tested on Hermes, Build # 5.2.21824
1. Create partnership with Desktop ‘A’ running on Vista -64 bit OS
2. Sync the User A - outlook accn (We are using MS account)
3. Mails and calendar are up-to-date.
[Note - I'm getting, Security certificate on the server is not valid error whenever I sync. It says Contact your Exchange server administrator or ISP to install a valid certificate on the Server.
Please refer to the Screenshot – Are you seeing similar issue on your side also?]
4. Disconnect the device
5. Connect the device with Desktop ‘B’ running XP OS. Try creating partnership with Desktop ‘B’.
6. It doesn't allows to sync the folders of User-A which are already sync to the Desktop ‘A’.
7. Sync's different folders like favorites and Notes that it allows.
[Note - I'm getting, Security certificate on the server is not valid error whenever I sync. It says Contact your Exchange server administrator or ISP to install a valid certificate on the Server.]
8. Connect the device with Desktop ‘A’
9. It fails to sync with the Desktop. There are few new mails, it fails to update the folders. (Is this the problem we are talking about) .
10. It just gives, Security certificate on the server is not valid error whenever I sync. It says Contact your Exchange server administrator or ISP to install a valid certificate on the Server.
11. We didn’t get the error code you mentioned.
- Checking back for a confirmation of the repro steps listed above, and the current build that this is being tested on is a 6.1 device. I've also made sure to mention that the data is stored in a .PST file where it was entered by hand or downloaded from a mail service - i.e. not backed by an Exchange Server. In addition, I had them not sync mail as Shaun wasn't to see if that's the issue. I think that will get rid of the folder issue that they are seeing, and that was mentioned above in my earlier post.
Thanks!- Edited by2GrokMobileMSFTThursday, July 23, 2009 8:17 PM
- Edited by2GrokMobileMSFTThursday, July 23, 2009 8:33 PM
I have followed the log modification suggestion and sent 2GrokMobile the files from the sync with my home Vista box. I guess I'll try the uncheck everything and recheck 1x1 to get it to sync, then try to get the log files from my XP box at work next.
Confirmation of steps: your steps are a bit confusing to me, but I'll try to confirm or note differences.
1. First partnership setup was with desktop A = Vista -32 (home PC).
2. Sync'd all items except mail (didn't use mail sync at that time). Don't know what you mean by MS account (I understand MicroSoft, but don't know what you mean by MicroSoft acct).
3. All sync'd items up to date. No security cert issues.
5. Connect to desktop B = XP machine (work). This machine syncs w/ an Exchange server, but I am not sync'ing to the server; just the pc. No security cert errors.
6. Connect back to A
7. May or may not fail to sync. Doesn't touch anything; no items updated as far as I can tell.
8. No security cert errors, just the "problem with desktop" notice.- Hi Grok
Not sure if your questions are directed at me, however:
1. desktop A = Vista 64bit and desktop B = Vista 32 Bit
2. I get no security certificate error
3. I, general, I succeed in syncing with desktop B, except for some all day appointments which created syncing errors until I deleted them
4. I get the error when I then attempt to resync with desktop A- Proposed As Answer byTomParris Sunday, July 26, 2009 6:50 PM
- Unproposed As Answer byShaun Ginsbourg Sunday, July 26, 2009 8:45 PM
Sorry guys, this issue has been identified as a problem with the BUILD of your 6.1 mobile.
I have contacted HTC and Verizon about it.
Windows fixed the problem in build 1.2.6
Problem is that for some STUPID reason, Verizon/HTC are not offering this build version for upgrades on "older" phones, BUT they do on their current versions!!- Tom; That was identified earlier as the "fix", however several users (myself and CV27) have later builds of WinMo and STILL have the problem. We both have WinMo build = 20276.1.3.3 on the Verizon version of the Samsung Omnia. Therefore, I'm ASSUMING we have a later build (1.3.3) than the "fixed" build 1.2.6.
It is still broke... Grok;
I've sent you my Vista logs from my home pc, but I've run into a problem getting you XP logs from my work pc. There is no WindowsMobile directory in the Windows directory, nor anywhere on my hard drive. There is also no file that starts with wmdc or wmdhost on my local hard drive. Any suggestions?- Sigh .... any progress?
- My solution was to give up.
I had contact with HTC and Verizon both promised to follow up.. both did not.
I solved my problem with OsaSync. It is a GREAT program (difficult to install) that sync's beautifully over the LAN. It has a Web feature as well, but I did not try it. (I tried several other Sync products, this was the only one that worked for me)
SO, now I sync with just my laptop, and let the laptop and the desktop sync on their own. For me it actually works better and MUCH easier than having to plug in my phone to each divice and back again. OsaSync checks for changes every 5 minutes if you want it to!
Anyway, NO I do not have ANY affiliation with OsaSync, just am loving their product.
Tom - Well, it appears I finally solved it. What it took for me was a ROM flash. I have the Samsung Omnia via Verizon. They recently offered a ROM update to version CF03, which also updated WinMo to build 20961.1.5.1
I flashed the ROM 1 month ago today and have been able to sync on both ends every since. There is one more variable in the soup: I installed SPB mobile shell 3.0 at the same time (LOVE IT), but I really doubt that had anything to do with it. I really believe it is/was the BUILD of winmo, as Tom and others have said. However, I don't understand how I could have had a version (1.3.3) that was later than the "fixed" version (1.2.6) and still have had problems. So in my eyes, the solution is confirmed: you need to get an updated ROM with a new WM version from your carrier.- Proposed As Answer byHeiDO Friday, September 04, 2009 3:21 AM
- Unproposed As Answer byShaun Ginsbourg Friday, September 04, 2009 3:40 AM
- So Shaun, why do you unpropose my solution? It is because it won't work for you, or you don't believe it is the root cause? Because I believe there are many people looking for a solution and if the answer is "you need a new version of WM", they need to know that, even if it is a painful answer...
- HeiDO,
Both 2GrokMobile, a MS insider, and another person I was put in touch with from MS, appear to accept that the issue causing the error is one previously unknown to Microsoft (cf the "100 contact" problem) and have suggested that Microsoft will look into the problem. I am still waiting to hear back from them - although it looks likely at this stage that they have given up and don't have the courtesy to get back to me and tell me that I have wasted all this time trying to fix the problem.
If their response is, contrary to earlier indications, in effect, "Oh, actually, we have fixed that problem in aku xxx and will abandon investigating a solution for users of HTC Touch Pro and the many other models of handsets that appear to have this problem," then I will accept your solution.
Unless and until that occurs, I will assume that, for reasons peculiar to your model of handset, you have been fortunate enough to escape the evil clutches of error 0x86000107.
In the meantime I would be interested to hear from anyone else who has build 20961.1.5.1 on a non-Omnia handset as to whether they have this problem. - bump
In the meantime I would be interested to hear from anyone else who has build 20961.1.5.1 on a non-Omnia handset as to whether they have this problem.
I have build 19965.1.2.3 on a Touch Pro and get that error Shaun. Like you, I am frustrated with it and hate to get the issues when I sync with a second PC. I do not get it when I sync with one PC. I laugh because I never experienced the issue until either just before you started this thread or during the initial beginnings of it but I got it.
I had the issue with my HTC 8525 and after months of trouble shooting, I just stopped syncing it with 2 PCs. So when it occured with the Touch Pro, I couldn't help but think it was an issue related to the maker of the device. Of course we found out it was an issue and that MS sent a fix to the vendors .... of course we have not seen a release from HTC (or others as far as I know).
So I just got the new HTC Verizon Imagio and so far, no issues but if it comes back, I will be an unhappy camper.
The 861000107 error is STILL on my list of important issues to find (or get) resolution. I do ask about it about every 3-4 weeks just to keep it alive and I will continue to do that. I'm not sure if we will see any results but as an FYI, I am still asking.
Jack Cook
http://www.experiencemobility.net
http://www.mobilitysite.com- I have also asked 2GrokMobile and the team for an update again...
- I have a hp910C MSM 6.1. I emailed hp about the error immediately after I bought the phone and I was told it was a known issue. I've been reading and following the comments from everybody. I am surprised both MS and HP are doing absolutely nothing to rectify the problem. iPhone owns the space and MS mobile is not even trying...Android is coming...
