Am unable to compile anything with Visual C++ Express. Installation carried out 'to the book', including using 'Install cleanup'.
First error message is "This project is out of date". Building the project , gives error code 1073741511, which I believe is 'file not found'.
Profiling with 'Dependency Walker'Yields the following:
Started "c:\program files\microsoft visual studio 8\vc\bin\CL.EXE" (process 0xECC) at address 0x00400000. Successfully hooked module.
Loaded "c:\windows\system32\NTDLL.DLL" at address 0x7C900000. Successfully hooked module.
Loaded "c:\windows\system32\KERNEL32.DLL" at address 0x7C800000. Successfully hooked module.
DllMain(0x7C900000, DLL_PROCESS_ATTACH, 0x00000000) in "c:\windows\system32\NTDLL.DLL" called.
DllMain(0x7C900000, DLL_PROCESS_ATTACH, 0x00000000) in "c:\windows\system32\NTDLL.DLL" returned 1 (0x1).
DllMain(0x7C800000, DLL_PROCESS_ATTACH, 0x00000000) in "c:\windows\system32\KERNEL32.DLL" called.
DllMain(0x7C800000, DLL_PROCESS_ATTACH, 0x00000000) in "c:\windows\system32\KERNEL32.DLL" returned 1 (0x1).
Injected "c:\depwalker\DEPENDS.DLL" at address 0x08370000.
DllMain(0x08370000, DLL_PROCESS_ATTACH, 0x00000000) in "c:\depwalker\DEPENDS.DLL" called.
DllMain(0x08370000, DLL_PROCESS_ATTACH, 0x00000000) in "c:\depwalker\DEPENDS.DLL" returned 1 (0x1).
Loaded "c:\windows\system32\ADVAPI32.DLL" at address 0x77DD0000. Successfully hooked module.
Loaded "c:\windows\system32\RPCRT4.DLL" at address 0x77E70000. Successfully hooked module.
Loaded "c:\windows\system\MSPDB80.DLL" at address 0x10300000. Successfully hooked module.
Loaded "c:\windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd\MSVCR80.DLL" at address 0x78130000. Successfully hooked module.
Loaded "c:\windows\system32\MSVCRT.DLL" at address 0x77C10000. Successfully hooked module.
First chance exception 0xC0000139 (DLL Not Found) occurred in "c:\windows\system32\NTDLL.DLL" at address 0x7C964ED1.
First chance exception 0xC0000139 (DLL Not Found) occurred in "c:\windows\system32\NTDLL.DLL" at address 0x7C964ED1.
Second chance exception 0xC0000139 (DLL Not Found) occurred in "c:\windows\system32\NTDLL.DLL" at address 0x7C964ED1.
Exited "c:\program files\microsoft visual studio 8\vc\bin\CL.EXE" (process 0xECC) with code -1073741511 (0xC0000139).
Can anyone tell me how to find out the name of the missing dll
Cheers,
BriTheProblem.

