---
title: "How Do I Read the Lasernet Logs? - Frequently Asked Questions"
slug: "how-do-i-read-lasernet-logs"
description: "At first glance, Lasernet logs may appear somewhat confusing, especially if you have not been exposed to log files before."
tags: ["Lasernet", "Lasernet logs"]
updated: 2026-09-10T13:21:12Z
published: 2026-09-10T13:21:12Z
canonical: "kb.lasernetgroup.com/how-do-i-read-lasernet-logs"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.lasernetgroup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How Do I Read Lasernet Logs?

Lasernet log files record what is happening as jobs are processed, but the format is not self-explanatory. This article covers how to view the logs, how to read their columns, how to add your own entries with a script, and how to solve common errors displayed in them.

## Viewing the Logs

Lasernet log files can be viewed in real-time in Lasernet Monitor.

Alternatively, the log files, which have the file type `.lnlog`, can be read directly using standard tools. See: [Where Do I Find the Lasernet Logs?](/v1/docs/where-do-i-find-the-lasernet-logs)

## Understanding the Logs

The logs have eight columns, separated by semicolons. They represent:

1. Server Name
2. Date and Time
3. Module Name
4. Type ID of message, some examples are:

- 0 – Starting/Stopping Service Details
- 1 – Uploading Build
- 2 – License Details
- 10 – Normal processing
- 11 – Running Script
- 12 – Creating a JobInfo

> [!NOTE]
> Note
> 
> For more information, see **Section 4.1.4.2** of the [Lasernet Developer Guide](https://lngsupportdownloads.blob.core.windows.net/lasernet/Documentation/Lasernet_10/Lasernet_Developer.pdf).

1. Thread ID
2. Not relevant
3. JobID
4. Message

Use the Thread ID, JobID, and Module Name to trace work through the system. When work is passed from one module to another, the JobID changes, but the Thread ID stays the same. Lasernet writes a message in the logs like the following:

`Passing job TECH018_FILE_INPUT_7805F9D3_6839_4BB0_A9A1_11CEF70DFD54 to XML Transformer 1`

This indicates that the job with JobID “TECH018_FILE_INPUT_7805F9D3_6839_4BB0_A9A1_11CEF70DFD54” is getting passed to a module called XML Transformer 1.

> [!NOTE]
> Note
> 
> When a job is passed to two destinations, the first destination in the list gets processed first. Only after the job is processed does it get passed to the second destination.

## Using Scripts to Add Information to the Logs

Scripts can be used within the Lasernet build to print information into the log file. For example:

`Logger.logEvent(123,"Logging Message Here " + job.getJobInfo("jobinfoName"));`

This has two parts: the Type ID and a message. The message can display any additional information you want to share. After this particular example script has been executed in Lasernet, “Logging Message Here” will be printed, along with the value of the jobinfo jobinfoName, and the message will have Type ID 123.

> [!NOTE]
> Note
> 
> Type ID values < 100 are reserved for the Lasernet service.

## Understanding Errors in the Logs

The logs can show a number of different errors. When viewed in Lasernet Monitor, errors are displayed in red text with an error-type tag.

A common error is when a job fails because a destination cannot be found. This can be caused by a misspelled destination name or by a module being removed without updating all other modules that point to it.

For example:

`TECH018_FILE_INPUT_7805F9D3_6839_4BB0_A9A1_11CEF70DFD54;Failed job`

`TECH018_FILE_INPUT_7805F9D3_6839_4BB0_A9A1_11CEF70DFD54 (Failed to pass`

`job(TECH018_FILE_INPUT_7805F9D3_6839_4BB0_A9A1_11CEF70DFD54): Destination PDFEngine not found)`

Another common error is a failure to write to a file. This can be caused by incorrect permissions being set on output folders.

For example:

`Could not write to file C:\temp\NoPerms\test.txt - failing job`

## Related

- [Where Do I Find the Lasernet Logs?](/where-do-i-find-the-lasernet-logs.md)