batch build over telnet and error PRJ0003 : Error spawning

batch build over telnet and error PRJ0003 : Error spawning

• Torns

  Hi Josh,
  
  I made a little project, and tried to build it on the machine of a collegue via telnet. This works.
  Differences to our server
  - Server runs under Win2000Server
  - PC of my collegue runs Win XP
  
  May this be the relevant point Or are there any issues/problems known about VC8.0 on Win2000
  
  Greetings from Germany
  Markus
  
  
  
  
  

• XBTester

  Hi Ayman,
  
  I tried your suggestions, but I had no success.
  Maybe more hints for you:
  - we use VC8.0 now, working over telnet with VC7.0 worked (without setting additional directories in the IDE)
  - we have a special machine here just to compile our projects.
  Calling our batch files, which contains lines like this:
  devenv /build release sofilib.vcproj
  works on this machine, when we start it direct on the machine.
  But when we use a telnet to log to this computer, we get the errors mentioned
  The server works with Win2000, the clients with XP
  
  Greetings from Germany
  Markus
  
  

• Kate Wells

  hmm. it would be surprising if the installation location of VS made any difference, but I guess you never know...

  a more likely cause is the OS difference, because in VS 2005 we use Job objects to try to launch the build processes and all the Job APIs that we need are not supported on Windows 2000. we should fall-back and try spawning the processes without Jobs, but perhaps something has gone wrong (internally in VS, that is) that makes us fail to do so.

  I don't have immediate access to a Windows 2000 machine to try telnet'ing to. can you perhaps try a similar experiment as before, but using a Win2000 machine (I'll see if I can track down a Win2000 machine that I can get access to, but being the holidays it may not be possible right away).

  josh

  
  
  

• Ilya Lehrman

  The original error implies that the IDE is not finding cl.exe on your machine. Could you make sure that cl.exe exists at the Vc7\bin directory
  
  It looks like the IDE is not finding the tools
  
  If it is there then I believe you can inform the IDE about it. Just start the IDE (without opening a specific project) and do the following:
  
  1) Go to Tools --> Options
  2) Click on the the projects folder at the left menu.
  3) Under "projects", click on "VC++ Directories"
  4) Make sure that the top right window labeled "Show directories for" contains "Executable files"
  5) click on the new New Line icon (icon similar to new folder icon on the top right)
  6) add the location where your cl.exe exists, e.g. d:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin (and the corresponding location from the other machine)
  
  Hope this helps!
  
  Thanks,
    Ayman Shoukry
    VC++ Team
  
  
  

• Morgan Cheng

  it sounds like this could be a permissions issue with the account that you are logging on with. we are not able to either launch the processes that are needed to build, or perhaps are not able to create the Job objects to contain those processes... I'm not sure what could cause that aside from permissions/security settings.
  
  FYI: I tried building a project via a telnet session to another of my machines, using both devenv /build and vcbuild.exe and both were successful... 
  
  
  josh
  VC++ Project System developer
   
  
  

• Jeffrey Litch

  Hi Marcus,
   I don't have further hints. I will send an email to the IDE folks concerning the issue and point them to the post.
  
  Thanks,
    Ayman Shoukry
    VC++ Team
  
  

• José Valim

  Hi,
  
  maybe one more comment.
  On our server the VC8 is installed on a different drive than the operation system. VC7 is installed on the same drive as the OS.
  Is it possible, that this causes the trouble
  
  Greetigns from Germany
  Markus
  
  

• ReneL

  Hi Josh,
  
  maybe it's a problem with permissoions. But we do same same batch build process with VC7.0 and this works fine.
  We don't know any significant difference between both build processes, or differences in the user permissions between both. So do you know anything what's different with permissions between both compiler versions
  
  Greetings from Germany
  Markus
  
  

• Radoslav Č&#225&#59;p

  Hi Josh, I still don't know what job objects are, but I think that is not so important for us. We use Win 2000 on this machine just because of 'never change a running system'. But we found another solution, we access the machine via RemoteDesktop from XP. This solution works just fine. So thanks for your efforts and have a nice christmas. Greetings Markus
  
  

• Lorren

  changes have been made to the build system in VS 2005 in order to support new features like Unicode output from the compiler/linker, multi-threaded builds etc. none of them had anything to do with user permissions or security settings. the only change I can think of that might impact this is that all processes are started under Job objects if you are running on an OS that fully supports them (Windows XP and onwards, I believe), but I don't know of anything about them specifically that would cause a failure like this.
  
  we do need to write a temporary file to the project directory and execute it (a batch file with the build commands in it), but this hasn't changed from previous versions.
  
  can you try a simple test case create a new project (win32 console application, for instance) on a different machine and telnet to it and build the project. are the results the same (of course this experiment may not yield interesting results if machines that you have available to use are all set up the same way).
  
  
  josh
  
  
• batch build over telnet and error PRJ0003 : Error spawning