What information to collect when Centrestack server is not responding or hit high CPU/RAM usage

Sometimes Centrestack server may become not responding. The web portal becomes not responding. Or you may notice a process uses high CPU/RAM. May have to reboot the server or restart IIS service to restore the service.

In that case, need to collect some information when IIS is not responding. Here is the list.

1. Ensure IIS Logging is disabled.
   Open IIS Manager.
   Under Server, open Logging
   
   If logging is enabled, see 'Disable' link on right. Click it to Disable IIS logging.
   
   Once IIS Logging is disabled, under Action, will see 'Enable' link. It confirms the logging is disable.
   
   Once IIS logging is disabled, if still see the issue, continue.
   
   
2. Follow the KB article here to check the Centrestack server version.
   https://support.centrestack.com/hc/en-us/articles/115005140654-Where-Are-The-Product-Versions-
3. Open windows Task Manager. Go to Process Details tab.
   
   Here, right click the Column name and click 'Select columns'
   
   In the Column list, select 'Commit Size', Handles and Threads
   
   
   Check whether there is any high CPU/Commit processes. If so, get the process User name/CPU/Commit size/Handles/Threads
   
   
   
4. Open IIS Manager. Go to Application Pools. Here, make sure all pools are running.
   
   
5. Open browser on the machine. Visit the following 2 URLs.
   
   http://localhost/namespace/n.svc/helloworld
   Sample output: 
   
   
   http://localhost/storage/u.svc/helloworld
   Sample output:
   
   
   
6. From the browser, visit http://localhost/portal/loginpage.aspx
   
   See whether user still hit the issue when login via the URL on the server directly.