There was an error checking. HRESULT = '8000000A'

Question

I get this error for a while while using devenv in automatic build. I went through every site that I can find, and the usual answers mention updated dependencies (which I believe fix it for manual deployment, but not automatic) and removing the source control code from projects, which did not help me.

The error does not occur at every creation, but each time it seems random in different deployment projects.

Does anyone have any advice on why this particular error occurs and how to fix it?

Answer 1

This is a known issue in Visual Studio 2010 (race condition). See This Connection Element .

We ran into this, and we had a very unsatisfactory call on this issue with Microsoft. In short: this is a known issue, it will not be resolved, and Microsoft advises abandoning Visual Studio installation projects (.vdproj).

We worked on this issue by initiating the MSI build for the second time when it does not fire the first time. Not good, but it works most of the time (error rate decreases from ~ 10% to ~ 1%).

Answer 2

An update for those who received this issue for VS2013 or VS2015 after updating the VS200X installation project using the Microsoft Project Studio development extension.

After the recipe for v1.0.0.0 from MS, it finally worked for me:

Microsoft Visual Studio Installer Projects

Unfortunately, we were not able to resolve all cases of command line problems for this version, as we are still investigating the appropriate way to resolve them. We have a workaround, which, in our opinion, will work for almost everyone. If you still suffer from this problem, you can try changing the DWORD value for the following registry value: 0: HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0_Config\MSBuild\EnableOutOfProcBuild (VS2013)
or
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\14.0_Config\MSBuild\EnableOutOfProcBuild (VS2015)
If this does not exist, you can create it as a DWORD.

Answer 3

I read somewhere on the Internet about this, and I fixed it like this (it was suggested by someone):

• open the installation project file (.vdproj) in notepad (or any other text editor).

• delete these lines at the beginning of the .vdproj file:

   "SccProjectName" = "8:" "SccLocalPath" = "8:" "SccAuxPath" = "8:" "SccProvider" = "8:" 

• build again - the error is gone

This error did not stop me from deploying, building, debugging (or changing) my project, it just annoyed me. And this happened even if I installed all the projects that will be built in the current configuration, but the installation project does not.

Answer 4

Update as of June 14, 2012

The Microsoft Visual Studio 2017 Installer Projects extension now includes a command-line tool to simplify the installation of the registry setting for Microsoft Visual Studio 2017 Installer Projects applications

Examples of tool paths (based on the installed version of Visual Studio)

Professional version: C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\CommonExtensions\Microsoft\VSI\DisableOutOfProcBuild\DisableOutOfProcBuild.exe

Community Edition: C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\VSI\DisableOutOfProcBuild\DisableOutOfProcBuild.exe

From README

---

This simple tool is designed to help users install the registry key needed to work around this error, which may appear when creating installer projects using the command line:

ERROR: An error occurred during validation. HRESULT = '8000000A'

This tool is for Visual Studio 2017+ and sets this registry key for a specific installed instance of Visual Studio for the current user. Therefore, if you install this in the assembly agent, be sure to use the user account that the assembly will use.

For usage information, run "DisableOutOfProcBuild.exe help".

---

Answer 5

Permanent solution (+ for assembly machines)

Visual studio 2017

For VS 2017, call the following CMD scripts under your target Windows account:

Public Edition
Professional Edition
Corporate Edition

TL; DR. Notes for the bad DisableOutOfProcBuild.exe , Microsoft has proposed a solution that I use for VS 2017.

1. DisableOutOfProcBuild.exe does not assume that you DisableOutOfProcBuild.exe it from the installation folder . Therefore, you cannot copy this .exe file. (By the way, if you want to build .vdproj, you have to install VS.)
2. DisableOutOfProcBuild.exe will work only if the installation directory DisableOutOfProcBuild.exe is specified in the current CMD directory.

For example, for VS Professional Edition we should call

 CD "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\CommonExtensions\Microsoft\VSI\DisableOutOfProcBuild" CALL DisableOutOfProcBuild.exe 

Visual Studio 2015 and earlier

CMD for the current Windows user

For many people, creating / fixing in HKEY_CURRENT_USER\.. does not always work or works all the time.
Trying to solve this problem, I found that I actually need to create / modify some strange key in HKEY_USERS HKEY_USERS\S-1-5-xx-xxxxxxxxxx-xxxxxxxxx-xxxxxxxxxxx-xxxxx\...\MSBuild

But I also found that if I use the CMD console for HKCU with the proposed fix
REG ADD HKCU\SOFTWARE\Microsoft\VisualStudio\14.0_Config\MSBuild/t REG_DWORD/v EnableOutOfProcBuild/d 0/f
this will write the value to this strange key HKEY_USERS \ S-1-5-xx-xxxxxxxxxx-xx ... , and not to HKEY_CURRENT_USER .

