Trying to compile a VS 2013 C++ application and Im getting the LNK1168 cannot open .\bin\foo\bar\foobar.exe for writing.
I've followed other articles. Application Experience is enabled and running. Ive restarted VS. Cleaned and tried to rebuild. Checked the Task Mgr to make sure the application isn't running too.
My only success is after a full system reboot.
Nothing is working except the system reboot. I went to the directory and noticed that when I tried to delete the .exe that is currently there (from a previous successful build) it gives me an error saying that the operation cannot be completed because it is open in Windows Audio..
Has anybody dealt with this before? Restarting my whole OS to build is not going to work for me much longer.
The project is mapped to a D: drive (i.e. not located on C:).
We are running automated Jenkins builds on Amazon servers (Windows Server 2012 R2) for a few Visual Studio solutions. The bigger projects in them are configured with the /MP, use multi processor compilation, attempting to minimize build time.
We run msbuild with its /m flag as well.
Problem is that after a few minutes we get:
TRACKER : error TRK0002: Failed to execute command: ""C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\CL.exe" #C:\Users\Administrator\AppData\Local\Temp\tmpd19a7e5e426f4ec7baa597ed75516fd4.rsp". Not enough quota is available to process this command.
This problem occurs only when running Jenkins agent. With Visual Studio IDE everything is fine. When running MSBuild from command prompt everything is fine as well.
Any idea why that happens and we can work around it?
Running
WMIC CPU Get DeviceID,NumberOfCores,NumberOfLogicalProcessors
got
DeviceID NumberOfCores NumberOfLogicalProcessors
CPU0 2 4
Maybe VS2015 does not detect the number of effective processors correctly and crosses some process boundary of spawning too many processes concurrently?
Any help would be greatly appreciated.
The problem was a quota was defined in WinRM as denoted here: https://msdn.microsoft.com/en-us/library/ee309367(v=vs.85).aspx
We changed the value of MaxProcessesPerShell to be higher than the default of 25 and voila.
The facile answer from technet to "create more virtual memory" is actually probably worth a bash.
Jenkins, at the time it launches MSBuild appears to use Runtime.exec() (checkout Launcher.java if you're having a look at their code).
This typically creates a new process, that, at least initially, has the same memory footprint as the launching process. So for a bit of time you're probably running twice as much memory as necessary for the build process. So having some more virtual memory available at launch time may be enough to allow the new process to run long enough for the launching process to finish and free.
Here's Technet's cough useful description of the error message: https://technet.microsoft.com/en-us/library/cc958981.aspx
I am trying to profile a Web application(Debug->Start Diagnostic Tool without Debugging) but every time it is failing with below message. Solution is set in release mode. After start profiling IE is opening with a URL http://localhost:19394/ but getting 'Page cannot be displayed'.
Warning VSP2013: Instrumenting this image requires it to run as a 32-bit process. The CLR header flags have been updated to reflect this.
Launching web server with profiling.
Launching profilable project.
Data written to C:\Project\Report150826(1).vsp.
Profiling finished.
File contains no data buffers
File contains no data buffers
Analysis failed
Profiling complete.
I am using VS 2015 Enterprise RTM and it is running under administrator privileges.
Tried to uninstall Visual studio using the command line "C:\Setups\Visual Studio\VS 2015\vs2015.ent_enu\vs_enterprise.exe" /uninstall /force but uninstall also failing with error message:
Update for Microsoft Windows (KB2999226) : The storage control blocks were destroyed.
I have been trying to run a script to generate a mandelbrot image using matplotlib however I am getting a very peculiar error. I am running the script through IDLE, running it for the first time does nothing but running it again after that brings up a window that says:
"Runtime error!
Program: C:\Python27\pythonw.exe
This application has requested the Runtime to terminate it in an unusual way."
The name of the window that pops up is Microsoft Visual C++ Runtime Library
I have previously gotten errors about pythonw when trying to run image related stuff, usually the plot will stop responding and a message displays "pythonw.exe has stopped working".
I have searched high and low for a solution to this and google shows a few people having similar problems but no one replying to their posts.
I have also tried installing microsoft visual x64 C++ 2010 redistributed package but that aborted stating that there was a more up to date version present
interestingly looking through windows update history shows some failed security updates for microsoft visual C++ 2008 that did later install. (don't know if thats relavent)
Running windows 7 64 bit and python 2.7
Was wondering if anyone had any ideas as to what was going on and how to fix it because I sure don't
Thanks in advance!
When compiling any C++ project with visual studio 2010 express I'm liable to get following behaviour - build started message appears in output window, CPU climbs to near 100%, multiple MSBuild.exe processes are spawned, long pause (several minutes) with nothing happening, build aborts with the following message
xxx.vcxproj : error MSB4014: The build stopped unexpectedly because of an internal failure.
xxx.vcxproj : error MSB4014: Microsoft.Build.Exceptions.BuildAbortedException: Build was canceled. MSBuild.exe could not be launched as a child node as it could not be found at the location "c:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe". If necessary, specify the correct location in the BuildParameters, or with the MSBUILD_EXE_PATH environment variable.
xxx.vcxproj : error MSB4014: at Microsoft.Build.BackEnd.NodeManager.AttemptCreateNode(INodeProvider nodeProvider, NodeConfiguration nodeConfiguration)
xxx.vcxproj : error MSB4014: at Microsoft.Build.BackEnd.NodeManager.CreateNode(NodeConfiguration configuration, NodeAffinity nodeAffinity)
xxx.vcxproj : error MSB4014: at Microsoft.Build.Execution.BuildManager.PerformSchedulingActions(IEnumerable`1 responses)
xxx.vcxproj : error MSB4014: at Microsoft.Build.Execution.BuildManager.HandleNewRequest(Int32 node, BuildRequestBlocker blocker)
xxx.vcxproj : error MSB4014: at Microsoft.Build.Execution.BuildManager.IssueRequestToScheduler(BuildSubmission submission, Boolean allowMainThreadBuild, BuildRequestBlocker blocker)
Microsoft have acknowledged a bug with this behaviour when your user name is 20 chars, but mine is much shorter. And needless to say I do have msbuild.exe in the right place.
The only work around I've found is to task switch to another app while the build is taking place. But I'm hoping someone has a better workaround.
MTIA
John
You've already eliminated KB2298853. Do make sure to install SP1. It is not the only reason, some other users have this problem too, even after the workaround. The basic failure appears to be a problem creating a pipe that lets msbuild talk to the IDE. Which is why it doesn't fail when you run msbuild from the command line.
This is an environmental problem, as yet undiagnosed. You need to chase down the reason the execution environment is unusual on your machine. Do so by selectively disabling or killing processes. Start with your malware software. Also, start another instance of Visual Studio and use Tools + Attach to Process to attach an unmanaged debugger to the first instance and/or msbuild. Debug + Break All and use Debug + Windows + Modules to find out what DLL might be injected in the process that is not made by Microsoft. Pay attention to the Path column. Not sure if Attach to Process is available on the Express edition btw.
it's actually just the behavior shield in avast that is causing the problems with visual studio.
if you turn that off when trying to build, it will build and run. now we just need either microsoft or avast to create an update which will eliminate this problem. just discovered this 10 mins ago. at 2:50 pm 12/3/2011 central standard time in wisconsin
I can confirm that this problem was also solved for me by turning off Avast's behavior shield. Something is definitely not right with that. Endless MSBuild.exe (and conime.exe) processes and devenv.exe maxing out the CPU. Seems to be a real system killer there by Avast. :-(
In my case simply restarting VS2010 helped fix the error. Anyone encountering this error might want to try that first.
(I am using VS 2010 with SP1)