Microsoft KB Archive/813579

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 18:02, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


BUG: Cannot deploy smart device application after you remove and reinstall ActiveSync

Article ID: 813579

Article Last Modified on 3/2/2006



APPLIES TO

  • Microsoft .NET Compact Framework
  • Microsoft ActiveSync 3.5
  • Microsoft Visual Studio .NET 2003 Enterprise Architect
  • Microsoft Visual Studio .NET 2003 Enterprise Developer
  • Microsoft Visual Studio .NET 2003 Academic Edition



Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry


SYMPTOMS

On a computer that has Visual Studio .NET 2003 installed, when you remove and reinstall ActiveSync 3.5, you cannot deploy a smart device application to a device that is connected over USB. You may receive the following error message:

Deploying to Pocket PC Device using TCP Connect Transport Error: Cannot establish a connection. Be sure the device is physically connected to the development computer.

CAUSE

When you install Visual Studio .NET, the installation writes registry entries that are related to the proxy port for ActiveSync. These proxy port registry entries inform ActiveSync to forward all localhost, proxy port-specific TCP data to the device. When you remove or reinstall ActiveSync, these registry entries are corrupted.

RESOLUTION

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this problem, you must recover the proxy port registry entries. To recover these registry entries, use one of the following methods:

  • Reinstall Visual Studio .NET. To do this, follow these steps:
    1. Remove and then reinstall Visual Studio .NET 2003.
    2. Restart the computer.

    For more information about how to remove and how to install Visual Studio .NET, click the following article number to view the article in the Microsoft Knowledge Base:

    312779 Visual Studio .NET 2002 Readme (Part 1)

  • Export and then import the proxy port registry entries. To do this, follow these steps:
    1. On the computer that does not have the problem, locate the following registry subkey:

      \\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows CE Services\ProxyPorts

    2. Right-click ProxyPorts, and then click Export.
    3. Save the registry file as Proxyport.reg.
    4. Copy the Proxyport.reg file to the computer that has the problem.
    5. Double-click Proxyport.reg, and then click Yes in the Registry Editor dialog box. This writes the proxy port registry entries to the registry.
    6. Restart the computer.


STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.


Additional query words: uninstall

Keywords: kberrmsg kbbug kbregistry KB813579