→ 🚀What's New? Explore Lansweeper's Fall 2024 Updates! Fall Launch Blog !
Monday
An ongoing issue from Friday that we are waiting for senior support for:
Our Lansweeper on-prem stopped working Friday morning. Logging into the server, the Lansweeper Service was stopped. Trying to restart it did not work, it went to "restarting" then back to "stopped." IISExpress and LansweeperLocalDB were both running. We had this issue in September and rebooting the server helped. This time, it did not work. Following support instruction, we attempted to upgrade the installation which failed and threw an error about the Lansweeper Service not being found. Checked the server, and Lansweeper Service is missing from the Windows Services menu and LansweeperLocalDB is stopped. Tried to restart it and it stays at stopped. We were then told to try installing using the "Easy" install method after moving our backup files. This did not work and threw the "Lansweeper LocalDB Service install failed. ErrorID: -1" error again.
Infrastructure was able to bring the LocalDB back up and running, and we attempted the reinstall of Lansweeper once more, only to have the error for Lansweeper Server come up and the install failed. Lansweeper Service is still missing and LocalDB cannot be started again (IISExpress can be started and stopped without issue). We have a renewal coming up and it's hard to pitch renewing when we can't use the service we are paying for. It's been 3 days now and from scouring the forums, it does not appear anyone else has had this issue before. If so, I'm hoping someone who had this happen may have a possible solution.
Thanks!
Solved! Go to Solution.
yesterday
We ended up fixing the issue without support. Just know this list doesn't include the pain and tears figuring this all out and it also doesn't include the steps tried. Here's what worked after we followed what Ls Support initially had us do (which was easy install Lansweeper):
Upon Login:
1. Performed fresh install of Lansweeper Service. Failed due to being unable to start Lansweeper DB Service.
2. Adjusted permissions for lansweeperuser (gave local admin)
3. Performed fresh install of Lansweeper Service. No issue.
4. Restored lansweeper database from the 11/10 .bak
5. Attempted site startup. Failed to connect.
6. Performed fresh install of Lansweeper Website
7. Edited IIS configuration file to match previous configuration file
8. Edited IIS configuration file to match the bindings of our Lansweeper Site
Issue resolved
yesterday
Hello Rinks,
Can you check if the account under which the LocalDB service runs has the "logon as service" permission?
Another common problem could be that the the database files of your LocalDB are not located on in the SQLDARTA folder in the Lansweeper folder structure.
You can check the file location of the database files in SQL Server Management Studio.
It might be a good idea to open a Support case. The Support team can review your log files and identify the root cause of the failing service.
yesterday
We ended up fixing the issue without support. Just know this list doesn't include the pain and tears figuring this all out and it also doesn't include the steps tried. Here's what worked after we followed what Ls Support initially had us do (which was easy install Lansweeper):
Upon Login:
1. Performed fresh install of Lansweeper Service. Failed due to being unable to start Lansweeper DB Service.
2. Adjusted permissions for lansweeperuser (gave local admin)
3. Performed fresh install of Lansweeper Service. No issue.
4. Restored lansweeper database from the 11/10 .bak
5. Attempted site startup. Failed to connect.
6. Performed fresh install of Lansweeper Website
7. Edited IIS configuration file to match previous configuration file
8. Edited IIS configuration file to match the bindings of our Lansweeper Site
Issue resolved
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now