---
title: "Change a User for the Lasernet Service when Using a LocalDB"
slug: "change-a-user-for-the-lasernet-service-when-using-a-localdb"
description: "When changing the user on the service, an error will occur in the Lasernet Monitor. Follow the steps highlighted in the article to resolve the issue."
updated: 2026-03-05T13:25:50Z
published: 2026-03-05T13:25:50Z
canonical: "kb.lasernetgroup.com/change-a-user-for-the-lasernet-service-when-using-a-localdb"
---

> ## 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 Change a User for the Lasernet Service when Using a LocalDB as the Backend?

**Applies to:** Lasernet Core 10

> [!WARNING]
> Warning
> 
> We recommend that you only carry out this operation during system downtime or while Lasernet is not in use, receiving no new input.

When changing the user on the service, this error will occur in the Lasernet Monitor:

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

To correct this, follow these steps to get the LocalDB database attached to the new user:

1. Stop the Lasernet Service.
2. Stop the Lasernet Config service (if on the same server).
3. Start Windows Task Manager and stop **sqlservr.exe** processes associated with LocalDB.
4. Right-click **Properties** to choose the right process.

In the following example, two processes (service and config) are associated with LocalDB, and one more process is associated with the SQL Express install.

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

1. Clear all folders indicated in the following screenshot:

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

> [!NOTE]
> Note
> 
> - The **ProgramData** folder might not be visible because it is hidden. In that case, type it in the search field.
> - The **Databases** folder only contains information including **FailedJobs**, **ScheduledJobs**, **Pausejobs**.
> - There are no changes made to the Lasernet configuration. If you use SQL Server as a database for running jobs, delete or rename the database yourself using your preferred SQL tool.

1. Open **Services**, locate the file, and right-click it; the menu will then display. Select **Properties** from the list.
2. Change **Log on as** to the new user, then start the Lasernet Service as this new user.
3. Start the Lasernet Config service (if on the same server).
4. Check that the Lasernet Monitor does not contain errors after starting the service. You may need to select **Fetch newest**.

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

1. Reboot the server, ensuring that the Lasernet Service starts before Lasernet Configurations (Config). Within the **Lasernet Config 10 Properties**, the service can be set to **Automatic (Delayed Start)**.

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