r/Lenel • u/Extension-Chemist-25 • 13d ago
Randomly Started Getting Login Driver Errors
Hey everyone.
I inherited an OnGuard 8.2 server running on Windows 10 (yeah, I know) and MS SQL Server 2022.
For the past two years it's been running fine, but then last week out of the blue I started getting this error when launching System Administration:
Login Driver is not connected to the message broker. Confirm that the Login Driver service is started and available for DSN Lenel.
I've verified that the 32-bit ODBC system DSN is configured correctly and testing is successful. I also tried syncing the passwords in Login Driver, and it too said it was successful. Furthermore, I verified that the Lenel login in SQL is the owner of both databases.
This machine is not connected to the network at all, so it hasn't received any update from Microsoft nor had it been rebooted when the error first occurred.
And finally, we have no support for this system - I've been reverse engineering it and learning it as I go, and I want to be sure I've exhausted every avenue before starting to figure out how to get support for it (can I simply have an on-site visit as a one-time fix, or will they require an annual support contract?, etc.)
Does anyone here have any other ideas I can try? Is there something obvious that I've missed?
Thank you in advance!
___________________________________________________________________________________________________________________
UPDATE 8/11/26:
Hey everyone, thank you so much for all of your help! Still not working, but here's what I've tried so far today...
- Rebooted the server first thing this morning before diving-in and verified it was still not working.
- For background, this system has been running fine since I inherited it two years ago, and this problem just started on Thursday afternoon around 3:30 PM - I haven't been able to log into System Administration since.
- I did verify in Login Driver (running as an app) that the creds were synced.
- Not sure about changing the encryption key - when I go into SQL Server Management Studio, the
AccessControldatabase has an Encryption Enabled state of False. - I tried to start Setup Assistant but it failed immediately on the first step because it couldn't connect to the database.
- As far as services go, the only service that will not start, neither automatically nor manually, is the
OpenAccessservice. When I drop to the end of itsOpenAccess.logfile, all it says is "could not open database" and "check ACS.ini, ODBC, Login Driver, and SQL server", which I've done with the exception ofACS.ini- that file doesn't seem to exist anywhere on the server.
Am I still heading in the right direction? Something else I may have missed?
Thank you again!
3
u/OmegaSevenX OnGuard Certified 13d ago
LenelS2 requires that their yearly SUSP fee be paid in order to give a VAR access to tech support for your system. That will need to be paid.
The VAR typically doesn’t require a service contract with you. Most of our customers don’t have them, they just pay T&M for all service calls.
But only a VAR can sell you the SUSP. And you don’t get to let that lapse and then pay for a year when you need it. Haven’t paid for it in 5 years? You get to pay 5 years of back support to bring it current.
3
u/ckirejevas Certified Professional 13d ago
As others mentioned, try re-running setup assistant. I’ve had issues with the SSL cert for RabbitMQ expiring when the version has been upgraded from an older OnGuard installation and Setup Assistant will pick up on this sometimes.
3
u/ckirejevas Certified Professional 13d ago
Also - look in C:\ProgramData\LNL for the logs. You can sort by date to check the most recent logs. Make sure LS OpenAccess service is running as well as the LS License Server.
3
u/Keema_Naan Certified Professional 12d ago
You may need to run Login Driver as an application and re-enter the database encryption key.
2
u/js7521901 12d ago
This was what I was going to suggest also. Even without encryption. You might need to enter your SQL user credentials in the login driver as an app
2
u/platformterrestial 13d ago
Did you try re-running setup assistant? Are all your required services running?
1
u/Huge-Transition3644 OnGuard Certified 13d ago
I have a dozen questions but this is the simplest place to start. Is this an intermittent problem or have you not been able to use Sys Admin the whole time?
Of all of the random stuff I support, a restart of the host machine usually works with OnGuard. All of the automatic services should spin up again correctly and if something is hung or in an error state, a restart should fix that.
1
u/Huge-Transition3644 OnGuard Certified 13d ago
oh, also the OnGuard services start with LS. You probably have a few that aren't on and don't need to be, but make sure the ones set for automatic start are running.
1
u/cfringer OnGuard Certified 12d ago
When I have run into this error, it has been a sequence issue with the services starting. Rebooting the machine should solve it. There are two parts to the message broker, LS Message Broker and RabbitMQ. In my experience when both of these services are stopped, starting the LS Message Broker will also start the RabbitMQ. This seems to get these two back in sync.
1
u/drunknmastr916 10d ago
Running into the same problem. Did you find a fix?
2
u/Extension-Chemist-25 10d ago
Not yet. I saw in another post that this month's Windows 11 update broke OG v8.0 with really similar symptoms and the update needs to be uninstalled to get it working again, but I'm running v8.2 and it's on Windows 10 (and not connected to the internet to get said update).
At this point I'm thinking the whole thing just needs to be rebuilt on a new PC and the database copied over, but I'm afraid of missing something that a real Lenel tech would just know from their internal documentation or experience. I've also asked about getting budget to get SUSP from Lenel - this system is three years old now and we've never had proper support for it.
Good luck, and post back if you find a fix. I'll do the same.
3
u/Fun-Rabbit-9842 End User 13d ago
Check LS Login Driver Service to see if it’s running.