error 1 unexpected error creating debug information file
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss unexpected error creating debug information file access is denied the workings and policies of this site About Us Learn more about
Unexpected Error Creating Debug Information File The Process Cannot Access The FileStack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow could not write lines to file obj debug access to the path is denied Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each tfs build csc unexpected error creating debug information file other. Join them; it only takes a minute: Sign up Error Creating Debug Information - Code Won't Compile up vote 23 down vote favorite 2 I'm using VS 2008. When ever I make a change in my code and try to compile I get the following error: Error 7 Unexpected error creating debug information file 'C:\Documents and Settings\jbezanson\My Documents\MyProjects\DispatchBoard\DispatchBoard\obj\Debug\DispatchBoard.PDB'
Unexpected Error Writing Debug Information The Method Or Operation Is Not Implemented-- 'C:\Documents and Settings\jbezanson\My Documents\MyProjects\DispatchBoard\DispatchBoard\obj\Debug\DispatchBoard.pdb: The process cannot access the file because it is being used by another process. ' DispatchBoard Using Process Explorer, it is always devenv.exe that is locking the file. If I run in Release mode this does not happen. It started 2 days ago when I started a WPF application, and since then it happens with every application I work on. The only info I could find from Google was referring to a bug in VS 2003. Anyone else have this problem? How do I fix it? It is getting very annoying having to kill the file handle every time I want to compile. c# visual-studio-2008 share|improve this question edited Sep 25 '09 at 14:30 Donut 53.8k992126 asked Sep 25 '09 at 14:21 modernzombie 83861738 add a comment| 19 Answers 19 active oldest votes up vote 9 down vote accepted When I have problems with locked files, I use Unlocker. (If you tried everything and it's not working, try this ;) In case of broken link, here's a mirror.
dll(s) in the /obj/ folder of library components. The fix that I have at the moment is as follows: Shut down VS.NET Browse to the project in windows explorer Delete the /obj/ folder. Delete the project outputs (.dll and .pdb) from /bin (not sure cs0042: unexpected error creating debug information file this step is necessary) (can't hurt, might help) -- delete the project outputs from any csc fatal error cs0042 other project /bin folders in the solution that is having issues. Restart VS.NET Rebuild Laugh the next time you hear that DLL Hell is
.pdb The Process Cannot Access The File Because It Is Being Used By Another Processno more in .NET... Update: Just deleting /obj/ after closing VS.NET does it. Ambrose pointed me to prcview.exe and that demonstrated that it is in fact devenv.exe locking the file, so it's VS.NET's own fault, not Index Server or http://stackoverflow.com/questions/1477582/error-creating-debug-information-code-wont-compile anything else that is to blame. Listening to: Disturbed - Remember 26 Comments Steven it's probably also the same problem I had few days ago. Check Index Server, and see if it's running. If you don't need it turn off the services, otherwise add some exclusion directories, the .Net temporary folders for a starter Paschall - Tuesday, August 12, 2003 2:36:00 PM The problem can be caused by virtually anything which runs in the background and is triggered by http://weblogs.asp.net/ssmith/23755 file activity. Index server is one example, also anti-virus scanners tend to do the same. I get this occasionally in VB/C# but much more often with managed C++ projects. I'm not sure why... Addy Santo - Tuesday, August 12, 2003 3:09:00 PM For the record, I am using VS.NET 2003. The one that keeps getting locked is a C# project (class library) in a solution with 4 other VB projects (3 class libs and a web). I'm wondering if the IDE real-time compiling of VB's IDE is hitting the PDF/DLL from the C# project and not cleaning them up. Using prcview, it's clear that only that one project's file are being referenced from the My Documents/Visual Studio Projects/ProjectName/obj/ folder. The rest (the other dlls and pdbs being locked/referenced by devenv.exe) are going to the shadow copy under Application Data/. Thanks for the link to Process Explorer - I'll check it out. Steven Smith - Tuesday, August 12, 2003 10:15:00 PM I've made some good experience to switch from "Debug" to "Release" and back to solve this problem. But it isn't working all the time. Denis Bauer - Wednesday, August 13, 2003 8:10:00 AM Tried switching from Debug to Release, and it worked! Easier than shutting down, to be sure. Thanks for the tip, Denis! Steven Smith - Wednesday, August 13, 2003 3:18:00 PM I've had this problem to, tis VERY annoying! Charles McEvoy
... Access is denied Visual Studio Team Foundation Server > Team Foundation Server - General Question 0 Sign in to vote I am trying to https://social.msdn.microsoft.com/Forums/vstudio/en-US/45aaf041-8b5a-4325-9e11-7a8f63e03a22/cannot-build-csc-unexpected-error-creating-debug-information-file-access-is-denied?forum=tfsgeneral deploy my app, but I get this error in the build. CSC: Unexpected http://crayveon.com/solve-unexpected-error-creating-debug-information-file-pdb-process-access-file-used-another-process-compiler-error/ error creating debug information file 'c:\Builds\2\STAS\STAS\Sources\Documents and Settings\jyothisrinivasa\My Documents\Visual Studio 2010\Projects\STAS\STAS\obj\Debug\STAS.PDB' -- 'c:\Builds\2\STAS\STAS\Sources\Documents and Settings\jyothisrinivasa\My Documents\Visual Studio 2010\Projects\STAS\STAS\obj\Debug\STAS.pdb: Access is denied. How do I fix this? Wednesday, December 14, 2011 5:19 PM Reply | Quote Answers 0 Sign in to vote Hello arame3333, As far as I know when you queue unexpected error a build the TFS, you will first got your source files and projects copied to the working directory by using your build service account, by default to the path: $(SystemDrive)\Builds\$(BuildAgentId)\$(BuildDefinitionPath). So to deal with your issue, please first make sure that the build service account you are using has the required permissions of the above path. In addition, another community member guokecongcong09 encountered the unexpected error creating same issue as you, and guokecongcong09 resolved that issue by copy the source files to another path, and then recreate one new workspace for these files. Please see this thread for further information: http://social.msdn.microsoft.com/Forums/en-US/tfsbuild/thread/deb662d3-e0a6-4de4-a93c-2d039e95ce8b Thanks. Vicky Song [MSFT] MSDN Community Support | Feedback to us Marked as answer by Vicky SongMicrosoft employee, Moderator Thursday, December 22, 2011 5:56 AM Thursday, December 15, 2011 5:14 AM Reply | Quote Moderator All replies 0 Sign in to vote Hello arame3333, As far as I know when you queue a build the TFS, you will first got your source files and projects copied to the working directory by using your build service account, by default to the path: $(SystemDrive)\Builds\$(BuildAgentId)\$(BuildDefinitionPath). So to deal with your issue, please first make sure that the build service account you are using has the required permissions of the above path. In addition, another community member guokecongcong09 encountered the same issue as you, and guokecongcong09 resolved that issue by copy the source files to another path, and then recreate one new workspace for these files. Please see this thread for further information: http://social.msdn.microsoft.com/Forums/en-US/tfsbuild/thread/deb662d3-e0a6-4de4-a93c-2d039e95ce8b Thanks. Vicky Song [MSFT] MSDN Community Supp
is being used by another process. – compiler error? How do I – Solve the – Unexpected error creating debug information file .pdb. The process cannot access the file because it is being used by another process. – compiler error? Written by Cornelius J. van Dyk on May 4, 2010. Posted in How Do I... As a SharePoint Developer, you may run across this error at some point. It is most common when you’re trying to recompile a SharePoint binary, from aVisual Studiosession ON the actual SharePoint server. Of course, in most normal situations, it’s unthinkable to run the compiler on the server, but as SharePoint developers, we know there is no other way to code for the platform so it’s pretty muchSOPfor us. The problem lies in the locks that are taken by the compiler process on the debug info file. Often the locks are taken by your last debug session and unfortunately the locks aren’t always released, even though you’re the same user from the same application. Call it a multi threading anomaly or something. Whatever it is, this happens in Visual Studio 2008. EnterProcess Explorer! This little gem byMark RussinovichfromSysInternals, has been around for a long time, now in it’s12th version. Microsoft bought SysInternals a couple of years ago, and with it, Mark’s great mind. I must say, it was probably one of the smartest acquisitions thatRedmondhas ever made. But I digress. So, if you have Process Explorer installed (if you don’t,download it nowand do so), it generally lives in the C:\Program Files\Process Explorer folder. To unlock your files and resume your compilation, follow these easy steps: Open Windows Explorer. Browse to the C:\Program Files\Process Explorer location, or any other alternative location where you may have installed Process Explorer to. Double click “Procexp.exe” to launch Process Explorer. Once Process Explorer opens, it will display a list of all active processes on your system. Odds are that your .pdb file is NOT shown here. In the top menu, click the “Find” menu item. In the drop down menu, click the “Find Handle or DLL” menu option. NOTE: If you’re a shortcut kinda guy or gal, you could have accessed this option with the “Ctrl+P” keyboard hotkey combo. In the Process Explorer Search dialog window, enter the name of your DLL,