VS not connect with activesync

[Felix González]

Hi,

I´ve uninstalled activesync and 3.7 and instaled activesync 3.8. and now I
can connect with active but VS can´t connect. what can I do?


thanks

 

[Dick Grier]

Hi,

When I had this problem in the past, what I did was to uninstall ActiveSync,
uninstall VS! (sorry), reboot, re-install ActiveSync, reboot, reinstall VS!
(sorry, again).

Others have had success fiddling with the registry, but I don't have those
details.

Dick

--
Richard Grier (Microsoft Visual Basic MVP)

See www.hardandsoftware.net for contact information.

Author of Visual Basic Programmer's Guide to Serial Communications, 4th
Edition ISBN 1-890422-28-2 (391 pages) published July 2004. See
www.mabry.com/vbpgser4 to order.

 

[Ilya Tumanov [MS]]

Gee, no need for such drastic measures. Please download this tool and fix
your connectivity problem in about 10 seconds:



http://www.microsoft.com/downloads/...a6-2095-4086-b0cc-7c6c39b28762&displaylang=en



From readme:



I uninstalled ActiveSync and then reinstalled it. Now I can't deploy my
application. How do I fix this?

Issue: After uninstalling ActiveSync version 3.5, 3.6, 3.7 or 3.71,
deploying fails with the error message "There were deployment errors.
Continue?" This typically happens when one version of ActiveSync is
uninstalled and a newer version is installed.

Solution: Uninstalling these versions of ActiveSync removes some registry
settings that are required for deployment. You must restore these registry
settings to enable deployment.

To restore the registry settings

1. 1. Import ProxyPorts.reg. to the registry.

Note ProxyPorts.reg is located by default in Program Files\Microsoft
Visual Studio .NET 2003\CompactFrameworkSDK\WinCE Utilities\WinCE Proxy
Ports Reg.

2. 2. Remove the device from the cradle and replace it. If
deployment still does not work, soft-reboot the device.





Best regards,



Ilya


This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Dick Grier]

Hi Ilya,

This tool needs to be found more easily. These problems have been manifest
for a couple of years. This is the first mention that I've seen (and I
don't go around with my eyes closed).

The oft mentioned complaint is, "The Microsoft search engine sucks." I have
to say that I agree.

Dick

--
Richard Grier (Microsoft Visual Basic MVP)

See www.hardandsoftware.net for contact information.

Author of Visual Basic Programmer's Guide to Serial Communications, 4th
Edition ISBN 1-890422-28-2 (391 pages) published July 2004. See
www.mabry.com/vbpgser4 to order.

 

[Dick Grier]

Specifically, this note in the Readme>>>

I get a device connection error when deploying or debugging, but other logon
users on the same computer can connect to the same device with Visual Studio
..NET. How do I fix this?

Issue: Deployment to a Pocket PC or Windows CE device connected with
ActiveSync fails with the error message "Could not establish a connection
with the device. Please make sure the device is connected and working
properly." Other logon users on the same computer may be able to deploy and
debug using the same device, ActiveSync is working correctly, and the file
\Windows\ConManClient.exe is not copied to the device when attempting to
deploy or debug.

Solution: These symptoms indicate a possible corrupted security key
container. On the computer running Visual Studio .NET, run
DelDesktopCryptKey.exe from the command prompt to clean the security key
container for the current user.

Note DelDesktopCryptKey.exe is located by default in Program
Files\Microsoft Visual Studio .NET 2003\CompactFrameworkSDK\WinCE
Utilities\DelDesktopCryptKey.

Not too hard to find, right?

Dick
--
Richard Grier (Microsoft Visual Basic MVP)

See www.hardandsoftware.net for contact information.

Author of Visual Basic Programmer's Guide to Serial Communications, 4th
Edition ISBN 1-890422-28-2 (391 pages) published July 2004. See
www.mabry.com/vbpgser4 to order.