Page Comparison

...

1. Make sure all instances of the TerminalEmulator application are closed
2. Open the folder where TerminalEmulator.exe is installed
3. Find and edit the file "TerminalEmulator.exe.config".

   1. Near the bottom you will see a "<system.diagnostics> / <trace>" entry. In that section, under "<sources> / <source>" you will see a "switchValue" attribute. By default it should be "Off" (case sensitive). Modify this value to instead contain (Case Sensitive):

      Code Block
      Information, ActivityTracing

      
      

   2. This will result in a complete section that looks like the following:

      Code Block
      <system.diagnostics> <trace autoflush="true"> <listeners> </listeners> </trace> <sources> <source name="System.ServiceModel" switchValue="Information, ActivityTracing" propagateActivity="true"> <listeners> <add name="sdt" type="System.Diagnostics.XmlWriterTraceListener" initializeData= "WcfDetailTrace.svclog" /> </listeners> </source> </sources> </system.diagnostics>

      NOTE: The <system.diagnostics> block may be present in the file but marked to be ignored. Check for the presence of "<!--" and "-->" around the block, such as the following:

      Code Block
      <!-- <system.diagnostics> ... </system.diagnostics> -->

      If present they need to be removed or the section will be ignored. They can be replaced after the log file is generated if you wish.

4. Save and close the file.

5. Restart TerminalEmulator as you would normally

6. Once you get the connection error, close TerminalEmulator.

   1. In the same folder as TerminalEmulator you should find a file named "WcfDetailTrace.svclog".

   2. Generally you should send this file to InteliSys Personnel, but you can also review it yourself using the Microsoft SvcTraceViewer app ("C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.1 Tools\SvcTraceViewer.exe" - alternatively see HERE for instructions on where to obtain it)

7. IMPORTANT Be sure to revert the "switchValue" setting to "Off" when you are done debugging. The service trace logs can be quite large and can also affect performance.

...