Skip to main content

When sending a batch to KTM Server a SchedulerSessionPipe error occurs

Article # 3037109 - Page views: 225


When sending a batch to KTM Server a SchedulerSessionPipe error occurs

Sample Errors: 
A) net.tcp://localhost:5000/SchedulerSessionPipe
B) net.pipe://localhost/<GUID>


Please follow step by step. It may happen that one step could solve the issue already.

  1. Check if KTM Service is running under (Domain-)Admin-Account
  2. Open Internet Explorer -> Tools -> Advanced -> Security -> Uncheck "check for publishers certificate revocation" -> Uncheck "check for server certificate revocation"
    This must also be checked on the user account which runs the service.
  3. Open C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config and change <runtime/> to <!--<runtime/>-->.
    Add the following below that changed entry:
      <generatePublisherEvidence enabled="false"/>
  4. Open gpedit.msc -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -->
    Check if Account is permitted to "Logon as a batch job" and "Log on as a service" Run "gpupdate /force" from command line.
  5. Check if account has permission for Kofax share "CaptureSV"
  6. Add exception for Kofax files or Disable AntiVirus completely(Stop Service)

Exceptions for Servers:

  • Entire contents of the CaptureSV share
  • Program Files\Kofax\CaptureSS (Kofax server and SQL Express 2005 runtimes)

Exceptions for Clients:

  • Temp directory (check the Environment Variables to ensure that the proper location is excluded)
  • C:\Documents and Settings\All Users\Application Data\Kofax
  • C:\Program Files\Kofax\Capture\Bin
  • *.tif files
  1. Add exception for desired port to firewall or set Windows Firewall to inactive.
    If Port is already used by a different service you can change the listening port for KTM Scheduler Service:
    32-Bit Machine
    HKEY_LOCAL_MACHINE: SOFTWARE\Kofax\Transformation\4.0\Server\
    64-Bit Machine
    Change value for "SchedulerCommunicationPort";

  2. Under same registry entry change "MaxUsedCores" to less cores to check if this is causing the problem.

  3. Reinstall Service through KTM Service Configuration

  4. It was also observed that the System Application eventlog was full and after clearing this the service started

  5. Disable UAC and see if that solves the issue

  6. Disable DEP for programs and see if that solves the issue

  7. Reboot system to ensure all changes are active and no temporary issue caused the problem.


Level of Complexity 



Applies to  

Product Version Build Environment Hardware
Transformation 6.3; 6.4 N/A N/A N/A


Add any references to other internal or external articles