It might sometimes be necessary to clear Lasernet database and temporary files. The reasons can vary, but these are the main examples:

• There are many FailedJobs slowing down the Lasernet application.

• A Lasernet job keeps running while stuck in a loop, causing Lasernet to crash persistently.

This article explains how to clean your Lasernet application.

Clean Up Lasernet

Follow these steps:

1. Ensure Inputs are paused and no jobs are running through Lasernet.

   Note

   If necessary, wait for any jobs to finish processing through Lasernet. You can check status using Lasernet Monitor.

2. Close all Lasernet applications.

3. Open Services and stop the Lasernet 10 and Lasernet Config 10 services. Alternatively, end them using Task Manager.

4. Open Task Manager and end the sqlservr.exe task.

   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.

   

5. Clear all folders indicated in the following screenshot:

   

1. Go to Services and restart the Lasernet 10 service first, followed by Lasernet Config 10.

1. Resume inputs, if any.

Lasernet will now be up and running again.

Troubleshooting

This section applies if you still have a problem after following the steps in the previous section.

It is possible to clear the running configuration loaded to the service. Follow these steps:

1. Repeat steps 1–5 in the previous section.

   
   

2. Open the Configuration folder and delete the files and folders.

   

3. Repeat steps 6 and 7 in the previous section.

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

1. Commit/Patch from Lasernet Developer to reload the configuration to the service.