Troubleshooting: Enable Tessitura logging

Article author
Miguel Panayotty
  • Updated

If you’ve tried importing an Extraction or List Manager list from Tessitura into WordFly and you’re running into issues, WordFly Support can help facilitate investigation with Tessitura logging enabled.

 

What to expect with Tessitura logging:

  • Logging captures more information about errors with the Tessitura integration configuration and list generation errors.
  • Logging is enabled in the WordFly web.config located on the IIS server where WordFly is installed.
  • In order for the logging to be written to the log file the WordFly identity account in IIS needs to have permission to write to the log folder.
  • Once logging is enabled we will ask you to rerun the list import and test your integration in WordFly. Log files should be generated, reply to your support ticket with the log files attached.
  • After troubleshooting is complete, disable logging so that log files are not continuously generated.
  • RAMP hosted organizations will need to open a Tessitura support ticket to request logging.

 

To enable Tessitura logging

 

1. Open the WordFly services web.config found in IIS

We prefer to open the web.config in Notepad++ or another plain text editor, such as VS Code.

 

2. Scroll to the Enable Logging section

<!--=========================================
 == Enable Logging here
 =========================================-->

<!--
 <system.diagnostics>

<trace autoflush="true" indentsize="2" />
 <sources>

 

3. Remove the <!-- above <system.diagnostics>

<!--=========================================
 == Enable Logging here
 =========================================-->


 <system.diagnostics>

<trace autoflush="true" indentsize="2" />
 <sources>

 

4. Scroll down to the  </system.diagnostics>

</sources>

 <switches>
 <add name="ErrorSwitch" value="Error" />
 <add name="WarningSwitch" value="Warning" />
 <add name="InfoSwitch" value="Information" />
 <add name="VerboseSwitch" value="Verbose" />
 </switches>
 </system.diagnostics>
-->

 

5. Remove the --> below </system.diagnostics>

This enables all logging options.

 </sources>

 <switches>
 <add name="ErrorSwitch" value="Error" />
 <add name="WarningSwitch" value="Warning" />
 <add name="InfoSwitch" value="Information" />
 <add name="VerboseSwitch" value="Verbose" />
 </switches>
 </system.diagnostics>

 

6. In each initializeData path, confirm the path points to your WordFly site logs folder

Important: Do not change the file name at the end of the logs path (example: PopEmsTessituraTrace.txt)

Example of each path to update:

 

  • c:\inetpub\wwwroot\wordflyapi\logs\PopEmsTrace.txt
  • c:\inetpub\wwwroot\wordflyapi\logs\PopEmsTessituraTrace.txt
  • c:\inetpub\wwwroot\wordflyapi\logs\PopEmsTrace.txt

 

7. Locate <source name="Pop.Ems" switchName="ErrorSwitch"

<source name="Pop.Ems" switchName="ErrorSwitch" switchType="System.Diagnostics.SourceSwitch">

 

8. Update the switchName value to VerboseSwitch

<source name="Pop.Ems" switchName="VerboseSwitch" switchType="System.Diagnostics.SourceSwitch">

 

9. Save the WordFly web.config

 

10. Run some tests to generate logs

  • Test the integration from Account > Tessitura and ask WordFly to test the integration as well.
  • Import the Tessitura Extraction or List Manager list to generate the error.

 

11. Reply to your WordFly support ticket with the updated logs attached

 

12. After troubleshooting is complete, disable logging so that log files are not continuously generated

To disable logging, follow steps 1-5 above to add the comment elements <!-- and --> back to the web.config.

 

 

 

Related articles