Frequently Asked Questions
Frequently Asked Questions: M-Files
How to use IIS failed request tracing to troubleshoot M-Files Web or RPC over HTTPS issues
Posted by Ville Karinen (M-Files) on 11 July 2018 08:39 AM

Sometimes setting up IIS for M-Files Web or RPC over HTTPS connections causes issues whose root causes are not obvious. In these cases you can enable IIS Failed Request Tracing to get more details about what might be causing the problem.


Before you start, you may have to install the IIS tracing feature if it is not already included in your IIS deployment:
Windows Server Manager -> Server Roles -> Web Server (IIS) -> Web Server -> Health and Diagnostics -> Tracing

Setting up tracing:
1. Enable Failed Request Tracing on the web site:
IIS -> Sites -> 'Default Web Site' -> 'Failed Request Tracing…' -> 'Enable'.

2. Add Failed Request Tracing Rules to the Default Web site.
IIS -> Sites -> 'Default Web Site' -> 'Failed Request Tracing Rules' -> 'Add…'

3. Specify content to trace: All Content.

4. Define trace conditions:
Status code(s): 100-999 (all of them).

5. Select Trace Providers:
Providers: WWW Server
Verbosity: Verbose
Areas: All

By default the logs are written to C:\inetpub\logs\FailedReqLogFiles. The folder will contain sub folders holding the actual log files in xml format and style sheets for viewing the logs. Use Internet Explorer to view the logs, and it will automatically use the style sheet in the same folder to display the logs in an easily readable format.


When you are done with the logging, remember to disable Failed Request Tracing, as it has a negative effect on IIS performance and fills up the disk with unnecessary logs.

(0 vote(s))
This article was helpful
This article was not helpful

Help Desk Software by Kayako case