So, it works the first time and forever. Just use the CMD console.

 REG ADD HKCU\SOFTWARE\Microsoft\VisualStudio\14.0_Config\MSBuild /t REG_DWORD /v EnableOutOfProcBuild /d 0 /f @REM (use 12.0_Config for VS2013) 

Solver for build servers

On the other hand, this code always works for the current user account that runs it (due to HKEY_CURRENT_USER). But build servers often use dedicated accounts or a local system, etc.

I fixed this on my build machines by adding the following simple batch file to my build tasks (Jenkins, TeamCity, CruiseControl)

VS-2015 , VS-2013 , VS-2017-Community , VS-2017-Professional , VS-2017-Enterprise

Answer 6

As indicated in the comments here , for VS2017 you will need to create a DWORD HKEY_CURRENT_USER \ Software \ Microsoft \ VisualStudio \ 15.0_ [IDKey] _Config \ MSBuild \ EnableOutOfProcBuild Replace [IDKey] with the ID suffix of the existing Visual Studio 15.0 subkey.

For example, if you see the key "15.0_abcd1234" in VisualStudio, it will be "15.0_abcd1234_Config".

Answer 7

The fix now downloads here:

http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=33186

You can read about it here:

http://connect.microsoft.com/VisualStudio/feedback/details/595632/inconsistent-hanging-with-devenv-2010

Answer 8

I ran into this problem after I transferred my project to another computer (VS 2010, several projects in solution).

I already built my project on the source computer, but after I copied it, I could not create my installation project and get this error.

I opened the /Debug folder in the root path of my installation project, there were MyProject.msi and setup.exe files, I deleted them and built my project again, it worked. Hope this works for some guys too.

Answer 9

Checking for project dependencies may help.

In VS 2010, right-click in your solution browser, then select “Detectable Dependencies” and “Dependent Updates”, it sometimes fixes the problem.

Answer 10

I am using VS 2017, but none of the above solutions work. So, the updated version of VS 2017 and the @AussieAsh solution work fine ...

I hope this solution can someone work.

Answer 11

with me it was caused by the wrong .suo file. (caused by skydrive) deleting this file solved the problem.

Answer 12

Visual Studio 2017 stores information previously stored in the public registry in a new private registry: C: \ Users \\ AppData \ Local \ Microsoft \ VisualStudio \ 15.0_6de65198 \ privateregistry.bin

Here you need to add EnableOutOfProcBuild according to the instructions for VS2013 / VS2015.

To update a private registry, you can use Regedit.

Click to select HKEY_USERS node.

Choose File> Download Hive and go to the privateregistry.bin file. When you select it, Regedit will ask for a name - no matter how you call it, how we will do it soon.

Now the registry structure will appear, and you can go down to Microsoft \ VisualStudio \ 15.0_Config \ MSBuild

Create a new DWORD EnableOutOfProcBuild with a value of 0.

After that, select the root of the hive (regardless of what you named earlier) and use File> Unload Hive to disconnect from it.

Now it should work: o)

Answer 13

My Visual Studio 2013 somehow became experimental, so she started using a different registry key for EnableOutOfProcBuild

Of course, I just added another line to my batch file to set the registry value and started working:

 REG ADD HKCU\SOFTWARE\Microsoft\VisualStudio\12.0_Config\MSBuild /t REG_DWORD /v EnableOutOfProcBuild /d 0 /f REG ADD HKCU\SOFTWARE\Microsoft\VisualStudio\12.0Exp_Config\MSBuild /t REG_DWORD /v EnableOutOfProcBuild /d 0 /f 

Answer 14

Just run this exe

(Visual Studio 2017 Community Edition)

C: \ Program Files (x86) \ Microsoft Visual Studio \ 2017 \ Community \ Common7 \ IDE \ CommonExtensions \ Microsoft \ VSI \ DisableOutOfProcBuild \ DisableOutOfProcBuild.exe

(Visual Studio 2017 Enterprise edition)

C: \ Program Files (x86) \ Microsoft Visual Studio \ 2017 \ Enterprise \ Common7 \ IDE \ CommonExtensions \ Microsoft \ VSI \ DisableOutOfProcBuild \ DisableOutOfProcBuild.exe

Answer 15

If this problem occurred today, try restarting Visual Studio, if it does not create a new project, save it, and then copy the files from the problem project. both methods worked for me.

Answer 16

First clear the solution, create the solution and try creating the installer. It will remove the error.