Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Device Connection Issue - Be sure device is physically connected...

2 views
Skip to first unread message

Vince Chin

unread,
Sep 9, 2003, 8:59:38 AM9/9/03
to
Hi,

I've researched this thoroughly and it's clear that many
people are experiencing the error:
"Error: Cannot establish a connection. Be sure the device
is physically connected to the development computer."

I've tried all the solutions posted on this forum and none
have solved the problem.

Everything was working fine until yesterday when I
couldn't connect to my iPaq 3870 via Visual Studio.net
2003. Also at the same time my Emulators: PPC2002,
PPC2003 experienced the same problem.

I uninstalled both of their SDKs and reinstalled, this
solved the emulators but not the iPaq so I uninstalled all
SDKs, & Visual Studio.net 2003 and the reinstalled
everything. The problem is still there, I cannot connect
to the iPaq 3870 via Stuiod.net 2003.

I donwloaded the "Windows CE .NET Utilities for Visual
Studio .NET 2003.EXE" app and merged the "ProxyPorts.reg"
with my registry and also deleted the ConnectionManager
files. None of these worked.

Without resorting to wiping my hard-drive and
reinstalling, what's left to do?

Sorry for the long-winded email but after wasting 2 days
trying different solutions and researching this issue,
I've got nowhere and I've resorted to manually copying
files to the iPaq using Windows Explorer.

Setup:
Windows XP Prof
Visual Studio.net 2003
ActiveSync 3.7 (which has not been uninstalled/reinstalled)
PPC 2002 SDK
PPC 2003 SDK

Regards

Vince Chin

Alberto Silva

unread,
Sep 9, 2003, 9:12:29 AM9/9/03
to
I think that what was missed was the AS reinstalation after VS.net
uninstall. That's the way I fixed the problem to conencto to my ipaq5450...

Alberto Silva

"Vince Chin" <vtopg...@nospam-hotmail.com> escreveu na mensagem
news:580101c376d2$3a1bdc60$a401...@phx.gbl...

Alberto Silva

unread,
Sep 9, 2003, 9:15:16 AM9/9/03
to
Are the pocketPC SDK needed for VS.net 2003, or just for the evTools?

AFAIK, when you choose the target as PocketPC you don't specify which PPC
version, and last week I depolyed sucessfully a project from VS.net 2003 to
an old PocketPC 2000 device, without having the PocketPC 2000SDK... It seems
that it's up to the compact framework to manage the dealing with the PPC...

Alberto Silva

"Vince Chin" <vtopg...@nospam-hotmail.com> escreveu na mensagem
news:580101c376d2$3a1bdc60$a401...@phx.gbl...

Shanti

unread,
Sep 9, 2003, 9:16:36 AM9/9/03
to
First of all, did you try 'Hard Reset' on PPC?

Secondly, don't know what are all the tricks posted here. There can still be
some that you have not noticed. So instead of saying that you have tried all
that posted so many times, it would have been helpful if you have mentioned
what exactly you have tried.

Thirdly, I only pray that this doesn't happen to me. This is really becoming
a nightmare. If no solution is found, 200+ dollars goes down the drain.

ThanQ...

"Vince Chin" <vtopg...@nospam-hotmail.com> wrote in message
news:580101c376d2$3a1bdc60$a401...@phx.gbl...

Vince Chin

unread,
Sep 9, 2003, 10:03:27 AM9/9/03
to
Thanks Shanti for the prompt reply.

I did try 'Hard Reset' and Soft Reset.

You said:
"it would have been helpful if you have mentioned
>what exactly you have tried."

I did:
1. I uninstalled both of their SDKs and reinstalled
2. Then Uninstalled SDKs, & Visual Studio.net 2003 and the
reinstalled everything again.
3. I downloaded the "Windows CE .NET Utilities for Visual


Studio .NET 2003.EXE" app and merged the "ProxyPorts.reg"
with my registry

4. And also deleted the ConnectionManager files.

