Linkedin
Facebook
Whatsapp
Whatsapp
We recommend that you only carry out this operation during system downtime or while Lasernet is not in use, receiving no new input.
If you change the user on the service you will see this error in the Lasernet Monitor:
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 Taskmanager and stop sqlservr.exe processes associated with LocalDB.
4. Right-click Properties to choose the right process.
In the example below, there are two associated processes with LocalDB (service and config), there is also one more process that is associated with the SQL Express install.
5. Clear all folders indicated in the following screenshot:
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.
6. Open Services, Locate the file and right-click it, the menu will then display. Select Properties from the list.
7. Change 'Log on as' to the new user, then start the Lasernet Service as this new user.
8. Start the Lasernet Config service (if on the same server).
9. Check that there are no errors within the Lasernet Monitor after starting the service. You may need to select Fetch newest.
10. 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).
Add a comment
Please log in or register to submit a comment.