An Error occurred generating a bootstrapper

Question

I am using a fresh install of Visual Studio 2010 Premium.

Last week, I was able to Publish my project including the setup.exe for prerequisites

Monday, I upgraded the Target Framework of my application to 4.0 (From 3.5SP1)

No problems were detected and I was still able to build and launch the application from within Visual Studio.

Today I tried to publish a new version of my solution.  It doesn't work if I try to have the publishing include a setup.exe to distribute prerequisite files.

I closed everything, rebooted, and created a blank project (windows form) Net 4.0.

If I try to publish it, it works unless i check "Create setup program to install prerequisite components". In that case I get the following error.

Error 2 An error occurred generating a bootstrapper: Unable to begin updating resource for bin\Debug\app.publish\setup.exe with error 80070002 TESTPUBLISH

My OS is Windows 7 x64.

Anyone has any idea what is going on ?

ETA:

I uninstalled VS2010 from my computer and reinstalled a fresh copy... Same error.  On another machine I have, same version of VS2010, same operating system, no problems.... 

 

---

MCAD 2005

Answer 1

Hi Fred,

 

> If I try to publish it, it works unless i check "Create setup program to install prerequisite components". In that case I get the following error.

 

Check the “Create setup program to install prerequisite components” will cause error or Uncheck it will cause error?

 

Sincerely,

Kira Qian

MSDN Subscriber Support in Forum

If you have any feedback on our support, please contact [e-mail]

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework!

Answer 2

Checking the Create setup program to install prerequisite components CAUSES the error

---

MCAD 2005

Answer 3

Hi Fred,

 

Could you please try to copy all the bootstrapper pacakge from other computer and replace the same in the problem computer? I think some of the bootstrapper might be corrupted. If that doesn’t work, the problem might be in the bootstrapper generator which unable to package the prerequisite into msi.

 

Please try it and inform me your result.

 

Sincerely,

Kira Qian

MSDN Subscriber Support in Forum

If you have any feedback on our support, please contact [e-mail]

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework!

Answer 4

I tried what you suggested, replacing all the packages from the good machine to the bad  machine.

Didnt change the problem, still same error.

Here is a screen capture i get...

The error message

The Prerequisite Window

 

 

 

---

MCAD 2005

Answer 5

Hi, The prerequisite packages are corrupted now. I would suggest to uncheck the prerequisite option. Build the project in visual studio

Next time go ahead and click on prerequisite see if those Yellow warnings still show up on Prerequisite packages

If that is the case select the third option Under Specify the Download location

Provide UNC path of the package and try publish your project

 

---

bill boyce

Answer 6

As soon as i try to publish with the Prerequisites Option Selected, regardless if i choose any of the 3 location options, i get the same 2 errors (as shown in my previous message.)

 

If you think the problem is with the YELLOW WARNING SIGNS, is there a way to fix this first...

 

And you are right I have no problems publishing if i dont select the prerequisite options.

---

MCAD 2005

Answer 7

I am having the same error messages with the same configuration. The Prerequisites on my system, however, are not corrupted (no yellow warning signs)

 

Any other ideas?

Answer 8

Hi,

 

Please review this to see if it helps you out.

 

http://download.microsoft.com/download/A/2/8/A2807F78-C861-4B66-9B31-9205C3F22252/VS2008SP1Readme.htm

2.3.1.1 Enable Samesite for the .NET Framework 3.5 SP1 bootstrapper package

If the .NET Framework 3.5 SP1 bootstrapper package is selected in the Prerequisite dialog box for a Setup project or in ClickOnce publishing, and also the "Download prerequisites from the same location as my application" option is selected, the following build error is shown: 

The install location for prerequisites has not been set to 'component vendor's web site' and the file 'dotNetFx35setup.exe' in item 'Microsoft.Net.Framework.3.5.SP1' cannot be located on disk.

To resolve this issue:

Update the Package Data

1. Open the [Program Files]\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 folder or %ProgramFiles(x86)%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 on x64 operating systems
2. Edit the Product.xml file in Notepad.
3. Paste the following into the < PackageFiles > element:
   <PackageFile Name="TOOLS\clwireg.exe"/>
   <PackageFile Name="TOOLS\clwireg_x64.exe"/>
   <PackageFile Name="TOOLS\clwireg_ia64.exe"/>
