This is relevant to CTP prepress products such as K2 or Navigator GPS.

We're going to start with the main log; the one you need to be able to send to Xitron Support for help.

XFDeBug.log

Configuring Diagnostic Logging - XFDebug

The most important log file for troubleshooting Navigator Server problems is a level 3 XFDebug log file called XFDeBug.log. If you want to give us useful logs, getting rid of the existing logs and then running a job that shows your problem will help a lot.  It gives us log files that show your problem and don't have to be sifted through for hours.


1. Get rid of old logs

First close Navigator or K2 Server and delete the following files. 


K2

C:\K2\K2\XFDebug.log

C:\K2\K2\K2Server.log


Navigator

C:\Navigator\Navigator\XFDebug.log

C:\Navigator\Navigator \XiFlowServer.log


2. Configure logging

Open the application "XFDebugLog.exe", in the Server folder. (C:\K2\K2\XfDebugLog.exe)

 

The screenshot below displays the XFDebugLog.exe menu accessed by navigating to "Configure" > "Set Levels..."

 

Each component (like "Server App", "Hot Folder", "RIP Action", etc.) has an associated logging level, and the dropdown values typically range from:

  • 0 – Logging Off
  • 1 – Errors Only
  • 2 – Warnings and Errors (default)
  • 3 – Full Debug (verbose logging)

 

The components set to level 3 (full debug logging) in the screenshot are:

  1. Server App
  2. Client App
  3. RIP Action
  4. Hot Folder
  5. RIP Output

 

These settings will generate detailed logs for diagnosing complex or particular issues. Here's what each helps troubleshoot:

 

  1. Server App: 3
  • Tracks internal server processes and communications between components.
  • Useful when the RIP server crashes, slows down, or fails to launch jobs.
  1. Client App: 3
  • Logs client-side actions and communication with the server.
  1. RIP Action: 3
  • Captures detailed information during the RIP (rendering) process.
  • Critical for diagnosing jobs that fail to RIP, are too slow, or cause unexpected errors.
  1. Hot Folder: 3
  • Monitors all file activities and errors in hot folder automation.
  • Use this when jobs are not being picked up, processed incorrectly, or mysteriously vanish.
  1. RIP Output: 3
  • Tracks how the RIP writes processed data (e.g., Tiffs) to output destinations.
  • Helps if printed files are corrupted, missing, or incomplete.

 

 

When to Set Level 3 on Other Components

Set level 3 selectively on other components only when needed, such as:


 WebServer

  • Use: Handles web-based communication between Job Submission and the K2 server.
  • Level 3 When: Job Submission fails or API calls time out.

Print Job

  • Use: Converts job to one or more TIFF images and outputs them to the Windows Print Spooler and through it to a specified printer connected to the Server PC.
  • Level 3 When: Jobs aren’t appearing in the Windows Print Spooler, go missing, or carry incorrect attributes.

Export

  • Use: To send job files from K2 to another location on the network.
  • Level 3 When: Output files are missing.

Stabilizer

  • Use: If a job errors when sent as a PostScript file, running it through the Stabilizer to create a PDF file may allow it to run.
  • Level 3 When: The action fails to convert a PostScript file to a PDF.

Preflight

  • Use: Scans incoming PDF or PostScript files against a set of rules to detect errors before RIPing.
  • Level 3 When: Use when files are unexpectedly rejected or passed without proper validation. Useful for identifying misconfigured preflight profiles or missing embedded fonts/images, as well as misapplied Pitstop profiles and actions.

Trapping

  • Use: Ensures correct overlapping of adjacent colors to avoid gaps or white lines.
  • Level 3 When: Output shows trapping errors or traps are missing entirely. Use to confirm trap zones, directions, and overlaps.

Spot Color

  • Use: Manages and converts spot colors in jobs to desired CMYK or output colorants..
  • Level 3 When: Unexpected spot color behavior (e.g., incorrect mapping or conversion) or override fails.

PDFChecker

  • Use: Validates PDFs for compliance with print standards (e.g., PDF/X). Analyzes and validates PDF file integrity, structure, and readiness.
  • Level 3 When: Files seem valid but cause errors during processing. Use to trace internal PDF issues like corrupt objects or malformed metadata.

Copy

  • Use: Copies a job or part of it to another workflow. Often used to fork proofing and final output.
  • Level 3 When: Jobs fail to appear in the destination workflow or are missing content. Use to confirm source/destination pathing and timing.

Ink Remapping

  • Use: Adjusts ink usage or swaps colors (useful in spot-to-CMYK remaps or when applying custom screen angles).
  • Level 3 When: Unexpected ink separations appear or conversions fail, or custom screen angles aren’t applied at the RIP.

Impose

  • Use: Handles page imposition — arranging pages in printing order for binding/finishing. Arranges pages for booklets, n-up, or ganging jobs.
  • Level 3 When: Layout is incorrect or inconsistent. Level 3 can reveal issues in the template application or page flow logic.

ROOMProof

  • Use: Provides output simulation for proofing workflows.
  • Level 3 When: Proof mismatches, file doesn’t represent job as RIP’d.

XiStep / XiPosition

  • Use: Controls position/steps for step & repeat jobs.
  • Level 3 When: Positioning or page-size adjustments fail, steps are misaligned or incomplete.

Step and Repeat

  • Use: Repeats a single item across media (e.g., for labels).
  • Level 3 When: When incomplete patterns, unexplained gaps, or overlaps occur.

PDF Optimizer

  • Use: Reduces file size or complexity (e.g., flattening transparency).
  • Level 3 When: Optimized files don’t render or lose elements.

PDF Compositor

  • Use: Allows Job Submission to send jobs to a particular workflow in the software Client. 
  • Level 3 When: Despite the Job Submission action in a specific workflow, PDFs do not reach the intended workflow in the software client.

 

 

 

You will now go back to the Configure menu and select Message Monitor. You will set this to Level 3 as well.

 

Once this is complete, you will now open Modules and select the RIP, server, or client action you wish to monitor. In the screenshot below, the Server App, Client App, RIP Action, and RIP Output Action are selected to be monitored.

 

3. Capture the problem data

Leave XFDebugLog.exe running, and start Navigator or K2 Server. Run jobs that show your issue. This issue will be captured inside the log files.

 

4. Send us these log files when complete.


K2

C:\K2\K2\XFDebug.log

C:\K2\K2\K2Server.log


Navigator

C:\Navigator\Navigator\XFDebug.log

C:\Navigator\Navigator \XiFlowServer.log

 

 

5. Set the logging levels back down.

Make sure to go back to XFDebugLog.exe and reset the setting levels back to 1 when complete.


Warning

Verbose logging at level 3 can:

  • Slow system performance
  • Generate unnecessary detail if not used purposefully

It’s best used temporarily during troubleshooting, then set back to level 1 or 0 once resolved.