Project : error PRJ0003 : Error spawning 'cmd.exe'.

Hot Topic

convert .net 2002 project to .net 2003 environment, there are some puzzled errors!
Microsoft Visual C++ Runtime Library error question
I am use visual c++ about 3 years. I found MFC is hard to learn. I want to return to pure c++. Is anybody likes as me?
load a COM dll dynamially
How do I distribute Visual Studio 2005 apps?
implementaion of unwinding
Linking problems using Visual Studio.net 2003
Misunderstanding something about pointers?
HOW DO WE GET CONSOLE INPUT USING getch()
Unmatched braces in preprocessor

Visual C++

IAddrBook::Address mapi problem
Linking the microsoft platform SDK to VS 2005 express
Please Help me Out From a Run Time Error
VS2005 porting issue
unable to add any item to the toolbox
build doesn't link
help! vs 2005 runtime lib
Question about "RUNTIME_CLASS"
Error D2022 on build of project on network drive
Tips for speeding up debugging (stepping through code)?

Project : error PRJ0003 : Error spawning 'cmd.exe'.

When i compile a project MFC (Visual studio 2005) with the default setting, Ihave this error message but my .exe is done and work.

Build Log
    
Build started: Project: SuperviseurGesma, Configuration: Debug|Win32
Command Lines
    
Creating temporary file "d:\Gesma2005\SuperviseurGesma\SuperviseurGesma\Debug\RSP00001A24003812.rsp" with contents
[
/out:.\Debug\SuperviseurGesma.exe.embed.manifest /notify_update /manifest

.\Debug\SuperviseurGesma.exe.intermediate.manifest
]
Creating command line "mt.exe @d:\Gesma2005\SuperviseurGesma\SuperviseurGesma\Debug\RSP00001A24003812.rsp /nologo"
Creating temporary file "d:\Gesma2005\SuperviseurGesma\SuperviseurGesma\Debug\BAT00001B24003812.bat" with contents
[
@echo Manifest resource last updated at %TIME% on %DATE% > .\Debug\mt.dep
]
Creating command line "d:\Gesma2005\SuperviseurGesma\SuperviseurGesma\Debug\BAT00001B24003812.bat"
Output Window
    
Embedding manifest...
Project : error PRJ0003 : Error spawning 'cmd.exe'.
Results
    
Build log was saved at "file://d:\Gesma2005\SuperviseurGesma\SuperviseurGesma\Debug\BuildLog.htm"
SuperviseurGesma - 1 error(s), 0 warning(s)



Answer this question

Project : error PRJ0003 : Error spawning 'cmd.exe'.

  • Barb M

    I have a big problem, I'm working with opengl libraries and when I compile the system saw many errors

    1>Project : error PRJ0003 : Error spawning 'cmd.exe'.



    Spintz wrote:

    FYI, this problem arose for me after installing MSXML 4.2 SP2 SDK. It seems that installer not just added paths to the executable list in VC++ Directories, but actually removed paths as well( as the "$(SystemRoot)\system32" used to be there, then after the install, it was gone....and it's added SySWow64 in it's place, which doesn't make sense, as I'm not running x64 Windows XP and don't even have that directory on my machine.



  • werner5

    Yes it worked..

    Thanks.

  • mohan kalyan

    I'm seeing the exact same problem as the parent message, and I've already made sure that the path to cmd.exe is in VC++ Directories list. Any other ideas

  • Paul E.



    This Worked for me

    thanks..

  • djflanger

  • DaveGoliath

    This fixed the problem I was having too.

    I would like to point out to other complete noobs like myself however that if
    $(SystemRoot)
    $(SystemRoot)\System32
    $(SystemRoot)\System32\wbem

    are not in your 'Show directories for: Executable files' list in your Tools > Options > Projects and Solutions > VC++ Directories tab you have to ADD them to the list and then use the arrow button to move them up above the $(PATH) variable. (Duh!)

    I've done lots of projects before and I've never run into this problem until now (trying to use a new library) so I just assumed that they were already in there somewhere. When I went in to check it out after reading WeBMartians post and I saw that $(PATH) thing on the bottom of the list I just figured everything was all hunky-dory. Then I got all frustrated because it still wasn't working and I cursed the forums for the hundred millionth time for giving me information that worked for everyone but myself. (The gods of technology truly hate me.)

    Then, after much gnashing of teeth, I reread his post and I actually understood what he was saying: I realized that I actually had to add these variables if they weren't there. (Doh!)

    Point is: if they're not there, just add them and see if that works.

  • John Morris

    The date on this post is pretty ancient. Anyway, here's what I found:

    If you set your environment variables (Start > Control Panel > System : Advanced tab; click Environment Variables) to use %SystemRoot% instead of explicit paths (say, C:\Windows), MSVS 2005 does not understand %SystemRoot% or it resets its entries... ...or both. Don't just believe what the list box says; Edit the item and you'll see the differences.

    What you must do is change MSVS 2005 options (Tools menu > Options > Project and Solutions > VC++ Directories) to ensure that
    $(SystemRoot)
    $(SystemRoot)\System32
    $(SystemRoot)\System32\wbem
    are specified BEFORE $(PATH).

    Setting your system's environment variables to use $(SystemRoot) rather than %SystemRoot% (indeed, even using     %SystemRoot%) is not a good idea: too much (MSVS 2005 as well as other applications) seems to break.

  • PanBocian

    FYI, this problem arose for me after installing MSXML 4.2 SP2 SDK. It seems that installer not just added paths to the executable list in VC++ Directories, but actually removed paths as well( as the "$(SystemRoot)\system32" used to be there, then after the install, it was gone....and it's added SySWow64 in it's place, which doesn't make sense, as I'm not running x64 Windows XP and don't even have that directory on my machine.
  • Project : error PRJ0003 : Error spawning 'cmd.exe'.
Answer this question