4. Find the element for < PackageFile Name="dotNetFX30\XPSEPSC-x86-en-US.exe" and change the PublicKey value to: 3082010A0282010100A2DB0A8DCFC2C1499BCDAA3A34AD23596BDB6CBE2122B794C8EAAEBFC6D526C232118BBCDA5D2CFB36561E152BAE8F0DDD14A36E284C7F163F41AC8D40B146880DD98194AD9706D05744765CEAF1FC0EE27F74A333CB74E5EFE361A17E03B745FFD53E12D5B0CA5E0DD07BF2B7130DFC606A2885758CB7ADBC85E817B490BEF516B6625DED11DF3AEE215B8BAF8073C345E3958977609BE7AD77C1378D33142F13DB62C9AE1AA94F9867ADD420393071E08D6746E2C61CF40D5074412FE805246A216B49B092C4B239C742A56D5C184AAB8FD78E833E780A47D8A4B28423C3E2F27B66B14A74BD26414B9C6114604E30C882F3D00B707CEE554D77D2085576810203010001
5. Find the element for < PackageFile Name="dotNetFX30\XPSEPSC-amd64-en-US.exe" and change the PublicKey value to the same as in step 4 above
6. Save the product.xml file

 

Download and Extract the Core Installation Files

1. Navigate to the following URL: http://go.microsoft.com/fwlink?LinkID=118080
2. Download the dotNetFx35.exe file to your local disk.
3. Open a Command Prompt window and change to the directory to which you downloaded dotNetFx35.exe.
4. At the command prompt, type:
   dotNetFx35.exe /x:.
   This will extract the Framework files to a folder named “WCU” in the current directory.
5. Copy the contents of the WCU\dotNetFramework folder and paste them in the %Program Files%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 folder (%ProgramFiles(x86)%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 on x64 operating systems). Note: Do not copy the WCU\dotNetFramework folder itself. There should be 5 folders under the WCU folder, and each of these should now appear in the DotNetFx35SP1 folder. The folder structure should resemble the following:
   o DotNetFx35SP1 (folder)
   • dotNetFX20 (folder
   • dotNetFX30 (folder)
   • dotNetFX35 (folder)
   • dotNetMSP (folder)
   • TOOLS folder)
   • en (or some other localized folder)
   • dotNetFx35setup.exe (file)

You may now delete the files and folders you downloaded and extracted in steps 2 and 4.

---

bill boyce

Answer 9

Thanks for suggestion. This did not work for me.

My problem is similar (likely the same) as discussed in here: http://social.msdn.microsoft.com/Forums/en-US/winformssetup/thread/e81d47d9-5df6-49b9-84b4-7bdbe77d3eaa

This is quite frustrating. Anyone?!?!?!

 

Answer 10

Hi,

 

You may want to check out and post here _http://code.msdn.microsoft.com/bmg/

from my checks with collegues this would take some time to determine.

There are various support options such as advisory and per issue. Please visit the below link to see the various paid support options that are available to better meet your needs. http://support.microsoft.com/default.aspx?id=fh;en-us;offerprophone

---

bill boyce

Answer 11

If you have installed SP1 for Visual Studio 2010,

Removing these elements from file

"c:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages\DotNetFX35SP1\product.xml" 

will help you

