Active Sync problems after loading WM2003, please reply

bandd · 10-08-03, 12:02 AM

I'm pulling my hair out. Loaded WM2003 and initial sync goes fine. After that everytime I try to sync it says "connecting to host" and immediately says "device connected" and just sits there. I've done everything, soft reset, hard reset, reloaded active sync, reloaded active synce 3.5 after flashing ROM back to A03. Everytime I do something different, it will sync and then the next time I try to sync it gives me the same message and just hangs. After it hangs for a while it says device disconnected try reconnecting or something. Someone please tell me how to fix this problem before I throw this thing across the room. Thanks.

pswets · 10-08-03, 12:29 AM

I have also recently upgraded to WM 2003. Good for me, bad for you, I haven't had the problems you've experienced. I sync to a computer at home and a different one at work, and it's working OK. (I still have the apparently Eudora-caused problem of deleting the mapi32.dll file a couple of times a day, but I can live, unhappily, with that.) Sorry, I can't help you without more data on your setup.

FLJeepGuy · 10-08-03, 08:08 AM

I noticed you made reference to using ActiveStink 3.5. Is this the only version you're using or are you dropping to 3.5 just trying to get things working. The current version is 3.7. I recommend you download and try this version if you haven't already.

You may also want to try connecting the Axim to a different USB port and/or not using a USB hub (if you have one). I had similar issues with my wife's Axim syncing to her Dell workstation. I worked with it for two weeks without sucess. I finally got it working after installing a cheap PCI USB 1.1 card that I had laying around. When connecting the Axim to this card, all the problems went away. I've never been able to reliably sync when connected to the Dell workstation's built in USB 2.0 ports.

As an interesting side note, I have a home-built workstation with an Asus motherboard with USB 2.0 ports. I've never had a problem on my system with my Axim or my wife's Axim. Both work fine with my USB 2.0 ports.

bandd · 10-08-03, 08:15 AM

I've gone to Active Sync 3.5 to try to fix the problem. Before I loaded WM2003 I was syncing through a USB 1.1 hub no problem. After having all the problems with WM2003 I flashed back to A03 and had sync problems like I described in first post. I've tried to sync through a USB 1.1 on the motherboard and a USB 1.1 and 2.0 hub. Now it's just letting me connect as a guest.

FLJeepGuy · 10-08-03, 09:32 AM

Delete your partnership, deinstall 3.5 and reboot, install 3.7, make sure your Ax's name doesn't contain spaces or underscores (Settings-System-About-Device ID), and then connect your Ax directly (not through a hub). You should then be able to create a new partnership and sync.

By the way, I'm just going through the things I've had success with so I may be going down paths you've already followed... Good Luck!

KnipKnup · 10-08-03, 09:45 AM

Activesync 3.7 is provided with the upgrade CD and the instructions gave me the impression WM2003 needed the newest version. Also, as jeepy above said, you should give your device a different name than pocket_pc (the default) BEFORE you attempt to sync.
Here's what I did:
1-hard reset
2-upgrade to as3.7
3-upgrade ax to wm2003 and when it was all complete (before creating a partnership)
4-rename ax while in cradle
5-create partnership and go
From there its all a matter of installing all the software from scratch.

I hope that helps.

bandd · 10-09-03, 12:02 AM

Thanks for the help. I'm back to WM2003 now. It's definitely something with the device ID. I've had several pocket PCs and don't remember HAVING to rename them upon initial connection. I've renamed them just for the hell of it before. The only thing I don't understand is after I would rename it, I could sync once and after that it would just connect as a guest. WM2003 seems to be working ok now so I'm going to leave it alone.