Lost connection from VS2003 to PocketPC

  • Thread starter Thread starter Jim Bloom
  • Start date Start date
J

Jim Bloom

I'm weeping.

I can't get VS2003 to connect with my iPaq anymore. It just says that it can't connect. It's been working fine for six months.

I've tried all of the stuff I've found...

- Deldesktopcryptkey.exe
- WinCEProxyPortsReg
- Reinstall VS2003
- Reinstall ActiveSync
- Reinstall WinCE Utilities for .NET
- Reinstall 2003 SDK
- Reinstall CompactFrameworkSP2

When I run the Deldesktopcryptkey program from a command line, I get an error:
CryptAcquireContext DELKEYSET error 0x80090016

....and I can't find anything on the new about this error.

Activesync is working fine with the ipaq. It just shouldn't be this difficult.

Anyone care to help a poor man? I'm losing it.
 
Hi!
some months ago I had exactly the same problem and i lost more than a
week searching all the solution. Unfortunately the only things that
worked, for me, was the reinstallation of the entire OS...:-(

If it's not too hard to do it's the easiest way. Maybe not the right way
but... if you have tried all the other ways, clean up your computer! :-)


Cheers

Carlo
 
Hi Carlo.
Thanks for letting me know. I'm dreading it, but I don't know what else to
do.
Regards,
Jim
 
First, the error fromDelDesktopCryptKeys means that the key set does not exist - probably an expected result after it runs successfully
Second, what does "can't connect" mean? Can't deploy or can't debug? Which one does not work - F5 or Ctrl-F5?


--
Alex Feinman
---
Visit http://www.opennetcf.org
I'm weeping.

I can't get VS2003 to connect with my iPaq anymore. It just says that it can't connect. It's been working fine for six months.

I've tried all of the stuff I've found...

- Deldesktopcryptkey.exe
- WinCEProxyPortsReg
- Reinstall VS2003
- Reinstall ActiveSync
- Reinstall WinCE Utilities for .NET
- Reinstall 2003 SDK
- Reinstall CompactFrameworkSP2

When I run the Deldesktopcryptkey program from a command line, I get an error:
CryptAcquireContext DELKEYSET error 0x80090016

...and I can't find anything on the new about this error.

Activesync is working fine with the ipaq. It just shouldn't be this difficult.

Anyone care to help a poor man? I'm losing it.
 
Hi Alex. Thanks much for responding.

I'm unable to debug. So, I click the arrow to send the latest build to the ipaq for debugging, and it just says that it can't connect. I can rebuild cabs, recompile, etc... and that works fine. It sounds very much like the same issues as the other, historical posts...many of whom find relief through deldesktopcryptokey and WinCEProxyPortsReg.

I can use any of the emulators for debugging (WM2003, WM2003SE, etc...). I can also use Embedded VB and it can connect, compile and send to the ipaq. All of the remote monitoring tools with VBCE also work fine. So, I assume it is a .NET CF issue, but I just can't figure it out.

I sure would appreciate any wisdom you can share.

Thank you!
Jim
 
And does Ctrl-F5 deploy and launch application?

--
Alex Feinman
---
Visit http://www.opennetcf.org
Jim Bloom said:
Hi Alex. Thanks much for responding.

I'm unable to debug. So, I click the arrow to send the latest build to
the ipaq for debugging, and it just says that it can't connect. I can
rebuild cabs, recompile, etc... and that works fine. It sounds very much
like the same issues as the other, historical posts...many of whom find
relief through deldesktopcryptokey and WinCEProxyPortsReg.
I can use any of the emulators for debugging (WM2003, WM2003SE, etc...).
I can also use Embedded VB and it can connect, compile and send to the ipaq.
All of the remote monitoring tools with VBCE also work fine. So, I assume
it is a .NET CF issue, but I just can't figure it out.
 
Neither of them work. I am unable to test the application on the iPaq.

Build works fine...starts to try to send it to the iPaq and it says..."could
not establish a connection...<make sure it's hooked up>...".

I've also reflashed the iPaq, just in case the problem was on that end. The
ActiveSync Remote Display app (from Power Tools) works fine.

Thanks again, Alex.
Jim

Alex Feinman said:
And does Ctrl-F5 deploy and launch application?

--
Alex Feinman
---
Visit http://www.opennetcf.org
Jim Bloom said:
Hi Alex. Thanks much for responding.

I'm unable to debug. So, I click the arrow to send the latest build to
the ipaq for debugging, and it just says that it can't connect. I can
rebuild cabs, recompile, etc... and that works fine. It sounds very much
like the same issues as the other, historical posts...many of whom find
relief through deldesktopcryptokey and WinCEProxyPortsReg.
I can use any of the emulators for debugging (WM2003, WM2003SE, etc...).
I can also use Embedded VB and it can connect, compile and send to the ipaq.
All of the remote monitoring tools with VBCE also work fine. So, I assume
it is a .NET CF issue, but I just can't figure it out.
I sure would appreciate any wisdom you can share.

Thank you!
Jim
not
exist - probably an expected result after it runs successfully that
it can't connect. It's been working fine for six months.
 
Back
Top