fatal error LNK1201: error writing to program database 'project.pdb'

[onkelhotte]

Hi there,
my colleague and I have an error message

fatal error LNK1201: error writing to program database 'C:\Users\ulso\Documents\Visual Studio 2010\Projects\DFC\bin\DFC_Kernel.pdb'; check for insufficient disk space, invalid path, or insufficient privilege

since a few days. We have to close Visual Studio completely (not just closing the soulution) and delete this file manually. Of course this happens not all the time, there is enough disk space, the path is correct and we have sufficient privileges...

Has anyone seen this behaviour before?

Thanks in advance,
Markus 

[FortranFan]

app4619 wrote:

..

I am now thinking that lockhunter puts a maybe 7 second delay in every build and given the lowish frequency of the glitch it is probably quicker to just right click on the pdb file and pick the unlock action on the times it does lock up.

Either way the unlocker is miles better than have to close and reopen VS. 

In a Visual Studio solution environment with many projects and a set of dependencies between them, one intermediate failure due to a stupid lock on a file can snowball into colossal loss of productivity; until Microsoft can adequately take care of this, LockHunter it is for me in all my "native" DLL and EXE projects.

[andrew_4619]

@#22. I guess it depends on complexity of the project/solution setup, I am finding the only issue is the pdb file at the link stage, that is normally a quick process to repeat.

Anyway Lockhunter rocks and I have three working options to choose from :-)