PDAsync reports that ActiveSync is not running when connecting to a Windows Mobile 5 device. Active Sync is running, how do I get PDAsync to work?
There seem to be three things that can cause this issue:
- Sometimes the device reports the wrong mobile OS. When that happens, we send it the wrong CAB
file. To check for this, check Add/Remove Programs in the Tools menu of AS4.1 to find the file size
of LapLink PDASync. What we have typically seen in these situations is the 87kb CAB (PPC2003) is
installed instead of the 194kb CAB (PPC5.0), but if it’s anything other than the 194kb CAB (it
actually shows as 193.6kb), then the wrong CAB got pushed. To fix this, follow these directions:
- Open C:\Program Files\Common Files\XCPCSync.OEM\Laplink.213-103\Translators\PocketPC
- Rename the file XTNDConnect PC.ini to XTNDConnect PC.ini.bak.
- Rename the file XTNDConnect PC.WM5.ini to XTNDConnect PC.ini
- Remove LapLink PDASync using Active Sync
- Sync again and the correct cab should be loaded
- If this is not the issue, then we have seen where Pocket PC CAB gets installed in the wrong place. If you have a removable storage card, such as MiniSD, SD, or MMC and you told the install to put our CAB onto the memory card (it prompts when a memory card is detected), rather than default internal memory, this problem can occur. In this case, you need to uninstall Laplink PDAsync from the device, soft reset the device, and then re-sync to push the cab on again using internal (default) memory this time.
- Sometimes Windows firewalls get in the way. If the devices are Pocket PC 5.0, then it is possible that either a firewall is blocking your ActiveSync stuff (AS 4.1 is very finicky) or ActiveSync is not telling us the correct device model and the wrong CAB is being pushed onto the device.To test the firewall theory, temporarily disable any firewalls (such as Windows Firewall, ZoneAlarm, Kerio, Norton and McAfee). Then test a sync and see if it works. If so you need to add exceptions to your firewall until you get a successful sync with the firewall enabled.
KB: 361 Last updated: May 25, 2006