Handles via command line - it has not found my dll ComHelper. Process Explorer - it has found my dll ComHelper.dll I was hoping that someone might be able to tell me how I was using handles incorrectly, or if there was a better tool for this. First published on TechNet on PsPing v1.0 : PsPing is a new Sysinternals PsTools command-line utility for measuring network performance.In addition to standard ICMP ping functionality, it can report the latency of connecting to TCP ports, the latency of TCP round-trip communication between systems, and the TCP bandwidth available to a connection between systems. Unfortunately, while I can get SysInternals' process explorer to find the dll, Handles.exe (the supposed command line version of process explorer) does not return anything. In order to fix it, I was thinking about using a command line tool to find the reference to the dll and then recycling the app pool that's using it. If the selected process is waiting for another process, a tree organized by dependency on other processes will be displayed. I'm not sure if it matters, but the w3wp process is set to run as 32 bit via IIS. dll command component (aka a vb 6 library that I've registered on the box using regsvr32.exe) but when I try to copy over the file, the app pool of the website has a lock on it.
On a windows server 2012 r2 box, I'm trying to use Chef to programmatically replace a.
0 kommentar(er)
