I have a web part which was originally written for Sharepoint 2003. I have recompiled it and deployed it to MOSS 2007. I have made some changes and tried to deploy again using the following script"C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\stsadm.exe" -o addwppack -filename Portal.Webpart.Menu.Deploy.cab -forceI get a message to say that the deploy failed because the web part dll was in use by another process.This has now happened a couple of times and the only way I know to get round it is to reboot the server and then deploy.Does anyone have any ideas why this might have become a problem or what I can do to release the dll before deployment?ThanksPaul

Just restart IIS. iisreset /noforce SharePoint Tips & Tricks Portal | Microsoft MVP | My Blog | My twitter

Sorry Michael, I unmarked this reply as the answer because it did not work for me. In the end, the only solution was to reboot the server.In my case, the web part uses a dll which is also used by another application which runs once a day to perform some data-synchonisation. The app was not active at the time (I checked in the task manager) so I cannot figure out what might be causing the problem.I should also say that this problem is only on the production server. On the test server (virtually identical setup) the problem does not occur.Can anyone recommend tools to identify which process and which dll is causing the problem?ThanksPaul

You can use the LockHunter for such purposes http://lockhunter.com/ or alternatively use the ProcessMonitor and watch the folder where you dll is for the processes that access that dll SharePoint 2007 - 2010 Tips & Tricks Portal | Microsoft MVP | My Blog about Information Management | My twitter