Skip to main content
Kofax

*** Archive *** Kofax TotalAgility - Enable Unity Logging for Export

Article # 3030682 - Page views: 96

Applies to

KTA v7.x

Background

This KB has been created to document the steps required to add Unity Logging for the Export connector in TotalAgility
We must make 2 changes in 2 config files, as detailed below

Enable Unity Logging

In the \\TotalAgility\CoreWorkerService\Agility.Server.Core.ExportService.exe.config file,
Search for KTALog, uncomment the section, ensure that Autoflush is True and add -ExportService to the name of the text file
i.e.
ExportService.png

In the same config, search for <unity xmlns="http://schemas.microsoft.com/practices/2010/unity">
Add the following after <container>:
<extension type="Agility.Server.Common.Logging.LogMethodRegistration, Agility.Server.Common, Version=1.0.0.0, Culture=neutral, PublicKeyToken=d86c87abe4a71948" />

i.e.
Unity.png

Save the config file

In the \\TotalAgility\CoreWorkerService\Agility.Server.Core.ExportWorker.Host.exe.config file,
Search for KTALog, uncomment the section, ensure that Autoflush is True and add -ExportWorker to the name of the text file
i.e.
ExportWorker.png

In the same config, search for <unity xmlns="http://schemas.microsoft.com/practices/2010/unity">
Add the following after <container>:
<extension type="Agility.Server.Common.Logging.LogMethodRegistration, Agility.Server.Common, Version=1.0.0.0, Culture=neutral, PublicKeyToken=d86c87abe4a71948" />

i.e.
Unity.png

Save the config file

After these changes have been made,
Ensure that the C:\Temp folder exists,
Restart the CoreWorker and Export services, 
Replicate the issue & attach the logs generated at C:\Temp to your support case along with the (unfiltered) Application Event Logs