Re: Windows Mobile 5 Bug - ActiveSync 4.1 - Dell Axim X50V with Outlook Issues

Hi,
There are multiple causes for the 85010014 error. See
http://www.pocketpcfaq.com/faqs/acti...shoot-as4x.htm.


--
Chris De Herrera
http://www.pocketpcfaq.com
http://www.tabletpctalk.com
http://www.pocketpctalk.com
http://www.mobilitytalk.com

ActiveSync 4.x Troubleshooting Guide -
http://www.pocketpcfaq.com/faqs/acti...shoot-as4x.htm

"Flash" <> wrote in message
news: ups.com...
> ActiveSync 4.1 installed; Win XP lastest SP; Outlook 2003 latest SPs;
> Dell Axim X50V with Windows Mobile 5 from Dell.
>
> Sync worked fine for a while with Outlook then quit working. It is not
> the communication piece as I can sync other files and Browse the unit
> through Active Sync just nothing through Outlook - not contacts nor
> email with just headers. Additionally I hooked up an older HP Ipaq
> with older Windows Mobile 2003 and issue is NOT there so this is not an
> 'Outlook issue' to me - it is a bug in Windows Mobile 5.
>
> I have uninstalled ActiveSync resorted back to Active Sync 4,0 issue
> still present on Axim; upgraded back to 4.1 issue still present; hard
> reset unit many times and repaired outlook. If it was an issue with
> Outlook was does older Pocket PC sync??? Hence I am blaming Windows
> Mobile 5. Other than doing a complete removal of office (which should
> not be required since it talks to another unit) the only thing left is
> Windows Mobile 5.
>
> I have also used another profile/email account to not blame anything in
> my profile and issue still present.
>
> Again older Windows Mobile OS works fine just new OS that has issue.
>
> Tired of support code 85010014
>

Did you by any chance put in credentials for Pocket MSN? If so, a lot of
the WM5 devices (Phones) will refuse to sync unless right after a soft
reset.....
"Flash" <> wrote in message
news: oups.com...
> As far as all of the articles you referred. I did everything EXCEPT
> uninstall Outlook completely from my system. I did a repair on it and
> checked and verified all else from the articles without ANY success.
> Again, this seems directly like a BUG within Windows Mobile 5 or why
> under 2003 SE does it work fine --
>