Log in

View Full Version : Continuing ActiveSync Problems


mochegod
02-23-2004, 12:00 AM
I am continuing to receive the following error message when trying to sync my IPAQ 2215 to my desktop computer:
Synchronization cannot be completed successfully. Disconnect your device and try again. If the problem persists, see Microsoft ActiveSync Troubleshooter in Microsoft ActiveSync Help on your desktop computer

When examining the wcesmgr.log is see the following:
**** ActiveSync (3.7.3244 RETAIL) started, Cmd line: '/onconnect'
2004-02-22 14:28:30 00000C8C - Checking existing partnership on device 0x57D64AF9.
2004-02-22 14:28:32 00000C78 - IE Version:6.0.2800.1106 IE5=1
2004-02-22 14:28:32 00000C78 - DTPT: Setting DTPT network to {7BF8440A-8631-97AB-D4C7-0AA46B352FE9}
2004-02-22 14:28:32 00000C78 - DTPT: Send DTPT Network={7BF8440A-8631-97AB-D4C7-0AA46B352FE9}. Result=0x00000000
2004-02-22 14:28:33 00000C78 - Server sync version: 1.1
2004-02-22 14:28:33 00000C78 - Found PIM at 'C:\PROGRA~1\MICROS~2\Office10\OUTLOOK.EXE'
2004-02-22 14:28:33 00000C78 - Found PIM at 'C:\PROGRA~1\MICROS~2\Office10\OUTLOOK.EXE'
2004-02-22 14:28:33 00000C8C - Connected to device 0x57D64AF9 (PocketPC, Pocket_PC) [partner 0]
2004-02-22 14:28:33 00000C8C - **** Starting synchronization engine
2004-02-22 14:29:34 00000CC8 - ERROR: Connection to ActiveSync on the device failed. Error: 0x80145001 Socket Error: 0x274A

I have no prior difficulty with ActiveSync over the past 6 months. I can still explore the files in my IPAQ from my desktop. I've also run "Detect and Repair" on Outlook.

I am far from an expert in computers, so any help would be greatly appreciated. I am running Outlook 2002 on XP Home, and ActiveSync 3.71

ctmagnus
02-23-2004, 01:29 AM
When examining the wcesmgr.log is see the following:
2004-02-22 14:29:34 00000CC8 - ERROR: Connection to ActiveSync on the device failed. Error: 0x80145001 Socket Error: 0x274A

This tells me there's a problem with ActiveSync on the iPaq end. Have you tried a soft-reset?

mochegod
02-23-2004, 06:12 AM
Well, I seem to have stumbled luckily onto a solution. A second detect and repair of Outlook and a reboot seems to have corrected the problem. Although, I'm still in the dark as to what caused the problem in the first place. Thanks to all who offered their help!