<PackageFile Name="dotNetMSP\x86\NetFX2.0-KB936704-v6000-x86_RTM_en.msu" PublicKey="3082010A0282010100AE8031675AF17A3E33678126CD966AB250FBD794AE62641514408099F8AF3F00CFCBD99CED0F8AE3C53D06C8B0016AAD2A7F5ED3CC6B582E76D72D36C803DC67205C70848F5DA797853D419FCE61356EA906252B525C43E8D46D5FECA28408A2737902BB102CF8316E6853B277F6BAAC96442BAD2CBBBE378FC3F0D20FAE4CB51054B0AD5E0CB811A4BDCC9C86409BE730C3D7A89A8E03B52D71E90BFBA7299C7CA61DB524619FDEC764EC9FD80BD18387BEF57A1D2D9D8828298003058426AE37356C7E4D6F052578409EF41D73C3DC7F7870F57E7BE281ACB7590B1315AEECF20D7BF1709614B3419CC875894F1B37787D11BAD2E4C61EE351091A2FD1BFF50203010001" />

        <PackageFile Name="dotNetMSP\x86\NetFX2.0-KB948609-v6001-x86.msu" PublicKey="3082010A0282010100AEAB00C051B5892274F899E0795867C715C1634C7F315ECA4A5D680FD967AE2D560FA01099A9D17793272DA2645679DAF26CEF6E09CD6926F1EF0A13E9DE2E22680D15BD0345E532D0009CACE2EEA6AE4A3EDB2CFD525EEF23B835B2ADA53AE9F111764BBF8ABCC81A9F81E1C85CF79DB9A85AA8F0E00E667728C5694F7C2B57826740CC812404D325FC4573157CFD8544020941A433C2EFC90FA249A4E2AA891ED21852E7708B66CDF94C2EEFABFB84DA62BFB18663E18443C5AD1ED23A0E9DE5F362BFD813670228E8B125E990C8CF55C2F19BC02B2666B7FBE1C69F9C56BDB56C6E570B0EF137AA10D8A4DD463D3323C8FF289DB07551F375D821A6C563C50203010001" />

        <PackageFile Name="dotNetMSP\x86\NetFX3.0-KB936705-v6000-x86_RTM_en.msu" PublicKey="3082010A0282010100AE8031675AF17A3E33678126CD966AB250FBD794AE62641514408099F8AF3F00CFCBD99CED0F8AE3C53D06C8B0016AAD2A7F5ED3CC6B582E76D72D36C803DC67205C70848F5DA797853D419FCE61356EA906252B525C43E8D46D5FECA28408A2737902BB102CF8316E6853B277F6BAAC96442BAD2CBBBE378FC3F0D20FAE4CB51054B0AD5E0CB811A4BDCC9C86409BE730C3D7A89A8E03B52D71E90BFBA7299C7CA61DB524619FDEC764EC9FD80BD18387BEF57A1D2D9D8828298003058426AE37356C7E4D6F052578409EF41D73C3DC7F7870F57E7BE281ACB7590B1315AEECF20D7BF1709614B3419CC875894F1B37787D11BAD2E4C61EE351091A2FD1BFF50203010001" />

        <PackageFile Name="dotNetMSP\x86\NetFX3.0-KB948610-v6001-x86.msu" PublicKey="3082010A0282010100AEAB00C051B5892274F899E0795867C715C1634C7F315ECA4A5D680FD967AE2D560FA01099A9D17793272DA2645679DAF26CEF6E09CD6926F1EF0A13E9DE2E22680D15BD0345E532D0009CACE2EEA6AE4A3EDB2CFD525EEF23B835B2ADA53AE9F111764BBF8ABCC81A9F81E1C85CF79DB9A85AA8F0E00E667728C5694F7C2B57826740CC812404D325FC4573157CFD8544020941A433C2EFC90FA249A4E2AA891ED21852E7708B66CDF94C2EEFABFB84DA62BFB18663E18443C5AD1ED23A0E9DE5F362BFD813670228E8B125E990C8CF55C2F19BC02B2666B7FBE1C69F9C56BDB56C6E570B0EF137AA10D8A4DD463D3323C8FF289DB07551F375D821A6C563C50203010001" />

        <PackageFile Name="dotNetMSP\x64\NetFX2.0-KB936704-v6000-x64_RTM_en.msu" PublicKey="3082010A0282010100AE8031675AF17A3E33678126CD966AB250FBD794AE62641514408099F8AF3F00CFCBD99CED0F8AE3C53D06C8B0016AAD2A7F5ED3CC6B582E76D72D36C803DC67205C70848F5DA797853D419FCE61356EA906252B525C43E8D46D5FECA28408A2737902BB102CF8316E6853B277F6BAAC96442BAD2CBBBE378FC3F0D20FAE4CB51054B0AD5E0CB811A4BDCC9C86409BE730C3D7A89A8E03B52D71E90BFBA7299C7CA61DB524619FDEC764EC9FD80BD18387BEF57A1D2D9D8828298003058426AE37356C7E4D6F052578409EF41D73C3DC7F7870F57E7BE281ACB7590B1315AEECF20D7BF1709614B3419CC875894F1B37787D11BAD2E4C61EE351091A2FD1BFF50203010001" />

        <PackageFile Name="dotNetMSP\x64\NetFX2.0-KB948609-v6001-x64.msu" PublicKey="3082010A0282010100AEAB00C051B5892274F899E0795867C715C1634C7F315ECA4A5D680FD967AE2D560FA01099A9D17793272DA2645679DAF26CEF6E09CD6926F1EF0A13E9DE2E22680D15BD0345E532D0009CACE2EEA6AE4A3EDB2CFD525EEF23B835B2ADA53AE9F111764BBF8ABCC81A9F81E1C85CF79DB9A85AA8F0E00E667728C5694F7C2B57826740CC812404D325FC4573157CFD8544020941A433C2EFC90FA249A4E2AA891ED21852E7708B66CDF94C2EEFABFB84DA62BFB18663E18443C5AD1ED23A0E9DE5F362BFD813670228E8B125E990C8CF55C2F19BC02B2666B7FBE1C69F9C56BDB56C6E570B0EF137AA10D8A4DD463D3323C8FF289DB07551F375D821A6C563C50203010001" />

        <PackageFile Name="dotNetMSP\x64\NetFX3.0-KB936705-v6000-x64_RTM_en.msu" PublicKey="3082010A0282010100AE8031675AF17A3E33678126CD966AB250FBD794AE62641514408099F8AF3F00CFCBD99CED0F8AE3C53D06C8B0016AAD2A7F5ED3CC6B582E76D72D36C803DC67205C70848F5DA797853D419FCE61356EA906252B525C43E8D46D5FECA28408A2737902BB102CF8316E6853B277F6BAAC96442BAD2CBBBE378FC3F0D20FAE4CB51054B0AD5E0CB811A4BDCC9C86409BE730C3D7A89A8E03B52D71E90BFBA7299C7CA61DB524619FDEC764EC9FD80BD18387BEF57A1D2D9D8828298003058426AE37356C7E4D6F052578409EF41D73C3DC7F7870F57E7BE281ACB7590B1315AEECF20D7BF1709614B3419CC875894F1B37787D11BAD2E4C61EE351091A2FD1BFF50203010001" />

        <PackageFile Name="dotNetMSP\x64\NetFX3.0-KB948610-v6001-x64.msu" PublicKey="3082010A0282010100AEAB00C051B5892274F899E0795867C715C1634C7F315ECA4A5D680FD967AE2D560FA01099A9D17793272DA2645679DAF26CEF6E09CD6926F1EF0A13E9DE2E22680D15BD0345E532D0009CACE2EEA6AE4A3EDB2CFD525EEF23B835B2ADA53AE9F111764BBF8ABCC81A9F81E1C85CF79DB9A85AA8F0E00E667728C5694F7C2B57826740CC812404D325FC4573157CFD8544020941A433C2EFC90FA249A4E2AA891ED21852E7708B66CDF94C2EEFABFB84DA62BFB18663E18443C5AD1ED23A0E9DE5F362BFD813670228E8B125E990C8CF55C2F19BC02B2666B7FBE1C69F9C56BDB56C6E570B0EF137AA10D8A4DD463D3323C8FF289DB07551F375D821A6C563C50203010001" />

