![]() ![]() Not sure if its due to using the Stop-Process powershell command that forcefully kills our worker EXE, but this issue has become a real pain in the butt and i need to figure out how to fix it before i go crazy. This is causing alot of issues with our process of updating our code and respawning our worker EXE, as the worker will fail to start due to the COM Dll being in use by dllhost.exe.ĭoes anyone have any ideas on how to fix this and have the dllhost.exe release the COM library so we can delete the file and restart our worker EXE with no issues? (preferably using powershell) Upon further investigation using ProcessExplorer, the DLL is still indeed in use by the dllhost.exe process (and not by our worker EXE). Often times, but not always, during step 3 when trying to delete the files in the EXE's folder, it will fail trying to delete the COM dll, saying that it is use by another process. Delete all files in the folder the EXE runs from, including the COM library.Issue Stop-Process command to stop our worker EXE process Download paul.dll for free Fix the DLL file error - paul.dll Do it yourself or use.We update our code from time to time, and have written a powershell script that performs the following tasks to update and restart the EXE: You can download Sysinternals Process Explorer here.I have a worker EXE i am running on Windows Server 2012 R2 that uses a COM DLL, and am having troubles with the COM DLL being in use after closing our process. Proceed with care when deleting handles as this may generate erratic behavior and instabilities may occur. Selecting the process/handle/program entry.An individual program or handle in the list provided by Process Explorer can be killed by: ![]() To release the lock on the file you are attempting the maintenance operation on, you will need to kill the appropriate process.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |