Can't download to device

[Anthony LaMark]

Hi All,

I am trying to use VS .Net 2003 with the compactframework using ActiveSync
3.7.1 and "SDK for Windows Mobile 2003-based Pocket PCs". I have also run
C:\Program Files\Microsoft Visual Studio .NET 2003\CompactFrameworkSDK\WinCE
Utilities\WinCE Proxy Ports Reg\ProxyPorts.reg but still get the error
message "Cannot establish a connection. Be sure the device is physically
connected to the development computer." The options are set to "Windows CE
..Net Device" (I am using a HP iPAQ rx3700) with Transport = "TCP Connect
Transport" using port number 5656 (I don't have the "Use fixed port number"
checkbox checked) and "Obtain an IP address automatically using ActiveSync".
Below is the WCESCOMM.LOG. One thing strange about the log is that the
ipaddress is 192.168.55.101 but my computers ip is 192.168.123.100 and the
handheld is 192.168.123.101. So either there is a bug in the logging
routing or the configuration is wrong. I ran TCPView and can see the
connections begin established but they break down right away. I see
everyone saying to uninstall 3.7.1 and then use 3.7. Is this the only
option? The posts are old enough that I would have thought Microsoft would
have come up with a hot-fix or something. Any wisdom regarding this issue
would be greatly appreciated. In the interim, I am doing my development
using eVC 4.0 SP3.

11/23/2004 12:11:09.234 - Windows CE Services (3.7.4034) Communication
Logging.
11/23/2004 12:11:09.234 - Logging file auto-purge after a successful device
connection.
11/23/2004 12:11:09.234 - Connection: Process connection from IP address
127.0.0.1:4627.
11/23/2004 12:11:09.546 - CesProxy: Accept on port 990, IsWinsock 1, hResult
0
11/23/2004 12:11:09.546 - TCP: ....S., 192.168.55.100(1105) =>
192.168.55.101(990) Seq=239018265-239018265 Ack=0 Win=8192 Len=44
11/23/2004 12:11:09.562 - TCP: .A..S., 192.168.55.101(990) =>
192.168.55.100(1105) Seq=-1617544326--1617544326 Ack=239018266 Win=32768
Len=44
11/23/2004 12:11:10.234 - CesProxy: Accept on port 990, IsWinsock 1, hResult
0
11/23/2004 12:11:10.234 - TCP: ....S., 192.168.55.100(1106) =>
192.168.55.101(990) Seq=239018953-239018953 Ack=0 Win=8192 Len=44
11/23/2004 12:11:10.234 - TCP: .A..S., 192.168.55.101(990) =>
192.168.55.100(1106) Seq=-1617309494--1617309494 Ack=239018954 Win=32768
Len=44
11/23/2004 12:11:10.656 - CesProxy: recv failed on Win socket 990, err =
10054
11/23/2004 12:11:10.656 - CesProxy: Close Win socket 990
11/23/2004 12:11:10.656 - CesProxy: Close PPP socket 990
11/23/2004 12:11:10.656 - TCP: ...R.., 192.168.55.100(1106) =>
192.168.55.101(990) Seq=239019144-239019144 Ack=-1617309453 Win=0 Len=40
11/23/2004 12:11:10.656 - CesProxy: recv failed on PPP socket 990, err =
10053
11/23/2004 12:11:12.500 - TCP: ....S., 192.168.55.101(1130) =>
192.168.55.100(999) Seq=-1616716911--1616716911 Ack=0 Win=32768 Len=48
11/23/2004 12:11:12.500 - Proxy: Connection Attempt on port 999, dest ip
0x6437a8c0
11/23/2004 12:11:12.500 - TCP: .A..S., 192.168.55.100(999) =>
192.168.55.101(1130) Seq=239021218-239021218 Ack=-1616716910 Win=8760 Len=44
11/23/2004 12:11:12.515 - CesProxy: Accept on port 999, IsWinsock 0, hResult
0
11/23/2004 12:11:12.546 - TCP: ....S., 192.168.55.101(1131) =>
192.168.55.100(5678) Seq=-1616649955--1616649955 Ack=0 Win=32768 Len=48
11/23/2004 12:11:12.546 - Proxy: Connection Attempt on port 5678, dest ip
0x6437a8c0
11/23/2004 12:11:12.546 - TCP: .A..S., 192.168.55.100(5678) =>
192.168.55.101(1131) Seq=239021265-239021265 Ack=-1616649954 Win=8760 Len=44
11/23/2004 12:11:12.578 - CesProxy: Accept on port 5678, IsWinsock 0,
hResult 0
11/23/2004 12:11:12.750 - TCP: ....S., 192.168.55.101(1132) =>
192.168.55.100(5678) Seq=-1616557183--1616557183 Ack=0 Win=32768 Len=48
11/23/2004 12:11:12.750 - TCP: .A..S., 192.168.55.100(5678) =>
192.168.55.101(1132) Seq=239021468-239021468 Ack=-1616557182 Win=8760 Len=44
11/23/2004 12:11:12.765 - CesProxy: Accept on port 5678, IsWinsock 0,
hResult 0

 

[Darren Shaffer]

Anthony,

I've had this happen frequently myself on a number of different development
machines and it typically involves an issue with the fact that the device is
connected to the development machine using a USB connection. If you don't
want to reinstall Activesync, run through these troubleshooting steps and
see
if any of it helps. Sometimes it has cleared up my "can't connect issue"
with
VS.Net2003 and ActiveSync 3.7.1.

http://www.cewindows.net/faqs/activesync/usbissues.htm#USB Issues

- Darren Shaffer

 

[Zanna]

Hi All,

I am trying to use VS .Net 2003 with the compactframework using ActiveSync
3.7.1 and "SDK for Windows Mobile 2003-based Pocket PCs". I have also run
C:\Program Files\Microsoft Visual Studio .NET 2003\CompactFrameworkSDK\WinCE
Utilities\WinCE Proxy Ports Reg\ProxyPorts.reg but still get the error
message "Cannot establish a connection. Be sure the device is physically
connected to the development computer."

I had the same problem and no one seemed to be able to resolve it (I
reinstalled ctiveSync, VS, checked register, configurations... no way).

A day browsing in VS directories I found DelDesktopCryptKey.exe.
I don't know if was it, but after I lauched id all work fine.

 

[Guest]

Hi Anthony!!!

I don't really understand what exactly is the problem you're getting.
However, I can tell you two things that might be usefull:

1. If the problem is that you cannot connect your PDA to your computer using
ActiveSync, then you have to look at your communication settings in your PDA,
your computer, and your ActiveSync installation. For example, if you're using
a serial port, be sure that both the PDA and the computer have the same
speed, the same parity and the same size of words, and ALSO that ActiveSync
can support serial port communication through the port you're using
(communcation settings). Also, be sure with your manufacturer that your
serial cable is the right one. In my particular case, I had a bad experience
in which the null modem I was using didn't have some other signals crossed,
and I spent a week before I could make a connection.

2. If the problem is that you cannot connect from Visual Studio to your PDA
even though your ActiveSync connection is working fine, then forget about
connecting using Visual Studio. Just compile your application, make its cabs
and copy them to your PDA (just like any other directory). After that, on
your PDA, just launch the cabs and the application should be installed.

The IP addresses that you're mentioning seems to be correct for subnet
masks of "255.255.0.0" and "255.0.0.0". If your computer has a subnet mask
of "255.255.255.0", then I'd suggest that that might be the source of the
problem.

Hope it helps!!!

PS: This post has been posted "AS IS"