API troubleshooting

If you cannot load your custom assembly for any reason, error messages with the necessary information should be included in the Kofax AP Agility log files. There are two types of errors that are logged.

  • The assembly or type cannot be loaded.

    This indicates that the assembly or one of its dependencies has not been installed into the GAC.

  • The configured class does not implement the ICustomInitializer interface.

    When this error occurs, review your implementation and make sure to register the correct class.

User exits are executed in the following processes.

  • Extraction is performed within an ExtractionProcess.exe process.

    Logging output goes into one of the IPA_Extraction log files.

  • Validation is either performed by Transformation Server or when it is done in IIS by a user during Validation.

    • To debug validation in Transformation Server that is part of the Kofax.CEBPM.CPUServer.ServiceHost.exe process, review the IPA_TransformationServier log file.

    • To debug validation in IIS that is part of the w3we.exe process, review the IPA_Web log file.

  • Line pairing and export are executed by the Kofax Core Worker Service.

    To debug this, attache to the Agility.Server.Core.WorkerService.exe process. Logging output goes to the IPACoreworker log file.