Resolution | Steps to enable WCF logging:
- Go to the Archer site’s virtual directory (\inetpub\wwwroot\Archer) and open the “config” folder.
- Open the “Diagnostics.config” file in Notepad for editing.
- Locate the following lines and adjust the log file path for Web_messages.svclog and Web_tracelog.svclog:
<add initializeData="C:\dev\Web_messages.svclog" <add initializeData="C:\dev\Web_tracelog.svclog"
- Close and save the “Diagnostics.config” file.
- Go to the Archer site’s virtual directory (\inetpub\wwwroot\Archer) and open the “web.config” for edit in Notepad.
- Toward the end of the file, locate these two lines and move the “-->” to the end of the line above.
BEFORE <!-- Uncomment the section below to turn on tracing for WCF services <system.diagnostics configSource="Config\Diagnostics.config" /> --> AFTER <!-- Uncomment the section below to turn on tracing for WCF services --> <system.diagnostics configSource="Config\Diagnostics.config" />
- Perform an IISRESET.
- Reproduce the issue and wait a minute after the error so the log files get updated.
- Collect the WCF logs from the log path above.
- After testing, edit the “web.config” file again by moving the “-->” back down to comment out the line.
- Perform an IISRESET.
If you open the WCF log files in Microsoft Service Trace Viewer, find the items in red and select them. The exception message is in the XML tab.
The following image is from an issue where the left Navigation Menu would not load for some Workspaces.
|