---
title: "Clear Out FailedJobs, Temporary Files, and Database LN10"
slug: "clear-out-failedjobs-temporary-files-and-database-ln10"
description: "It might sometimes be necessary to clear Lasernet database and temporary files. The reasons can vary, but the main examples are shown in this article. "
updated: 2026-09-01T10:38:25Z
published: 2026-09-01T10:38:25Z
canonical: "kb.lasernetgroup.com/clear-out-failedjobs-temporary-files-and-database-ln10"
---

> ## 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.

# Clear Out FailedJobs, Temporary Files, and Database LN10

**Applies to:** Lasernet Core 10

A clear-out of the Lasernet database and its temporary files may be necessary due to:

- Too many FailedJobs slowing down the Lasernet application
- A Lasernet job stuck in a loop, causing Lasernet to crash persistently

## Clean Up Lasernet

> [!WARNING]
> Warning
> 
> Following this procedure will remove:
> 
> - All active jobs
> - Any jobs paused for the Lasernet client

Follow these steps:

1. Ensure all inputs are paused, and no jobs are running through Lasernet.

> [!NOTE]
> Note
> 
> If necessary, wait for all jobs to finish processing. You can check their statuses using Lasernet Monitor.

1. Close all Lasernet applications.
2. Open Windows Services and stop the Lasernet 10 and Lasernet Config 10 services. Alternatively, end them using Task Manager.

> [!TIP]
> Tip
> 
> Note the service name before you stop it.

1. Open Task Manager and end the `sqlservr.exe` task.

> [!NOTE]
> Note
> 
> This is the process handling LocalDB for both service instance and config. Because it is not a service, it cannot be stopped via Services.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-UCON8X28.png)

1. Clear the folders highlighted in red in the screenshot below, then restart the service.

> [!NOTE]
> Note
> 
> Open the `ProgramData` folder (for example, navigate to `C:\ProgramData\Formpipe Software\Lasernet 10\Service`). Then, open the subfolder for the service name. This will differ depending on what you have named your service.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-W9UF4V0E.png)

> [!NOTE]
> Note
> 
> - The `Programdata` folder might not be visible because it may be hidden. In that case, type “Programdata” in the **Search** field.
> - The `Databases` folder only contains information about FailedJobs, ScheduledJobs, and PauseJobs. It contains no information about the Lasernet Configuration.
> - If you use SQL Server as a database for running jobs, delete or rename the database using your preferred SQL tool.

1. Open Windows Services and restart the Lasernet 10 service, then restart the Lasernet Config 10 service.

> [!NOTE]
> Note
> 
> The service database will be re-created in the `Databases` folder.

1. Resume the inputs, if any.

Lasernet will now be up and running again.

## Troubleshooting

If you are still experiencing issues after following the steps in the previous section, clear the running configuration loaded to the service.

Follow these steps:

1. Repeat steps 1–5 from the previous section.
2. Open the `Configuration` folder and delete any files and folders inside it.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-4O6D7FLC.png)

1. Repeat steps 6 and 7 from the previous section.

The service will start without the configuration loaded in Lasernet Monitor, as shown:

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-0RWEUAC9.png)

1. Commit and patch the configuration from Lasernet Developer to reload the configuration to the service.