Failed to successfully start or connect to the MSBuild.exe child process. Verify that the MSBuild.exe file

Question

The first time this happens to me.

Run the build and get this error.

When I rebuild other sln everything works fine.

Error 1 The collection unexpectedly ended due to an internal failure. Microsoft.Build.Exceptions.BuildAbortedException: The assembly has been canceled. Failed to start or connect to the child MSBuild.exe to process. Make sure that the MSBuild.exe file "C: \ Windows \ Microsoft.NET \ Framework \ v4.0.30319 \ MSBuild.exe" starts successfully, and that it loads the same microsoft.build.dll that the startup process has loaded. If the location seems to be incorrect, try specifying the correct location in the BuildParameters object or using the MSBUILD_EXE_PATH environment variable. at Microsoft.Build.BackEnd.NodeProviderOutOfProc.CreateNode (Int32 nodeId, INodePacketFactory factory, NodeConfiguration configuration) at Microsoft.Build.BackEnd.NodeManager.AttemptCreateNode (INodeProvider nodeProvider, NodeConfiguration nodeConfiguration.NodeFonfield.Ben configuration , NodeAffinityAffinity node) at Microsoft.Build.Execution.BuildManager.PerformSchedulingActions (IEnumerable`1 answers) to Microsoft.Build.Execution.BuildManager.HandleNewRequest (Int32 node, BuildRequestBlocker Blocker) submissionBuild.ExecutionItu.BueildBuildBueildBuildBuild , Boolean allowMainThreadBuild, BuildRequestBlocker blocker) D: \ MaM \ Server \ ClientServices \ Dev \ ClientService 1.4 \ Conduit.Mam.ClientServices.Common.Initizliaer \ Conduit.Mam.ClientServices.Common.Initizliaer.csproj.monitor.conspermj.monp. Initizliaer

Answer 1

Exiting and reopening Visual Studio decided for me.

Answer 2

We had the same problem this morning. This error usually appears when your system is running low on memory. If shutting down and reopening VS does not do the trick, try closing some of the other applications that are currently running. If all else fails, reboot the system.

http://blogs.msdn.com/b/paraswadehra/archive/2014/01/04/the-build-stopped-unexpectedly-because-of-an-internal-failure.aspx

Answer 3

If you tried everything in this message (reboot, reboot, etc.), nothing helps. Try running VS2012 as an administrator and see if that helps.