I kicked off a full load from a File Channel source to SQL Server target. I noticed the Sorter task has been running for 5 hours with all tables in queue. I changed the sorter logging to verbose and have a lot of the following logs.
Event 'CTI (51)' of transaction '00000000000000000000000000000000' at position: '<none>' with record id 0 and timestamp: 00064B3749F8B1D5 ( 2026-02-19 14:24:56.583637 ) <no table> (sorter_transaction.c:458)
The long runtime of your Sorter task with repeated CTI (51) events and <no table> entries usually means Qlik Replicate is processing a heavy stream of change‑table markers without advancing to actual table data. It isn’t truly hung, but is stuck handling CTI events from the File Channel source. This can happen if the source produces large batches or malformed CTI markers, or if the sorter lacks memory/temp space. If progress doesn’t resume after a reasonable time, try breaking the load into smaller batches, adjust sorter resources, or disable CTI handling for a one‑time full load. If the issue persists, Qlik support may need to review your verbose logs and provide a patch or configuration fix.
Thanks for the input. Its been well over 12 hours and still at this step. The server appears to be very underutilized at the moment, only using around 2%-4% cpu and only 38% memory. Where might I find the CTI handling setting? If you need anything from me, please let me know.
