I have just got my Axim X51v. I installed the activesync 4.0 (come with the CD) to my laptop. I have winodws 2000 service pack 4.0. But the AS4.0 seemed to recognize my X51v but got stuck in connecting...

I talked to the Dell support. They suggested me to uninstall and then install again for AS4.0. Problem still existed. I have disable ZoneAlarm, VPN, and my WI-FI. Still have problem. I phoned Dell support again and she told me to upgrade to Activesync 4.1 which I did. Now, it is even worst! The activesync will NOT recognize the X51v anymore.

Anybody can help?

This happens to me quite often and all I do to correct the problem is lift my Axim out of the cradle for 5 - 10 sec and replace it into the cradle. Give it time to connect...don't rush it.

Jim

Sometimes when it seems to hang up I fix it by soft resetting the Axim.

I have been trying to help gene101, and what we did was we left the PDA in the cradle for at least a minute or two, and it was still stuck in the 'Connecting...' state. We will try to soft reset the Axim, but that is a surprising solution, since the Axim is brand new. It isn't even a day old yet.

does anybody has the same experience?

I understand some people do have problems with ActiveSync 4.0 and WM5.

I am on my 3rd Pocket PC in 6 years and the Soft Reset has proved to solve many, many problems.

Brad

I have the same problem with my Axim and my wife's IPAQ, both running WM5 with AS 4.1. The workaround is to make sure the ppc is "on" when you plug it in. If you re-boot the pc with it cradled, it won't ever connect. If you reset the ppc when cradled it won't ever connect. The only sure way I've found is to make sure the pc and the ppc are both up and finished booting before you cradle it. Since doing this, I've never had the problem again. Hope this clears your problem!

Gene, I had a similar situation -- x51v frozen at the "connecting" stage -- and had to do a few things before it worked reliably. See:

http://www.aximsite.com/boards/showthread.php?t=107714

I'm convinced that ActiveSync is so fragile that multiple things can cause it to fail -- bad drivers, hidden vpn/firewall problems, slightly tweaked network configurations, the registry pointing in a bad direction, left-over DLLs from prior installations -- so sometimes you've gotta work your way through a number of possible solutions.

Had this same problem after I upgraded to AS 4.0 and upgraded my X50v to WM 5.0. It seems this combination is just very unstable. I would sometimes randomly get it to connect, but I couldn't tell you how I got it to work each time. It seemed I took very many random and illogical steps.

Interestingly enough, I downgraded my X50v back to WM 2003SE w/o downgrading AS back to 3.7 and AS is working as smoothly as it used to before I upgraded my PDA to WM 5.0. This leads me to believe the instability, for me, was being caused on the PDA's end and not by the new version of AS on my desktop computer.

I did notice I was having lots of issues w/ AS starting on its own and slowing down my PDA under WM 5.0, so the above hypothesis would not surprise me at all.

I had this same problem and after trying everything everyone has posted I still couldn't get it to work. I ended up downloading the most current chipset drivers for my PC (Dell Precision workstation) and it fixed the problem. I've still decided to downgrade back to 2003SE, just too much BS trying to get this to work. Hope this helps someone!

Trev

Wow. It never ceases to amaze me how many different ways Microsoft found for ActiveSync to screw up. RaViNLuNeY, that's a totally new one: I haven't read that one anywhere.

We (gene101 and I) were trying to get ActiveSync to work on Windows 2000. We finally managed to get it working on Windows XP Home, which is on another computer. It is an inconvenience, but at least it works. With Microsoft, that's usually how it goes.

One thing that I found in order to pinpoint the problem was to uncheck all sync options (in active sync window - tools, options). And then one by one add the calendar then sync. Add the contacts then sync, etc. There could be a conflict with one of the options. Mine was with favorites. I know how frustrating it is to not be able to sync, especially when in a hurry.