EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB6627: How to enable different levels of logging for Microsoft Internet Information Server to troubleshoot MicroStrategy Web issues


Community Admin

• Strategy


To troubleshoot MicroStrategy Web issues, users must enable different levels of logging for Microsoft Internet Information Server (IIS)

To troubleshoot Strategy Web issues, users must enable different levels of logging for Microsoft Internet Information Server (IIS) by executing the following steps:

  • Launch the Internet Information Services manager.
  • Expand the machine name.
  • Right-click on 'Default Web Site' and choose 'Properties'. The following screen is launched, and displays the checkbox 'Enable Logging' that needs to be checked for log file creation.
ka04W000000OeO7QAK_0EM44000000296c.gif
  • To change the level of logging, click on the 'Properties' button in the 'Enable Logging' subsection. A window called 'Extended Logging Properties' is launched. Access the 'Extended Properties' tab as illustrated in the screenshot below.
    NOTE: For these changes to take effect, please restart the IIS service.
ka04W000000OeO7QAK_0EM44000000296h.gif

Extended Logging Properties - Extended Properties Property Sheet:
Use this property sheet to customize W3C Extended logging by choosing the fields (items) to be recorded in the log. To limit log size, omit unneeded fields.
 
The following is a description of each field.

  • Date The date on which the activity occurred.
  • Time The time the activity occurred.

Extended Properties:

  • Client IP Address: The IP address of the client that accessed the server.
  • User Name: The name of the user who accessed the server.
  • Service Name: The Internet service that was running on the client computer.
  • Server Name: The name of the server on which the log entry was generated.
  • Server IP: The IP address of the server on which the log entry was generated.
  • Server Port: The port number to which the client is connected.
  • Method: The action the client was trying to perform (for example, a GET command).
  • URI Stem: The resource accessed: for example, an HTML page, a CGI program, or a script.
  • URI Query: The query, if any, the client was trying to perform; that is, one or more search strings for which the client was seeking a match.
  • HTTP Status: The status of the action, in HTTP terms.
  • Win32 Status: The status of the action, in terms used by Windows.
  • Bytes Sent: The number of bytes sent by the server.
  • Bytes Received: The number of bytes received by the server.
  • Time Taken: The length of time the action took.
  • Protocol Version: The protocol (HTTP, FTP) version used by the client. For HTTP this will be either HTTP 1.0 or HTTP 1.1.
  • User Agent: The browser used on the client.
  • Cookie: The content of the cookie sent or received, if any.
  • Referer: The site that directed the user to the current site.

Process Accounting:

  • Process Event: The type of process that triggered the event, either CGI or out-of-process application. The type can be CGI, Application, or All.
  • Process Type: What event was triggered: Site-Stop, Site-Start, Site-Pause, Periodic-Log, Interval-Start, Interval-End, Interval-Change, Update, Eventlog-Limit, Priority-Limit, Process-Stop-Limit, Site-Pause-Limit, Eventlog-Limit-Reset, Priority-Limit-Reset, Process-Stop-Limit-Reset, or Site-Pause-Limit.
    • Site-Stop: The Web site was stopped.
    • Site-Start: The Web site was started or re-started.
    • Site-Pause: The Web site was paused.
    • Periodic-Log: This is a regularly defined log entry whose interval was specified by the administrator.
    • Reset Interval-Start: The Reset Interval has begun.
    • Reset Interval-End: The Reset Interval has been reached and reset.
    • Reset Interval-Change: The Web site administrator changed the value for the Reset Interval.
    • Update: One of these events happened: the log interval was changed, and interval event took place, the site either stopped started, or paused.
    • Eventlog-Limit: An event log was made for the Web site because its CPU resource usage for CGI and out-of-process application reached the event log limit set by the administrator.
    • Priority-Limit: The Web site had a CGI or out-of-process application set to low priority because it reached the low priority limit set by the administrator.
    • Process-Stop-Limit: The Web site had a CGI or out-of-process application stopped because it reached the process stopping limit set by the administrator.
    • Site-Pause-Limit: The Web site was paused because it had a CGI or out-of-process application reach the site pause limit set by the administrator.
    • Eventlog-Limit-Reset: The Reset Interval was reached or the Eventlog-Limit was manually changed.
    • Priority-Limit-Reset: The Reset Interval was reached or the Priority-Limit was manually changed.
    • Process-Stop-Limit-Reset: The Reset Interval was reached or the Process-Stop-Limit was manually changed.
    • Site-Pause-Limit: The Reset Interval was reached or the Site-Pause-Limit was manually reset.
  • Total User Time: The total accumulated User Mode processor time, in seconds, that the site has used during the current interval.
  • Total Kernel Time: The total accumulated Kernel Mode processor time, in seconds, that the site has used during the current interval.
  • Total Page Faults: The total number of memory references that resulted in memory page faults.
  • Total Processes: The total number of CGI and out-of-process applications created during the current interval.
  • Active Processes: The total number of CGI and out-of-process applications running when the log was recorded.
  • Total Terminated Processes: The total number of CGI and out-of-process applications stopped due to Process Throttling during the current interval.

Comment

0 comments

Details

Knowledge Article

Published:

June 9, 2017

Last Updated:

June 9, 2017