I've also emailed Ximing Zhou, 'xim...@microsoft.com'
with my problem as he replied to others on this forum with
similar issues and I'm hoping he'll help out.

Cheers

Vince

>.
>

Vince Chin

unread,
Sep 9, 2003, 10:09:01 AM9/9/03
to
Hello Alberto,

Thanks for the prompt reply.

I just tried reinstalling AS and rebooting the PC. Funny
thing is, the PC on reboot went through hardware detection
again on the iPaq, wierd?

Anyway, it didn't work so I Hard Reset the iPaq and reran
the "ProxyPorts.reg" file, also cleared the
ConnectionManager files, and deleted all previous
partnerships hoping to clear all previous AS connections.

Still the problem's there, I can't connect to my iPaq
through Visual Studio.net 2003. But I can now connect to
all my Emulators, so there was some success.

Thanks for your help

Regards

Vince

>.
>

Alberto Silva

unread,
Sep 9, 2003, 12:31:11 PM9/9/03
to
Vince,
Now I remember... besides having reinstalled ActiveSync 3.7 BEFORE vstudio,
I went to these folders and I deleted the whole subtrees, before installing
vs.net

C:\Documents and Settings\AlbertoSilva\Application
Data\Microsoft\VisualStudio
C:\Documents and Settings\AlbertoSilva\Local Settings\Application
Data\Microsoft

I hope this helps...

Alberto Silva

"Vince Chin" <vtopg...@nospam-hotmail.com> escreveu na mensagem

news:065401c376db$245a02e0$a001...@phx.gbl...

Carl Dumas

unread,
Sep 9, 2003, 1:25:47 PM9/9/03
to
Vince,
I'm going through the same trama. If you have any joy fixing it
without complete format c:, please post it. I have also tried all the
tricks you have.
this is extremely frustrating. It happened to me about 3 months ago
and I had to nuke my system and start fresh. Now I have a project to
deploy in 3 days and it happens again.

good luck,

carl

"Vince Chin" <vtopg...@nospam-hotmail.com> wrote in message news:<065401c376db$245a02e0$a001...@phx.gbl>...

Vince Chin

unread,
Sep 10, 2003, 5:47:35 AM9/10/03
to
Thanks Alberto,

I tried what you suggested, but I've still got the same
problem. Thanks anyway.

