This topic explains how you can make your system ready for a debugging session to debug a WCF Service problem on your Content Manager server machine.
Procedure
- Use the
iisreset /stop command to stop IIS.
- Access the folder %TRIDION_HOME%\web\WebUI\WebRoot\bin\
- Back up the file Tridion.Web.UI.Core.dll to, say, Tridion.Web.UI.Core.dll.notTrace.
- From the trace\ subfolder, copy Tridion.Web.UI.Core.dll, overwriting the original.
- Back up the file web.config to, say, web.config.notTrace.
- Open web.config for editing and do the following:
Enclose the <system.diagnostics> section in comment delimiters.
Add the following replacement:
<system.diagnostics>
<sharedListeners>
<add name="WcfListener" type="System.Diagnostics.XmlWriterTraceListener" initializeData="c:\temp\wcfLog.svclog" />
</sharedListeners>
<sources>
<source name="System.ServiceModel.MessageLogging">
<listeners>
<add name="WcfListener" />
</listeners>
</source>
<source name="System.ServiceModel" switchValue="Verbose,ActivityTracing">
<listeners>
<add name="WcfListener" />
</listeners>
</source>
</sources>
</system.diagnostics>
replacing the folder in the initializeData attribute to a log location (to which the w3wp process, typically running under the NETWORK SERVICE account, must have read, write and creates access) of your choosing.
- Save and close web.config.
- Use the
iisreset /start command to restart IIS.