Answer 12

Were you able to solve the problem?

Answer 13

Error Message:

Error 2 An error occurred generating a bootstrapper: Unable to begin updating resource for bin\Release\app.publish\setup.exe with error 80070002 

-----------------------------------------------------------------------------------------------------------------------------------------------------

Able to resolve  the issue after deleting Bin & Obj from the project folder.

 

Regards

Keshav

Answer 14

Thank you, Keshav.  Deleting the bin and obj folders from the project folder allowed me to resolve my error (identical to the screenshot above).

Answer 15

My 2 cents here.

During a regular day of work, all the sudden I started having the abiove problem

Error 2 An error occurred generating a bootstrapper: Unable to begin updating resource for bin\Debug\app.publish\setup.exe with error 80070002 TESTPUBLISH

I tried all the workarounds suggested in this discussion but did not have any success.

Then I remembered that I started having the issue after I installed Test Track Pro with the Visual Studio 2010 add-ins.

After uninstalling Test Track Pro the problem did go immediatelly away.

Not sure why but seems like that was causing the problem.

Thanks,

Gabriele

Answer 16

I just ran into this problem out of the blue.  I had not installed anything new and the project built just fine days before.  I found that I had mistakenly started VS without running as Administrator.  Once I restarted it as Admin, everything was normal and the project published as expected.  I hope this helps someone out.

Regards,

Lee

---

Lee

Answer 17

I have the same scenario, after uninstalling Test Track Pro with the VS 2010 add-in, it works again.

Thanks,

Henry

Answer 18

Thanks

It workd for me

Answer 19

It worked! Thank you heeTop!

From control panels, I uninstalled ONLY the TestTrack plugin (to Visual Studio).

This deployment error has plagued me for months. I've scoured the net, and I tried so many (many) unsuccessful fixes.

It is finally fixed.

Thanks again!

---

Veni Vidi Giocavono X-Box

Answer 20

Error Message:

Error 2 An error occurred generating a bootstrapper: Unable to begin updating resource for bin\Release\app.publish\setup.exe with error 80070002 

-----------------------------------------------------------------------------------------------------------------------------------------------------

Able to resolve  the issue after deleting Bin & Obj from the project folder.

Regards

Keshav

My problem was caused by Updating my MS SQL 2008 R2 instalation with 2008 R2 Service pack 1 and then again, updating with MS SQL 2012.

Deleting the Bin and Obj folders from the project folder also fixed my problem!

Just remember to close and save your project before deleting those folders or you will get an error.

Answer 21

Same problem here, minimal successful solution:

- close VS 2010

- delete offending file here setup.exe (not necessary to delete folder tree)

- op vs, open project, rebuild project, and then publish

note to MS: if setup.exe is deleted w/o closing vs first and immediately try to publish: VS complains about tons of "access denied" for all kinds of files (that otherwise never occur <- so I guess MS-bug).

---

If you don't dig, you won't find it

Answer 22

This one the only solution that helped me, I don't know why this is causing an error, I just Uncheck it and it was pretty much all.

Thanks