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
"Vince Chin" <vtopg...@nospam-hotmail.com> escreveu na mensagem
news:580101c376d2$3a1bdc60$a401...@phx.gbl...
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...
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...
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
>.
>
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
>.
>
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...
good luck,
carl
"Vince Chin" <vtopg...@nospam-hotmail.com> wrote in message news:<065401c376db$245a02e0$a001...@phx.gbl>...
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
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
>.
>
>.
>
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