Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  1. Open Task Manager, find the IIS Worker Process that takes a lot of CPU

  2. Right-click that process and select Go to details:

    Image Added
  3. Check who is the user running that process under the User name column (it is "AccessPortal" in the following sample screenshot):

    Image Added
  4. Go to IIS Manager, Application Pools, find the pool with that name, right-click on it and select View Applications:

    Image Added
  5. Check what is the name of the Site that runs on that application pool (it is "AccessPortalBastion" in the following sample screenshot):

    Image Added
  6. Open sites list in IIS manager (by clicking on Sites folder in the left panel) and check what is the id of the needed site (it is "2" in the following sample screenshot):

    Image Added
  7. Last step: go to C:\Inetpub\logs\LogFiles and select folder W3SVCN where N is the id found in the previous step (like W3SVC2). Copy log file from the date the IIS was low and file from the date it is high.

    Image Added
  8. Thank you!

Note: If there are more than one applications in step 5 – please perform next steps 5-7 for each one of the applications