Knowledge Base

PRB: Platform Manager Reports Error Message: Connection Failed (Error Code =0xLX)

Article ID: 271190

Article Last Modified on 8/19/2005

APPLIES TO

Microsoft eMbedded Visual Basic 3.0
Microsoft Office Keyboard
Microsoft Windows CE Platform Software Development Kit for Handheld PC 2000

This article was previously published under Q271190

SYMPTOMS

When you run an application developed with eMbedded Visual Basic 3.0 on your Microsoft Windows CE device, the download process to the Windows CE device reports an error message:

Embedded Visual Basic:
Platform Manager reports error: Connection Failed (Error Code =0xLX) Make sure your device is connected. You may need to verify your configuration by pressing the Configure button in Project Properties. You also may need to reinstall the Platform SDK.

When you try to test the connection to your Windows CE device in the Platform Manager of your embedded Visual Basic environment, you may see the following error message:

Unable to connect to the device. Please make sure you have installed the underlying transport (e.g., ActiveSync) and have a device connected.

This problem may even occur when Microsoft ActiveSync already has a connection established to the Windows CE device at the same time.

CAUSE

This connection problem may occur with eMbedded Visual Basic, as well as with Microsoft eMbedded Visual C++, when the TCP/IP protocol is only bound to a Dialup adapter, for example, and not to a real network or Microsoft Loopback-Adapter.

RESOLUTION

If you have a Microsoft Windows 98-based computer with no network adapter installed, you may install a network adapter or configure the Platform Manager to use the "PPP Transport for Windows CE."

To do so:

On the Project menu, select Project Properties, select Configure Target, and then open the Platform Manager.
Select the default device that is connected to the desktop computer (for example, Pocket PC), and then click Properties.
Select PPP Transport for Windows CE, and then click Test.

If you have a Microsoft Windows NT 4.0-based or a Microsoft Windows 2000-based development computer, and you have no "real network adapter" installed, you may install a MS Loopback-Adapter. With TCP/IP protocol bound to the MS Loopback-Adapter you can also use Microsoft ActiveSync or TCP/IP as transport protocol.

For additional information about this topic, click the article number below to view the article in the Microsoft Knowledge Base:

236869 HOWTO: Install Microsoft Loopback Adapter in Windows 2000

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.

MORE INFORMATION

This problem can be reproduced when you have installed the eMbedded Visual Tools 3.0 on a desktop computer that does not have a real network adapter installed. Because you need TCP/IP protocol for ActiveSync, you may have installed only a dialup adapter. Even if Microsoft ActiveSync is working as expected, you may get the error or errors listed in the "Symptoms" section if you have bound the TCP/IP protocol only to the dialup adapter.

Steps to Reproduce Behavior

Start a new eVB or eVC Project.
On the Project menu, select Project Properties, select Configure Target, and then open Platform Manager.
Select the Pocket PC default device (connected through ActiveSync to the desktop), and then click Properties.
Select Microsoft ActiveSync or TCP/IP Transport, click Test, and note that you see the following error message:

"Establishing platform manager connection to the device"

After a while, you receive this additional error message from CEMGRUI:

"Unable to connect to the device. Please make sure you have installed the underlying transport (e.g., ActiveSync) and have a device connected."

Additional query words: Error Code =0xLX 0xLX

Keywords: kbbug kbprb KB271190

Microsoft KB Archive/271190

Contents