greenamyer

Greetings All and please accept my apologies in advance for what may be a common problem with an easy solution.

I've had my X5 for several years and have only recently encountered issues with syncing to my desktop (XP with Outlook 2000). The connection is established, it starts looking for changes, then posts a "Synchronization error" message, and reverts to the "Not Connected" state.

I've tried ActiveSync 4.2 and 4.5, and I've tried disabling my ZoneAlarm Security Suite, but I get the same result. Soft and hard resets don't work either. Hours on the Dell and Microsoft websites haven't been productive, except that it did lead me to Aximsite, so any help would be sincerely appreciated.

Jogga

Welcome to Aximsite greenamyer

As yours is an X5 it may be worth trying an earlier version of Activesync (3.8 perhaps). Other things to try:

• Make sure that the cradle is plugged in to a primary USB port (rather than a hub)
• Check for damaged pins on the connector
• Check your regional settings are correct
• Have you updated your BIOS on the PC?
• Try another PC if you have access to one

As a last resort, you could try deleting the current partnership and attempting to create a new one.

Good luck.

mostlylisten

If you have dsl or broadband i wouldn't hessitate to delete active sync and download 4.5 again and reestablish the partnership. I used to have x5 and had that problem and for some reason was able to download again and worked fine. If 4.5 is ok by microsoft to use with x5 no reason to downgrade. Its another problem.

greenamyer

Thanks Jogga. I tried it all without success. Downloaded a fresh version of 4.5 on a much newer computer, set up the relationship, same result. Can't see any damage on the pins, but there must be something wrong with the AXIM or the cradle.

I can't recall exactly when this problem arose, but it may coincide with my fixing a common problem with the touch screen, which required taking the unit apart and applying some tape to protect contacts from the buttons on the lower front.

Anyway, thanks again for your help. If you have any other ideas, please let me know.

greenamyer

Thanks too mostlylisten. I'm sure that I was running 4.5 before the problem started, but I noticed that Microsoft doesn't recommend it for use with Outlook 2000. But, as you can see in my reply to jogga, I tried it from scratch on a much newer computer and got the same result.