Carl, I'm currently corresponding with Microsoft's Ximing
Zhou [xim...@microsoft.com] who has supplied a
troubleshooting tool. I've ran the tool and returned the
logs, so considering time differences I'm hoping to get a
reply later today. I'll keep you posted, or you could
also contact Ximing (we'll gang up on him :-) )

Cheers

Vince

Vince Chin

unread,
Sep 11, 2003, 3:19:55 AM9/11/03
to
Hello Carl,

I'm glad to say Ximing Zhou, xim...@microsoft.com has
fixed the problem for me. He sent me a utility
called "DelDesktopCryptKey.exe" which I ran through a cmd
window and it done-the-job. Ximing said "This tool is not
released yet but will be included in the next version of
Windows CE .NET Utils pack."

Hoooraayy.

Thanks Ximing

Vince Chin

>.
>

JohnB

unread,
Sep 11, 2003, 7:40:13 AM9/11/03
to
It would be very nice if Microsoft would share with us
what this utility does. I know I am one of many that has
this problem and has given up on finding the solution.
Every time I see a message thread start, I've monitored
the thread and more often than not, there is no
solution.
I'm glad you're working.

>.
>

Jan Yeh

unread,
Sep 15, 2003, 12:31:11 AM9/15/03
to
Hello,

I believe that many people are suffering from "Unable to establish a
connection" &
"Unable to start debugging" situations. There are couples of solutions in
the newsgroup,
some works for some situation, and some doesn't.

Mine is NB with WinXP Prof. and HP Jornada 568, connected by cradle & CF
NIC...
Debugging never works on my NB,
but it goes well on my PC(Win2K, the same device)...

I searched many threads, and tried many ways trying to solve this problem.
Including the recently "Windows CE Utilities for .NET Compact Framework",
SDAuthxxx.exe.

Yesterday, I saw a thread talking about this.
And I try to log in with another account which has administrator authority,
and it works fine.
Then I turn back to log in with the original one, still fail.

That's really a great finding.
I believe that there must be some settings were wrong in the registry or
personal profiles.
Re-install the whole machine would be a extreme solution, but re-install
VS.NET 2003 is
already a torture :(
However, that need someone more perseverant to keep finding, or wait for
MSFT to release
some patches or explainations.

Following is some milestones articles in the locus of my searching...

Loopback adapter
There are tons of this solution, so I skip this link...

Un-install and Re-install VS.NET
I even delete reside keys in registry HKLM(HKCU as
well)\Software\Microsoft\VisualStuio...

ProxyPorts Registry
http://groups.google.com.tw/groups?hl=zh-TW&lr=&ie=UTF-8&oe=UTF-8&frame=right&th=33076538f84b5347&seekm=tNJMW4m7CHA.2260%40cpmsftngxa08.phx.gbl#link5

Windows CE Utilities for Visual Studio .NET 2003 Add-on Pack
http://groups.google.com.tw/groups?hl=zh-TW&lr=&ie=UTF-8&oe=UTF-8&frame=right&th=33076538f84b5347&seekm=9ZKFx6y8CHA.1640%40cpmsftngxa06#link14

WinCEConfig tool solution
http://groups.google.com.tw/groups?hl=zh-TW&lr=&ie=UTF-8&oe=UTF-8&frame=right&th=dd220c169ee838b0&seekm=%236Zksy0tCHA.2496%40TK2MSFTNGP10#link2

Login with another account
http://groups.google.com.tw/groups?hl=zh-TW&lr=&ie=UTF-8&oe=UTF-8&frame=right&th=dd220c169ee838b0&seekm=eKNA9IlxCHA.1620%40TK2MSFTNGP11#link13

If you have any other resource or findings, it's welcome to follow the post.
BTW, I wish most is to know the mechanism how debugging over TCP connection
works.

Best Regards,
Jan Yeh


Martin Robins

unread,
Sep 16, 2003, 10:56:59 AM9/16/03
to
Ok,
 
Just tried this at work and it did not work!
 
However, if you are reading this thread then look for a thread "Unable to deploy or debugging... Some clues!" started on 15/09/2003 within which Ximing Zhou from MS has posted a fix that did work for me.
 
Best of luck.

 

"Martin Robins" <martin - robins @ ntlworld dot com> wrote in message news:OUVo1B9e...@TK2MSFTNGP12.phx.gbl...
> Ok, try again; OE6 managed to work out what it was even though it was
> renamed! Now it is in a zip.
>
> "Martin Robins" <martin - robins @ ntlworld dot com> wrote in message
>
news:e3GNo88e...@TK2MSFTNGP10.phx.gbl...
> > Microsoft have accepted that this is a problem and posted a proposed
> > solution in the knowledge base:
> >
http://support.microsoft.com/default.aspx?scid=kb;en-us;813579.
> >
> > I have yet to confirm if this works as I have the problem on my work
> machine
> > and not at home, I have however attached a ProxyPorts.reg file for those
> of
> > you who do not have access to another machine that is working.
> >
> > I will be trying this in the office tomorrow, but if anybody cares to try
> it
> > earlier and let me know if it helps then great.
> >
> > Martin.
> >
> > NB: Usual disclaimers apply; I promise this is a genuine reg file
> containing
> > only my ProxyPorts registry branch but if your machine dies all you will
> get
> > from me is a sorry message.  Please check the file for yourself before
> > installing.
> >
> >
> >
> > "Vince Chin" <
vtopg...@nospam-hotmail.com> wrote in message
> >
news:580101c376d2$3a1bdc60$a401...@phx.gbl...
0 new messages