This article applies to Lasernet 9. For Lasernet 10, please refer to Clear out FailedJobs, temporary files and database (Lasernet 10)
On occasion, there may be a need to clear Lasernet database temporary files. The reasons can vary, but predominantly they are:
There may be many FailedJobs slowing down the Lasernet application.
A Lasernet job keeps running through stuck in a loop and persistently causes Lasernet to crash.
Follow these steps to clean up your Lasernet application:
1. Ensure Inputs are paused as you don't want to clear the database with jobs running through Lasernet. Wait for the jobs to finish processing through Lasernet (check the Lasernet monitor).
2. Open Services and stop the Lasernet service or end it via Task Manager.
3. Clear the folders marked in red boxes in the screenshot below and start the service again.
The databases folder only holds information about FailedJobs, ScheduledJobs, Pausejobs, etc. There is nothing about the Lasernet configuration. If you use SQL Server as a database for running jobs, you will have to delete/rename the database yourself via your preferred SQL Tool.
4. Start the Service back and you should see the service database re-created.
5. Resume any inputs.
Clear the configuration
If the above hasn't solved the issue then you can clear the running configuration loaded to the service. In that case, open the CurrentConfiguration folder and delete the files and folders marked below:
Then Commit/Patch from the Developer to reload the configuration to the service.
Add a comment
Please log in or register to submit a comment.