DLL-locking
Find out which process is locking a DLL without extra tools
Today I got the "The process cannot access the file ... because it is being used by another process" error again, during a development build. And as long as the DLL is locked, it's not possible to do a successful build.
Most sites and tips on the internet suggest to download some tool to detect which process is using the DLL. It seems that not many people are aware that
, since Windows XP, we don't need to download (or even pay for) a tool to detect this.Just launch the windows console and navigate to the directory of the DLL. Now type
tasklist.exe /m /FI "MODULES eq locked.dll
and it will show you exactly which processes have loaded and locked this DLL. For moere information about tasklist use tasklist /?
:-)
I wish you nice day
Print article | This entry was posted by tosc on 2010-09-10 at 06:00:00 . Follow any responses to this post through RSS 2.0. |
Tag cloud
backup «best practices» books bug configuration ctp «cumulative update» demo denali dmv ebook humor index indexoptimize integrity kbfix loginproperty maintenance «ms sql server 2008» performance php profiler «reporting services» reviews «service pack» «service pack 2» «service packs» sharepoint «sql 2012» «sql pass» «sql server» «sql server 2005» «sql server 2008 r2» «sql server 2012» «sql server 2014» sqlcat sqlpass «sqlpass franken» ssms ssmstoolspack sysadmin «system views» t-sql «technical note» tempdb tools «trace flag» troubleshooting upgrade whitepapers