RE: Deployment / Debugging Problem
From: Darren Shaffer (DarrenShaffer_at_discussions.microsoft.com)
Date: 09/27/04
- Next message: Darren Shaffer: "RE: List Box (VB.NET Compact Framework)"
- Previous message: Darren Shaffer: "RE: Unable to Connect to Remote Server"
- In reply to: Peter Kemp: "RE: Deployment / Debugging Problem"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 27 Sep 2004 16:17:02 -0700
Peter,
Glad you got things working, but I think, like the solutions I listed, you
did something that worked this time and it probably won't work consistently.
I always login as local admin on three different dev boxes and still have
this issue sporadically.
WCESMGR is the culprit, but I don't know how to give you a permanent fix.
-Darren
"Peter Kemp" wrote:
> Hi Darren
>
> Thanks for the reply
>
> I had tried the things you suggested previously with no luck, but just this
> morning I tried something different. It goes like this.
>
> Normally I login to my machine using a domain account which is an admin for
> the domain and my machine. This time I logged in with a local machine admin
> account, then created a simple 'Hello World' app for the Pocket PC tried
> deploying it and to my surprise it worked first time no problems. I then
> logged out an back in with my normal domain account and everything works the
> way it used to.
>
> Hopefully this may be of help to you in future too.
>
> Thanks again
>
> Peter
>
> "Darren Shaffer" wrote:
>
> > Peter,
> >
> > This happens occasionally on all of my development PCs when I attempt to
> > deploy to device from VS.NET 2003 using Activesynch 3.71. There is no
> > permanent fix - it is an Activesynch problem. On different occasions, one of
> > the following fixes the problem for me for a period of time:
> >
> > 1) import the proxy ports registry entry on your PC running ActiveSynch.
> > the registry entry to import is located at:
> >
> > \Program Files\Microsoft Visual Studio .NET 2003\CompactFrameworkSDK\WinCE
> > Utilities\WinCE Proxy Ports Reg
> >
> > 2) try deploying a second time
> > 3) disconnect the device, wait 5 seconds, reconnect and wait for a
> > partnership to be established. redeploy.
> > 4) power off the device. connect it while powered off and the device wakes
> > up, Activesynch establishes a partnership, and redeploy
> > 5) soft reset the device, partnership, redeploy
> > 6) restart VS.NET 2003
> > 7) restart the PC running Activesynch
> >
> > Yes, this is just no fun. I've been experiencing this for 2+ years now and
> > have never seen a permanent solution to it. At various times, all of the
> > things above have fixed it (for a while).
> >
> > -Darren
> >
> >
> > "Peter Kemp" wrote:
> >
> > > Hi All
> > >
> > > I am having a problem deploying and debugging a pocket pc application.
> > > Problem is when I try to deploy to the device I get this error:
> > > 'Cannot establish a connection. Be sure the device is physically connected
> > > to the development computer.'
> > > The result is that i can no longer debug applications. The device is
> > > connected properly and ActiveSync (3.7.1) works fine. I have heard this
> > > version can cause problems but it is the version I have always used.
> > >
> > > This only started occurring recently after working fine for months. I have
> > > tried all suggested solutions in this discussion group with no success. The
> > > only thing I haven't done and don't want to do, is rebuild my PC from scratch.
> > >
> > > I know there are others out there with this problem so any help would be
> > > greatly appreciated.
> > >
> > > Regards
> > > Peter
- Next message: Darren Shaffer: "RE: List Box (VB.NET Compact Framework)"
- Previous message: Darren Shaffer: "RE: Unable to Connect to Remote Server"
- In reply to: Peter Kemp: "RE: Deployment / Debugging Problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
