C
Clark Wilson
My ActiveSync 4.5 synchonization with a Windows Mobile 6 device spontaneously
went bad soon after unexpected building power loss and power restore events.
The PPC syncs okay with another, nearly identical laptop. The same ActiveSync
error message occurs whether I am synching via cable or via Bluetooth. The
laptop is XP Pro SP2 with security patches applied.
My most recent Bluetooth attempt ended with this sequence of messages (from
WCESCOMM.LOG):
11/11/2008 08:55:19.353 - Proxy: Created dynamic proxy on port 1026.
11/11/2008 08:55:22.212 - TCP: ....S., 192.168.55.101(1084) =>
192.168.55.100(7438) Seq=71602742-71602742 Ack=0 Win=32768 Len=48
11/11/2008 08:55:22.228 - Proxy: Connection Attempt on port 7438, dest ip
0x6437a8c0
11/11/2008 08:55:22.228 - TCP: .A..S., 192.168.55.100(7438) =>
192.168.55.101(1084) Seq=48282187-48282187 Ack=71602743 Win=8760 Len=44
11/11/2008 08:55:22.415 - TCP: ....S., 192.168.55.101(1085) =>
192.168.55.100(990) Seq=71684538-71684538 Ack=0 Win=32768 Len=48
11/11/2008 08:55:22.431 - Proxy: Connection Attempt on port 990, dest ip
0x6437a8c0
11/11/2008 08:55:22.431 - TCP: .A..S., 192.168.55.100(990) =>
192.168.55.101(1085) Seq=48282390-48282390 Ack=71684539 Win=8760 Len=44
11/11/2008 08:55:23.212 - CesProxy: Accept on port 7438, IsWinsock 0,
hResult 0
11/11/2008 08:55:23.212 - CesProxy: Accept on port 990, IsWinsock 0, hResult 0
11/11/2008 08:55:23.915 - TCP: ....S., 192.168.55.101(1088) =>
192.168.55.100(990) Seq=72095441-72095441 Ack=0 Win=32768 Len=48
11/11/2008 08:55:23.931 - TCP: .A..S., 192.168.55.100(990) =>
192.168.55.101(1088) Seq=48283890-48283890 Ack=72095442 Win=8760 Len=44
11/11/2008 08:55:24.306 - CesProxy: Accept on port 990, IsWinsock 0, hResult 0
11/11/2008 08:55:24.478 - TCP: ....S., 192.168.55.101(1089) =>
192.168.55.100(990) Seq=72245999-72245999 Ack=0 Win=32768 Len=48
11/11/2008 08:55:24.478 - TCP: .A..S., 192.168.55.100(990) =>
192.168.55.101(1089) Seq=48284437-48284437 Ack=72246000 Win=8760 Len=44
11/11/2008 08:55:25.400 - CesProxy: Accept on port 990, IsWinsock 0, hResult 0
11/11/2008 08:55:25.400 - CesProxy: recv failed on Win socket 990, err = 10054
11/11/2008 08:55:25.415 - CesProxy: Close PPP socket 990
11/11/2008 08:55:25.431 - CesProxy: recv failed on Win socket 990, err = 10054
11/11/2008 08:55:25.431 - TCP: ...R.., 192.168.55.100(990) =>
192.168.55.101(1088) Seq=48283891-48283891 Ack=72246004 Win=0 Len=40
11/11/2008 08:55:25.447 - CesProxy: Close PPP socket 990
11/11/2008 08:55:25.462 - CesProxy: recv failed on PPP socket 990, err = 10053
11/11/2008 08:55:25.478 - CesProxy: Close Win socket 990
11/11/2008 08:55:25.494 - TCP: ...R.., 192.168.55.100(990) =>
192.168.55.101(1089) Seq=48284438-48284438 Ack=72246004 Win=0 Len=40
11/11/2008 08:55:25.494 - CesProxy: recv failed on PPP socket 990, err = 10053
11/11/2008 08:55:25.509 - CesProxy: Close Win socket 990
Do these messages point anyone to a diagnosis and fix? Is there another
newsgroup better suited to this question?
CHW
went bad soon after unexpected building power loss and power restore events.
The PPC syncs okay with another, nearly identical laptop. The same ActiveSync
error message occurs whether I am synching via cable or via Bluetooth. The
laptop is XP Pro SP2 with security patches applied.
My most recent Bluetooth attempt ended with this sequence of messages (from
WCESCOMM.LOG):
11/11/2008 08:55:19.353 - Proxy: Created dynamic proxy on port 1026.
11/11/2008 08:55:22.212 - TCP: ....S., 192.168.55.101(1084) =>
192.168.55.100(7438) Seq=71602742-71602742 Ack=0 Win=32768 Len=48
11/11/2008 08:55:22.228 - Proxy: Connection Attempt on port 7438, dest ip
0x6437a8c0
11/11/2008 08:55:22.228 - TCP: .A..S., 192.168.55.100(7438) =>
192.168.55.101(1084) Seq=48282187-48282187 Ack=71602743 Win=8760 Len=44
11/11/2008 08:55:22.415 - TCP: ....S., 192.168.55.101(1085) =>
192.168.55.100(990) Seq=71684538-71684538 Ack=0 Win=32768 Len=48
11/11/2008 08:55:22.431 - Proxy: Connection Attempt on port 990, dest ip
0x6437a8c0
11/11/2008 08:55:22.431 - TCP: .A..S., 192.168.55.100(990) =>
192.168.55.101(1085) Seq=48282390-48282390 Ack=71684539 Win=8760 Len=44
11/11/2008 08:55:23.212 - CesProxy: Accept on port 7438, IsWinsock 0,
hResult 0
11/11/2008 08:55:23.212 - CesProxy: Accept on port 990, IsWinsock 0, hResult 0
11/11/2008 08:55:23.915 - TCP: ....S., 192.168.55.101(1088) =>
192.168.55.100(990) Seq=72095441-72095441 Ack=0 Win=32768 Len=48
11/11/2008 08:55:23.931 - TCP: .A..S., 192.168.55.100(990) =>
192.168.55.101(1088) Seq=48283890-48283890 Ack=72095442 Win=8760 Len=44
11/11/2008 08:55:24.306 - CesProxy: Accept on port 990, IsWinsock 0, hResult 0
11/11/2008 08:55:24.478 - TCP: ....S., 192.168.55.101(1089) =>
192.168.55.100(990) Seq=72245999-72245999 Ack=0 Win=32768 Len=48
11/11/2008 08:55:24.478 - TCP: .A..S., 192.168.55.100(990) =>
192.168.55.101(1089) Seq=48284437-48284437 Ack=72246000 Win=8760 Len=44
11/11/2008 08:55:25.400 - CesProxy: Accept on port 990, IsWinsock 0, hResult 0
11/11/2008 08:55:25.400 - CesProxy: recv failed on Win socket 990, err = 10054
11/11/2008 08:55:25.415 - CesProxy: Close PPP socket 990
11/11/2008 08:55:25.431 - CesProxy: recv failed on Win socket 990, err = 10054
11/11/2008 08:55:25.431 - TCP: ...R.., 192.168.55.100(990) =>
192.168.55.101(1088) Seq=48283891-48283891 Ack=72246004 Win=0 Len=40
11/11/2008 08:55:25.447 - CesProxy: Close PPP socket 990
11/11/2008 08:55:25.462 - CesProxy: recv failed on PPP socket 990, err = 10053
11/11/2008 08:55:25.478 - CesProxy: Close Win socket 990
11/11/2008 08:55:25.494 - TCP: ...R.., 192.168.55.100(990) =>
192.168.55.101(1089) Seq=48284438-48284438 Ack=72246004 Win=0 Len=40
11/11/2008 08:55:25.494 - CesProxy: recv failed on PPP socket 990, err = 10053
11/11/2008 08:55:25.509 - CesProxy: Close Win socket 990
Do these messages point anyone to a diagnosis and fix? Is there another
newsgroup better suited to this question?
CHW