- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I see this too on every build in VS2015. It seems harmless, but I will be asking the developers about it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Try this. Do a Build > Clean on the solution. Then go into the project folder and delete all .pdb files you can find. See if the message goes away.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I couldn't get rid of it with a clean and *.pdb delete, but it does seem to be harmless and only occurs with the Debug/Win32 build. The Release builds and the Debug/x64 build don't have the problem. I'll just ignore it for now.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It turns out that this is a problem Microsoft has acknowledged and is planning to fix in a VS2015 update. It does seem to be generally harmless. We are tracking this with our issue DPD200569783. Workarounds are said to be:
1. Compile with the option /Z7 rather than /Zi or /debug:full
2. Modify PATH such that
c:/Program files (x86)/Microsoft Visual Studio 14.0/VC/BIN
precedes
c:/Program files (x86)/Microsoft Visual Studio 14.0/Common7/IDE
3. Rename the copy of mspdb140.dll residing in the directory
c:/Program files (x86)/Microsoft Visual Studio 14.0/Common7/IDE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I had the "error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb"
I changed the name of MSPdb140.dll to MSPdb140_Save.dll and the message went away.
Now I get "error #10037: could not find 'link'"
The only Link.exe I have is in C:\Program Files (x86)\Microsoft Visual Studio 12\VC\....
There is no Link.exe in the c:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\...
Can I use the one in VS12 ?
Windows 7 64 Bit
Visual Studio 2015
Intel Fortran Parallel Studio XE 2015
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You might find that it is easier to just ignore the error instead of renaming files and getting other errors. It seems to be harmless, plus for me it only occurs with Debug/32-bit builds. If you build for Release/32-bit or Debug/Release/64-bit then you shouldn't get the error.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Options 1 and 2 are the recommended workarounds. Option 3 is not recommended due to the risk of impacting other applications as Dana has discovered.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It looks as if Microsoft fixed this issue in VS2015 Update 1.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page