Connection Failed. The bootstrap could not be loaded. (Someone from MS?)

D

Daniel McCarty

I'm assuming that my problem must be pretty rare, since a lot of people
use VS2005 by now and a lot of people must use it to debug managed
apps. I have a CE5.0 device running a platform built on our BSP.
We've also exported an SDK that I installed for VS2005.*

I am connected to the device via ActiveSync 4.1. When I try to debug I
choose the device I want to deploy to, and VS reports

------ Deploy started: Project: NetConfApiTest, Configuration: Debug
Any CPU ------

After a little while I get the error

The bootstrap could not be loaded.
(also see http://h1.ripway.com/dpm/Usenet/bootstrapNotFound.jpg)

There isn't much information about this error, but I did find some
Usenet articles saying that it might be related to the processor ID. I
found some sample code from Ilya Tumanov [MS] and compiled it into a
project and ran it, and it reported my ID as

2336 (0x920)

(This is PROCESSOR_ARM920, which is correct, since our OEMInit() is
setting CEProcessorType to this value. The device is based on the
ARMv4I.**)

Last year when VS was in beta there were two MSDN Blog articles about
debugging without ActiveSync:
- http://blogs.msdn.com/vsdteam/archive/2005/01/05/347332.aspx, and
- http://blogs.msdn.com/vsdteam/archive/2005/04/28/413304.aspx

This method works for us. However, it is cumbersome in the least and
not the ideal way to debug. If anyone has any suggestions for
deploying and connecting normally they would be greatly appreciated.

Best regards,
Dan.


* This is all happening on a brand new PC running XP Pro (SP2), PB 5.0,
eVC 4.0, VS2005 and our SDK (installed in that order). (No QFE's have
been installed yet.)

** I can verify that
C:\dev\VS8\SmartDevices\SDK\CompactFramework\2.0\v2.0\WindowsCE\wce500\armv4i\NETCFv2.wce5.armv4i.cab
exists, although I don't know what CPU ID it's trying to match.
 
C

Chris Edgington

Dan, have you tried a regular Win32 app (non-managed), to see if the
framework runtime is part of the problem or not?

-Chris

Qualnetics Corporation
cedgington at qualnetics dot com
 
D

Dan McCarty

Chris said:
Dan, have you tried a regular Win32 app (non-managed), to see if the
framework runtime is part of the problem or not?
Click to expand...

No, a Win32 app has the same problem. Here is a sample from output
window:

1>------ Deploy started: Project: NT2, Configuration: Debug
WestellMediaTerminal (ARMV4I) ------

[...waiting here about a minute or two...]

1>The bootstrap could not be loaded.

========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped
==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
 
G

Guest

I had the exactly the same problem and finally fixed this yesterday.
I can't said if this the true solution, so let me(all of us) know if it is
or not,
because I tried uninstall and re-install so many times and I think when I
reinstall PB5.0, it messed it up so bad all debug don't work including the
emulator, which it used to work.

This is the error that I got when I got trying to fix the "The bootstrp..."
problem.
“The configuration data for this product is corrupt. Contact your support
personnel.â€

then I find this (BUT I DON'T HAVE VS2005 BETA INSTALLED):
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=104023&SiteID=1
and all I did was delete this dir:
%userprofile%\Local Settings\Application Data\Microsoft\CoreCon\1.0 Folder
and all files under it.

then when I try the ARM Device Emulator, I got a different message, which is
because the setting to the resolution is gone. once fixed the emulator worked.
Then I uninstall my custom device SDK, then try the Windows CE 5.0 device and
it worked. then I install back the custom device SDK and use that and it
still works.

So, after all this I believe just deleting this folder is the key solution
%userprofile%\Local Settings\Application Data\Microsoft\CoreCon\1.0 Folder



Daniel McCarty said:
I'm assuming that my problem must be pretty rare, since a lot of people
use VS2005 by now and a lot of people must use it to debug managed
apps. I have a CE5.0 device running a platform built on our BSP.
We've also exported an SDK that I installed for VS2005.*

I am connected to the device via ActiveSync 4.1. When I try to debug I
choose the device I want to deploy to, and VS reports

------ Deploy started: Project: NetConfApiTest, Configuration: Debug
Any CPU ------

After a little while I get the error

The bootstrap could not be loaded.
(also see http://h1.ripway.com/dpm/Usenet/bootstrapNotFound.jpg)

There isn't much information about this error, but I did find some
Usenet articles saying that it might be related to the processor ID. I
found some sample code from Ilya Tumanov [MS] and compiled it into a
project and ran it, and it reported my ID as

2336 (0x920)

(This is PROCESSOR_ARM920, which is correct, since our OEMInit() is
setting CEProcessorType to this value. The device is based on the
ARMv4I.**)

Last year when VS was in beta there were two MSDN Blog articles about
debugging without ActiveSync:
- http://blogs.msdn.com/vsdteam/archive/2005/01/05/347332.aspx, and
- http://blogs.msdn.com/vsdteam/archive/2005/04/28/413304.aspx

This method works for us. However, it is cumbersome in the least and
not the ideal way to debug. If anyone has any suggestions for
deploying and connecting normally they would be greatly appreciated.

Best regards,
Dan.


* This is all happening on a brand new PC running XP Pro (SP2), PB 5.0,
eVC 4.0, VS2005 and our SDK (installed in that order). (No QFE's have
been installed yet.)

** I can verify that
C:\dev\VS8\SmartDevices\SDK\CompactFramework\2.0\v2.0\WindowsCE\wce500\armv4i\NETCFv2.wce5.armv4i.cab
exists, although I don't know what CPU ID it's trying to match.
Click to expand...
 
D

Dan McCarty

That did it! VS recreated the folder and it connected over ActiveSync.

Thank you very much.

-Dan
I had the exactly the same problem and finally fixed this yesterday.
I can't said if this the true solution, so let me(all of us) know if it is
or not,
because I tried uninstall and re-install so many times and I think when I
reinstall PB5.0, it messed it up so bad all debug don't work including the
emulator, which it used to work.

This is the error that I got when I got trying to fix the "The bootstrp..."
problem.
"The configuration data for this product is corrupt. Contact your support
personnel."

then I find this (BUT I DON'T HAVE VS2005 BETA INSTALLED):
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=104023&SiteID=1
and all I did was delete this dir:
%userprofile%\Local Settings\Application Data\Microsoft\CoreCon\1.0 Folder
and all files under it.

then when I try the ARM Device Emulator, I got a different message, which is
because the setting to the resolution is gone. once fixed the emulator worked.
Then I uninstall my custom device SDK, then try the Windows CE 5.0 device and
it worked. then I install back the custom device SDK and use that and it
still works.

So, after all this I believe just deleting this folder is the key solution
%userprofile%\Local Settings\Application Data\Microsoft\CoreCon\1.0 Folder



Daniel McCarty said:
I'm assuming that my problem must be pretty rare, since a lot of people
use VS2005 by now and a lot of people must use it to debug managed
apps. I have a CE5.0 device running a platform built on our BSP.
We've also exported an SDK that I installed for VS2005.*

I am connected to the device via ActiveSync 4.1. When I try to debug I
choose the device I want to deploy to, and VS reports

------ Deploy started: Project: NetConfApiTest, Configuration: Debug
Any CPU ------

After a little while I get the error

The bootstrap could not be loaded.
(also see http://h1.ripway.com/dpm/Usenet/bootstrapNotFound.jpg)

There isn't much information about this error, but I did find some
Usenet articles saying that it might be related to the processor ID. I
found some sample code from Ilya Tumanov [MS] and compiled it into a
project and ran it, and it reported my ID as

2336 (0x920)

(This is PROCESSOR_ARM920, which is correct, since our OEMInit() is
setting CEProcessorType to this value. The device is based on the
ARMv4I.**)

Last year when VS was in beta there were two MSDN Blog articles about
debugging without ActiveSync:
- http://blogs.msdn.com/vsdteam/archive/2005/01/05/347332.aspx, and
- http://blogs.msdn.com/vsdteam/archive/2005/04/28/413304.aspx

This method works for us. However, it is cumbersome in the least and
not the ideal way to debug. If anyone has any suggestions for
deploying and connecting normally they would be greatly appreciated.

Best regards,
Dan.


* This is all happening on a brand new PC running XP Pro (SP2), PB 5.0,
eVC 4.0, VS2005 and our SDK (installed in that order). (No QFE's have
been installed yet.)

** I can verify that
C:\dev\VS8\SmartDevices\SDK\CompactFramework\2.0\v2.0\WindowsCE\wce500\armv4i\NETCFv2.wce5.armv4i.cab
exists, although I don't know what CPU ID it's trying to match.
Click to expand...
Click to expand...
 
D

Dan McCarty

Interesting, I ran some diffs on the files (some of them had different
sizes), and here's what I found:

conman_ds_addonsinstalled.xsl:
<ADDONSINSTALLEDCONTAINER> contained a
"Version="$majorHigh$.$majorLow$.$minorHigh$.$minorLow$"" value that
the recreated file did not have.

conman_ds_debuggger.xsl:
<DEBUGGERCONTAINER> contained the same
"Version="$majorHigh$.$majorLow$.$minorHigh$.$minorLow$"" value that
the newly created file didn't have.

conman_ds_device.xsl:
In addition to the "version=" value, <DEVICECONTAINER> contained a lot
of GUID's that the new file didn't have. For example:

<DEVICE ID="6228C644-D184-4E53-840B-E41F28CD3594" Name="CE Device">
<PROPERTYCONTAINER>
<PROPERTY ID="Device Image" Name="Device Image">
....

conman_ds_file:
<FILECONTAINER> contained the same "version=" value.

I suspect all of these files had the same problem, though I didn't
check each one:
conman_ds_osimage.xsl
conman_ds_package.xsl
conman_ds_platform.xsl
conman_ds_property.xsl
conman_ds_servicecategory.xsl

conman_ds_typemap.xsl:
This one was the most interesting. The newly-created file was
missing about a dozen <QIS ID="16908288"> values that the old file had.
They represented different processer type properties. I saved both
files if anyone from MS is interested in troubleshooting the issue.
(Just email me.)

FWIW, this fix also worked on another developer's machine, so I'm
officially calling this the "blessed" fix.

-Dan.
I had the exactly the same problem and finally fixed this yesterday.
I can't said if this the true solution, so let me(all of us) know if it is
or not,
because I tried uninstall and re-install so many times and I think when I
reinstall PB5.0, it messed it up so bad all debug don't work including the
emulator, which it used to work.

This is the error that I got when I got trying to fix the "The bootstrp..."
problem.
"The configuration data for this product is corrupt. Contact your support
personnel."

then I find this (BUT I DON'T HAVE VS2005 BETA INSTALLED):
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=104023&SiteID=1
and all I did was delete this dir:
%userprofile%\Local Settings\Application Data\Microsoft\CoreCon\1.0 Folder
and all files under it.

then when I try the ARM Device Emulator, I got a different message, which is
because the setting to the resolution is gone. once fixed the emulator worked.
Then I uninstall my custom device SDK, then try the Windows CE 5.0 device and
it worked. then I install back the custom device SDK and use that and it
still works.

So, after all this I believe just deleting this folder is the key solution
%userprofile%\Local Settings\Application Data\Microsoft\CoreCon\1.0 Folder



Daniel McCarty said:
I'm assuming that my problem must be pretty rare, since a lot of people
use VS2005 by now and a lot of people must use it to debug managed
apps. I have a CE5.0 device running a platform built on our BSP.
We've also exported an SDK that I installed for VS2005.*

I am connected to the device via ActiveSync 4.1. When I try to debug I
choose the device I want to deploy to, and VS reports

------ Deploy started: Project: NetConfApiTest, Configuration: Debug
Any CPU ------

After a little while I get the error

The bootstrap could not be loaded.
(also see http://h1.ripway.com/dpm/Usenet/bootstrapNotFound.jpg)

There isn't much information about this error, but I did find some
Usenet articles saying that it might be related to the processor ID. I
found some sample code from Ilya Tumanov [MS] and compiled it into a
project and ran it, and it reported my ID as

2336 (0x920)

(This is PROCESSOR_ARM920, which is correct, since our OEMInit() is
setting CEProcessorType to this value. The device is based on the
ARMv4I.**)

Last year when VS was in beta there were two MSDN Blog articles about
debugging without ActiveSync:
- http://blogs.msdn.com/vsdteam/archive/2005/01/05/347332.aspx, and
- http://blogs.msdn.com/vsdteam/archive/2005/04/28/413304.aspx

This method works for us. However, it is cumbersome in the least and
not the ideal way to debug. If anyone has any suggestions for
deploying and connecting normally they would be greatly appreciated.

Best regards,
Dan.


* This is all happening on a brand new PC running XP Pro (SP2), PB 5.0,
eVC 4.0, VS2005 and our SDK (installed in that order). (No QFE's have
been installed yet.)

** I can verify that
C:\dev\VS8\SmartDevices\SDK\CompactFramework\2.0\v2.0\WindowsCE\wce500\armv4i\NETCFv2.wce5.armv4i.cab
exists, although I don't know what CPU ID it's trying to match.
Click to expand...
Click to expand...
 
X

xtrm

Joined
Apr 9, 2010
Messages
1
Reaction score
0
How to solve that fuXXXX error hehe.
After a lot of testing Ive been able to solve the error which no ones knows how to solve it.
Ive formatted hdd, reinstalled apps, changed a lot of registrys, patched system..........

SOLUTION:
Apply service pack 1 for Visual Studio 2005 OR Install Visual Studio 2008
Automatically the connection works for VS2005 and for Remote Tools (remote registry...)
[SOLVED]

-eof-
 
Top