Problem
In situations where your K2 service become unresponsive but never fully crashes, a memory dump would be more useful than a crash dump. This is because in order for the crash dump to be generated, the K2 service must fully crash. You would see that the K2 service was terminated in the event viewer/ host server logs. However if this is not the case, capturing a memory dump would be the next best thing to troubleshoot the issue.
Solution
1. Download the procdump tool and install from here: https://learn.microsoft.com/en-us/sysinternals/downloads/procdump2. Create a folder to be used to save the .dmp file (example C:\Dump)3. Open task manager, Processes, right click on 'CPU' or 'Memory' and click enable 'PID'4. Once procdump is installed, you'll need to run it from a CMD window as Admin. Example:
C:\Users cd C:\Users\Downloads\ProcdumpC:\Users\Downloads\Procdump - procdump64.exe (You can use 64bit version if necessary)5. The syntax for the next step is as followed:procdump -ma [PID of K2 Hostserver] C:\dump\k2hostserver.dmp ('-ma' is enables Full memory dump and PID is process ID of K2hostserver.exe in task manager)Example - C:\Users\Downloads\Procdump procdump -ma 8080 C:\Dump\k2hostserver.dmp6. Once memory dump is generated, install and run Debug Diagnostic tool: https://www.microsoft.com/en-us/download/details.aspx?id=1034537. Import the newly generated.dmp file and check box 'DotNetMemoryAnalysis' then run analysis. If an analysis report is generated then that means the dump file was successful.