Windows Mobile 5.0 and ActiveSync 4.1 Challenges
April 18, 2006 by Jason Bean
Filed under Computers
I got a new smart phone today, the problem is it’s being pretty dumb and irritating the fire out of me. I know I risk large amounts of ridicule by posting this on here, but hey, I’m not afraid to fire back at Microsoft for some things they really need to get fixed.
I’m on Sprint and the new phone I got is Pocket PC PA10A1. I’ve been more than happy with Sprint’s service, except when you talk to their accounting department, then they all seem to have lost their minds. So, I’ll be sure and check on the costs of my recent upgrade to their PCS Vision Plan. Should only be another $15/mnth.
So, I’m very happy with my new device. I’ve got everything set the way I like it (at least for now). I’ve got the Wi-Fi working with my home network no problem. I got ActiveSync4.1 installed, but I can’t get a successful synch to occur. I keep getting the following error codes:
ActiveSync encountered a problem on the desktop.
Support Code:85010014
and
Synchronization Error 85010017
Now, I’ve already read the following, and not gotten anywhere further after following their directions.
Synchronization Issues with Microsoft Outlook
If you are experiencing difficulties setting up and completing synchronization of data with Microsoft Outlook, please refer to the following section to find details about symptoms and workarounds.Synchronization Error 85010017
In some cases, ActiveSync will fail to synchronize data with Microsoft Outlook with Synchronization Error code 85010017. This could be due to the presence of large volume of items on first sync or specific large items such as a calendar item with many meeting attendees. Some targeted instances of this have been fixed in ActiveSync 4.1.
If you are experiencing this on Windows 2000 or Windows XP SP1, please upgrade to ActiveSync 4.1. Otherwise you can try archiving your inbox to reduce the number of items in the mailbox for synchronization.
Synchronization Error 85010014
ActiveSync reports a Synchronization Error code 85010014 because of one of the following reasons:
- Synchronization Fails because Application Data Folder is Redirected
- Synchronization Fails because Outlook is in Offline Mode
- Synchronization Fails because of Outlook script blocking
- Synchronization Fails because ActiveSync is incorrectly registered with Outlook
I’ve updated and “Fixed & Repair” Outlook. I’ve “Googled” and MSN’d (just doesn’t have the same ring) to find a solution and nothing has seem to work. I’ve reset all my settings in Outlook, almost losing all of my loads of client e-mail data. And I’ve done and redone and done again all of the steps trying to get this thing to synch. No luck.
If anyone out there has come across this, let me know. I’m dying to get this thing going and begin to share more Microsoft experience on this blog with everyone.
Come on Microsoft! What’s the deal. It’s Outlook 2003 and ActiveSync 4.1. The most current versions of both applications, both have been updated with the latest patches and fixes. Why can’t you get your own programs to play nicely together.
[Let the anti-Microsoft comments begin!, even though I'm not going to agree with you]
Shocking isn’t it. It should be so easy, and I’ve had it working on other servers, but when a problem pops up it’s a nightmare.
I’ve had microsoft rdp in to a server for 4 hours solid and they still couldn’t figure out why it wasn’t working. Got to a point where it works on an emulator, but not on 3 different windows mobile 5 devices. Wierd.
WHAT I DID THAT WORKED (for now, at least)
- Turn off Windows (and any other) Firewall
- Backup Outlook to a .pst file, just in cast
— Outlook> File > Import Export > Export to File > Personal Folder File (.pst) > select top level Folder (repeat for any other top level folders)
- Remove PPC from USB connection to PC
- Go to Activesync> File > Delete Mobile Device
- Connect PPC to PC with USB connection
- When asked, only Sync Contacts, Calendar, Tasks and Favorites first
- After successful sync, to to > Tools> Options> add Notes (I have a lot of Note files, which seemed to be the source of my problems in the past.)
- This should result in an automatica sync that will hopefully be successful.
None of the above ever worked for me reliably even to a clean device with a fresh hard reset.
I did get it to do a full sync a few times, but every time it left the WM 5 device I had (Cingular 8125) extremely slow (it could take 30-60 secs just to open contacts or to navigate in calendar from one day to another).
I tried hard for 3 months to get the sync to work for a real amount of data (2000+ contacts, 4000+ appointments). Finally, I met so many people having the same issue with wm5 and activesync 4, I just gave up and moved on to a Symbian device.
I recently purchased an SE M600i which is working so much more nicely. I got a full sync on the first try!! And, despite having all my contacts and appointments on it, the interface is nice and quick. This phone does have some sync issues, but nothing like I had with my WM5 device. (If you want a symbian phone with a near perfect, effortless sync – try the SE 910 – I got the 600 because I wanted something smaller).
Good luck!
This is amazing. I have no desire to “uninstall outlook” or anything else from my PC. What kind of shoddy business is that?? But, as well, no other suggestions worked for me either. I’ve been using activesync with Office 2003 and Office 2007 Beta with no probs (ActiveSync 4.1). I moved to Office 2007 RTM and a week later (not immediately) syncing stopped working. I also tried it with 4.2 and 4.5 beta of activesync to no avail.
This is just unbelievable! Even my colleague has the same problem and out of 110 people in our company, nobody has figured it out yet – and we are one of the Microsoft’s Gold Partners!!!
Its the firewall.
I had similar problems with ActiveSync 4.1 and xda Mini S. Although my firewall was specifically commanded to enable all active Sync activities, it still caused problems, allowed me to drag and drop files but REFUSED to synchronise.
Bottom line, I turned off the firewall (Zone Alarm) and it works fine! Will need to fine tweak firewall though, dont want nasty hackers.
Just got a HP hw6945 unlocked for $600.
I previously had and still own Palm Vx, Treo 270, Treo 680, Symbian devices.
In sum, at WM5 this OS is at best beta ready. Same for the devices. There are so many issues that allgo back to core bad programming, lousy testing and no support, that MS should can the whole thing. Maybe they are even doing it. There is no KB section for WM5 to be found…
In a bigger picture, also the recent Palm OS 5 has its (similar) issues, but they are not as grave as WM5. Further, the slow down in performance (waiting 60 sec for a phone to boot up ???), syncing and lack of basics (HTML email ???) combined with draw of battery (mine lasts 6h with minimal phone calls) is so primal, that the nice design and all-around features (WiFi, GPS, Cell & PDA in one box) become pale and irrelevant.
Sorry MS, just another MS screw up.
PS as to the error: It appears to be a badly designed syncing protocol that has problems with writing and keeping track of what is going on for itself. Just bad programming. No executive will want to deal with that.
I’ve had all sorts of issue with Active Sync 4.1 / 4.2 with my PocketPc running Windows Mobile 5.0, the fix I found that worked instantly was to download Microsoft Active Sync 4.5
http://www.microsoft.com/downloads/details.aspx?FamilyID=9e641c34-6f7f-404d-a04b-dc09f8141141&DisplayLang=en
FIXED!
Alister Walters
Nuclear Studio
I am running already OL 2003, ActiveSync 4.5 and all the latest patches. The sync issues are abundant. It may take as little as to remove the ipaq from the cradle and putting it back and all of a sudden the sync process does not start, it appears discinnected, does not transfer email data, but calendar and vice versa, in all various combinations. Then this connection troubler shooter comes up, does a test run, builds its log and wants to send it to Redmond. No reply or solution ever from them.
I think this is all high priced beta testing. Palm had been at that level ten years ago. MS is just ten years behind everything, Apple, iPod, Palm, you name it…
I am running version 4.5 of active sync with my T-Mobile MDA and all had been working perfect until today. I Googled error number 85010014 and found this site. After reading all of the helpful information above, I was just about to uninstall/reinstall when I decided to check the Task Manager to see what was running.
I found that even though I DID NOT have Outlook open, there was 2 instances of OUTLOOK.EXE running. Using the Task Manager, I closed both instances out and then I plugged in my MDA. Viola, it synced without a hitch.
I hope this helps someone else, because I know that I went crazy for like an hour trying to get this thing working.
Hi I just bought a dopod c720w, OS window Mobile 5, and try to run it with activesync.. now i have instead of 85010014 a 86000107 .. gosh.. anybody there who might have this as well ?
Hi I just bought a dopod c720w, OS window Mobile 5, and try to run it with activesync 4.5.. now i have instead of 85010014 a 86000107 .. gosh.. anybody there who might have this as well ?
Gentlemen, I think firewall is the issue and there is no need to uninstall AS or OL. I tried deleting the profiles several times; it did help to hook AS to OL but still did not sync the contacts. I disable the firewall (Windows own) – the sync went perfect and everything was backed up. I re-enabled the firewall, re-syncked – the sync went OK. I guess the firewall settings are somewhat esoteric.
PS. For a number of other software packs, it is also recommended to start them first without firewall to let them train, then restart firewall and restart the program. Oh that MS…
Thank you Papasik for that information. It is odd to recommend that you have to turn off Microsoft’s own firewall to make sure applications run properly initially. The “training” idea makes sense though.
i followed one of the suggestions above and the 85010014 error was gone and syncing is ok. I simply went to “help” in outlook 2003 and then “Detect and Repair”. Check “Restore” but unckeck “Discard”, then hit OK. After a while the repair is done and syncing occurred again, this time without the nasty error!
I am using Win2000, AS4.1, WM5, and Outlook 2003. Hope this helps.
After several months using a Symbian device (SE M600i) I really missed some things about the Pocket PC platform. And when I started using the push mail solution for the M600i I found it no longer let me sync the device directly with the laptop. Which was my main reason for switching…. So I decided to give it WM a try again with a Cingular 8525 (I got a good deal on Ebay).
I upgraded the 8525 to WM2006 (you can find instructions on the internet) and am using ActiveSync 4.5 with no problems at all. The sync worked the first time perfectly. I had one small problem later that was resolved by turning off “advanced tcpip” or something similar.
I really can’t believe how much better it is. For those of you that can upgrade your firmwares to WM2006, you may want to try it. And for those of you still stuck with synch issues – I feel your pain – good luck!
I had the problem of being stuck on “Syncronizing”…
What I FINALLY figured out was to allow port exceptions in the firewall to allow ActiveSync through. I had blocked this on the domain, so I added the following ports to be allowed through:
- 990: open inbound TCP port
- 999: open inbound TCP port
- 5678: open inbound TCP port
- 5679: open outbound UDP port
- 5721: open inbound TCP port
- 26675: open inbound TCP port
(all i had to do was read the help file with activesync…’doh!!!)
As SOON as I enabled this, activesync worked like a charm!!
I hope that helps someone as frustrated as I have been.
Who would have thought to actually read hte entire help file?!! Thanks for sharing this great tip Kenny.
I was having the 86000209 error. The info I found that helped me fix mine was at:
http://www.pocketpcfaq.com/faqs/activesync/exchange_errors.php
Summary: In ActiveSync (I did it on PC, others say do it on handheld, I assume it doesn’t matter) open Options and DEselect email for synch. You get a warning about removing email from the handheld. Fine.
When you save the change, you sync automatically. Mine proceeded smoothly and…voila. Back in business. Later, you go back and REselect email so you start synching again.
FYI: My problem started after I developed a problem with my outlook.pst file. I could no longer send or received. After many attempts to solve the problem (detect/repair, repair from Add/Remove, use scanpst and one or two others I don’t remember now) I simply renamed outlook.pst, re-opend outlook, and started fresh with a new pst, then imported stuff from the old file manually. New file is fine, but the synch problem kicked in.
Now that’s okay, too.
Thanks, everyone.
Dudes,
You are yanking your batteries without shutting down first.
Bad boys!
I had the 86000209 error, but not today. Why? Because I powered off last night, and never swapped batteries yet today.
(Now, if I can just get Comodo to accept AS, I can sync thru my firewall…)
hey
i got this o2 XDA atom
and i recently installed some securty software.
and the problem now is i restarted and it asks for password and does not display the keyboard. i dont have a keyboard . how can i reinstall windows mobile 5.0 or solve the problem ??
help me guys
gyas
If you are part of a domain you need to be a local administrator of the domain on the PC. This can be done under user accounts. The problem is with the Windows firewall, but adding the user as an administrator will sort this issue. I am sure that user not part of the domain, mmust make sure they have administrator rights on the local machine, and then check the firewall to make sure it allows active sync and it’s components.
85010017 is what I get when Quickbooks 2008 is running. Seems QB has an Outlook contact DDE and locks the connection. If the phone is plugged in first or QB is not running then Async can do it’s thing. Earlier versions of QB had a contact sync to Outlook too. Could be an issue for some of you.
wow, this registry fix from one of the first posts worked for me and that information is over 2 years old.
http://blogs.geekdojo.net/andy/archive/2004/08/31/2983.aspx