Debugging VS.Net "Cannot establish a connection." Errors

Anybody got any clues on debugging the error:

Error: Cannot establish a connection. Be sure the device is physically
connected to the development computer.

I just upgraded my development system from ActiveSync 3.5 to 3.7 (build 3083
and hopefully NOT 3.7.1) and now none of my CF projects can be deployed of
my primary devo box. I've got multiple iPaqs and other devo systems and
they all work except any device attached to my primary devo system.

I can sync and see all folders on an attached iPaq and I can run Remote
Display Control Host so it is not a connectivity issue.

I'm using a cable and USB connection.

In VS my tools -> options ->Device Tools ->Devices for Pocket PC Device is
set to use Transport: TCP Connect Transport and Startup Server is:
ActiveSync Startup Provider.

I've never changed these and everything was fine until AS 3.7. I tried
uninstalling 3.7 and reinstalling 3.5 and that didn't work either.

Are there any debug switched or log files that I can look at.

I'm ready to format my drive and reinstall windows (Arggh...)

Funny thing is now my emulators don't work on this system either (and it is
connected to a network that also works).

Antares
Fri Dec 19 04:43:03 CST 2003

Here there's the solution:

http://www.opennetcf.org/Forums/topic.asp?TOPIC_ID=305

Antares

>-----Original Message-----
>Anybody got any clues on debugging the error:
>
>Error: Cannot establish a connection. Be sure the device
is physically
>connected to the development computer.
>
>I just upgraded my development system from ActiveSync 3.5
to 3.7 (build 3083
>and hopefully NOT 3.7.1) and now none of my CF projects
can be deployed of
>my primary devo box. I've got multiple iPaqs and other
devo systems and
>they all work except any device attached to my primary
devo system.
>
>I can sync and see all folders on an attached iPaq and I
can run Remote
>Display Control Host so it is not a connectivity issue.
>
>I'm using a cable and USB connection.
>
>In VS my tools -> options ->Device Tools ->Devices for
Pocket PC Device is
>set to use Transport: TCP Connect Transport and Startup
Server is:
>ActiveSync Startup Provider.
>
>I've never changed these and everything was fine until AS
3.7. I tried
>uninstalling 3.7 and reinstalling 3.5 and that didn't
work either.
>
>Are there any debug switched or log files that I can look
at.
>
>I'm ready to format my drive and reinstall windows
(Arggh...)
>
>Funny thing is now my emulators don't work on this system
either (and it is
>connected to a network that also works).
>
>
>.
>

Paul
Fri Dec 19 09:10:46 CST 2003

You might also check the FAQ when stuff like this comes up:

http://msdn.microsoft.com/mobility/prodtechinfo/devtools/netcf/FAQ/default.aspx

Paul T.

"Antares" <anonymous@discussions.microsoft.com> wrote in message
news:073601c3c61c$e0dbf000$a601280a@phx.gbl...
> Here there's the solution:
>
> http://www.opennetcf.org/Forums/topic.asp?TOPIC_ID=305
>
> Antares
>
> >-----Original Message-----
> >Anybody got any clues on debugging the error:
> >
> >Error: Cannot establish a connection. Be sure the device
> is physically
> >connected to the development computer.
> >
> >I just upgraded my development system from ActiveSync 3.5
> to 3.7 (build 3083
> >and hopefully NOT 3.7.1) and now none of my CF projects
> can be deployed of
> >my primary devo box. I've got multiple iPaqs and other
> devo systems and
> >they all work except any device attached to my primary
> devo system.
> >
> >I can sync and see all folders on an attached iPaq and I
> can run Remote
> >Display Control Host so it is not a connectivity issue.
> >
> >I'm using a cable and USB connection.
> >
> >In VS my tools -> options ->Device Tools ->Devices for
> Pocket PC Device is
> >set to use Transport: TCP Connect Transport and Startup
> Server is:
> >ActiveSync Startup Provider.
> >
> >I've never changed these and everything was fine until AS
> 3.7. I tried
> >uninstalling 3.7 and reinstalling 3.5 and that didn't
> work either.
> >
> >Are there any debug switched or log files that I can look
> at.
> >
> >I'm ready to format my drive and reinstall windows
> (Arggh...)
> >
> >Funny thing is now my emulators don't work on this system
> either (and it is
> >connected to a network that also works).
> >
> >
> >.
> >