Failed to successfully launch or connect to a child MSBuild.exe process. Verify that the MSBuild.exe

First time this happens to me.

Ran the build and got this error.

When I rebuild other sln all works fine.

> Error 1 The build stopped unexpectedly because of an internal failure. > Microsoft.Build.Exceptions.BuildAbortedException: Build was canceled. > Failed to successfully launch or connect to a child MSBuild.exe > process. Verify that the MSBuild.exe > "C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe" launches > successfully, and that it is loading the same microsoft.build.dll that > the launching process loaded. If the location seems incorrect, try > specifying the correct location in the BuildParameters object, or with > 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) at > Microsoft.Build.BackEnd.NodeManager.CreateNode(NodeConfiguration > configuration, NodeAffinity nodeAffinity) at > Microsoft.Build.Execution.BuildManager.PerformSchedulingActions(IEnumerable`1 > responses) at > Microsoft.Build.Execution.BuildManager.HandleNewRequest(Int32 node, > BuildRequestBlocker blocker) at > Microsoft.Build.Execution.BuildManager.IssueRequestToScheduler(BuildSubmission > submission, Boolean allowMainThreadBuild, BuildRequestBlocker > blocker) D:\MaM\Server\ClientServices\Dev\ClientService > 1.4\Conduit.Mam.ClientServices.Common.Initizliaer\Conduit.Mam.ClientServices.Common.Initizliaer.csproj Conduit.Mam.ClientServices.Common.Initizliaer

Quitting and re-opening Visual Studio solved it for me.

Just had the same issue this morning. This error usually appears when your system is running low on memory. If quitting and re-opening VS doesn't do the trick, try closing some of the other applications that are currently running. If all else fails try restarting your system.

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

If you have tried everything in this post (restart, reboot, etc.) and nothing helps. Try Running VS2012 as Administrator and see if that helps.