dll hell ???
Eric Murphy
Someone else got the same error :
http://forums.microsoft.com/msdn/showpost.aspx postid=53712&siteid=1
The solution was to do a full re-installation. So perhaps your installation is messed up (for whatever reason).
Dondata
Thanks, Bri and Phil, for solving my same problem as well. I'm luck that the problem hassled me just a couple of days when I found your discussion.
Just a update for the information about the dll files in my case:
mspdb80.dll in correct location (....\ide\mspdb80.dll) is version 8.0.50727.762 -Size 169Kb - 1st Dec 2006.
mspdb80.dll in wrong location (...\VC\bin\mspdb80.dll) is version 8.0.40310.39 - size 150Kb - 3 Mar 2006.
Astrogator
SpeakerBob
Thanks for reply, but I have read every posting and relevent document available. This doc is about the worst ever, talk about stating the obvious.
The reply from Phil Lucido has solved the problem - wrong dll in wrong place.
v-pakote
Phantastic Phil !!,
I really don't believe this. After two months of hair pulling you have provided the solution overnight. It was, as you say, a version of mspdb80.dll in the wrong place. As you instructed, I moved it out of c:\windows\system, re-ran the walker profile and the prog compiled !!!! Thank you so, so much.
For information in case anyone else comes up against the same problem:
mspdb80.dll in correct location (....\ide\mspdb80.dll) is version 8.0.50727.42 - size 168 Kb - 23rd Sept 2005.
mspdb80.dll in wrong location (...\windows\system\mspdb80.dll) is version 8.0.40310.39 - size 242Kb - 22 Aug 2005.
How the latter dll got there I shall never know.
Once again thanks so much - brilliant!
BriTheProblemNoLonger. (hair growing again)
Tobi
Yes, I removed everything inc. the .net framework, not just C++. As I said, I uninstalled using the microsoft hand uninstallation sequence and the clean up tool Further info, if it helps
1. C# and VB installations work fine.
2. Command Line reads as follows:
/Od /D "WIN32" /D "_DEBUG" /D "_UNICODE" /D "UNICODE" /FD /EHa /MDd /Yu"stdafx.h" /Fp"Debug\YetAnotherTrial.pch" /Fo"Debug\\" /Fd"Debug\vc80.pdb" /W3 /nologo /c /Zi /clr:pure /TP /errorReport:prompt /FU "c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.dll" /FU "c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Data.dll" /FU "c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Drawing.dll" /FU "c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Windows.Forms.dll" /FU "c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.XML.dll"
Does that give anyone any clues
A very frustrated, hairless BriTheProblem.
Hossam El-Deen
Have done full re-installation 5 times! This included uninstall by hand as per Microsoft instructs. Also used 'Install CleanUp'. All to no avail! Have been working on this problem for two months and done everything I can think of. That is why I am sure it is a dll prob, but am unable to sort out which dll is missing as I do not have the expertise.
BriTheProblem
thiti300
Here is what the Visual Studio .NET 2003 (probably the same for 2005) documentation says about that one error you are recieving. It's not very informative tough...
error result returned from 'command line'.
A command, command line, which was formed from user input in the Property Pages dialog box, returned an error code but no information will appear in the Output window.
The resolution to this error depends on which tool generated the error. For MIDL, you will get an idea of what went wrong if /o (Redirect Output) is defined.
A batch file, such as a custom build step or build event, that is not informative about failure conditions could also be the reason for this error.
To resolve this error, be more informative on error conditions.
genocide77
Thanks for replying.
Build log as follows:
Qi Sheng
Ruxana Patel
RichLando
I've also been having this error for the last few weeks (probably since I installed the Platform SDK.
I have tried what was suggested above.
I have FOUR copies of mspdb80.dll. The correct one (I assume) 8.0.50727.762 -Size 169Kb - 1st Dec 2006, is in the correct location (....common7\ide\mspdb80.dll)
The other three are in the following locations:
C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Bin\win64 - 03-03-06
C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Bin\win64\x86\AMD64 - 03-03-06
C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\VsaEnv - 23-09-05
These all seem to be older.
I have tried renaming these three and leaving the corrct one, but my programs still will not build or compile!
C#, Visual Basic programs work just fine.
There have been various suggestions in the various threads that I've found regarding this problem, but none of them worked.
Please helpe me....
Nyasha
I suspect the problem is because you've got an old copy of mspdb80.dll in the wrong location. Note this line from your Dependency Walker output:
Loaded "c:\windows\system\MSPDB80.DLL" at address 0x10300000. Successfully hooked module.
Mspdb80.dll should not be loaded from c:\windows\system. That directory appears to be used by 16-bit apps only. I'm not sure how you got a copy of mspdb80.dll there. My guess is that the copy there is bad in some way. The good copy should be available in your VS2005 installation, at "c:\Program Files\Microsoft Visual Studio 8\Common7\ide\mspdb80.dll".
Chances are you just need to delete c:\windows\system\mspdb80.dll. I'd probably try renaming it first, to something like mspdb80.dll.save, just in case it's in use. I'd also check the date and timestamp on the two copies, to see if the misplaced version is just a copy of the good one, or something else entirely.
If renaming the bad mspdb80.dll doesn't fix your problem, then my next guess is that you've got a bad copy of c:\windows\system32\secur32.dll. That's because, when I run Dependency Walker on my installation of VS2005's cl.exe, where you start getting exceptions, I instead see secur32.dll being loaded. Secur32.dll is being loaded because mspdb80.dll needs it, which again points to mspdb80.dll as being the problem here.
sakthiG