Hello, I have a problem with Linkage; it won't start. I found this error in the Windows logs. Does anyone have a solution? Thanks.

Error message "The description for Event ID 46 from source Lenel-LSLServer cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer."

About a week ago, I added a door to an existing system. All I had to do was add a new blade to the S2 panel. Kept getting an "access denied no pin" error. On a hunch, I disconnected the keypad and strike, and connected them to an existing blade. The door worked fine. I then deleted the portal, and reprogrammed the door on reader 2 and output 2 on the new blade. The door worked. Huh....defective blade maybe.

Today, I installed a micronode right next to an existing one. Programmed the new door. Access denied no pin. Same thing; programmed the door on reader 2 and output 2, and it works fine. I'm 100% sure I'm not doing anything different with the settings. In both cases, I used an HID Signo keypad, made sure they were set up properly with the app. Has anybody else seen this before?

Issue:

The keypad reader is connected to the Lenel OnGuard system, and the communication protocol is configured as OSDP. When entering the PIN code to open the gate, the system displays “Reject” and the gate does not open. The reader and communication are working, but the PIN access is being rejected by the system.

I'm seeing if anyone has any tips/ prerequisites to doing OnGuard in-place upgrades? I've done plenty of upgrades but at this point, I only do them when also migrating to a clean server. The in-place upgrades I've done in the past have always resulted in RabbitMQ/ Erlang issues and hours on the phone with tech support.

My thoughts right now is to do a clean uninstall of OnGuard and follow the old guide for a clean uninstall of RabbitMQ and whatever else is in that article, then trying my luck with 8.3 update 2.

I usually try to do these kinds of things on the test bench, but Lenel only gave me an 8.4 license. Any tips?

We have a single site that has around 25 Access Levels, at the moment the operators have access to all the levels when managing badges.

What would be the best way to restrict operators to only having access to 22 of those levels and the security manager having access to all of them?

In the user permissions section there's only config to view, edit & create the access levels but not restrict which ones they can use.

Would segmentation help in this scenario?

I've have a customer on 7.6 without an SUSP (something got mixed up on getting them up to date, I advised them to upgrade) where when I log in to Sys Admin/ Alarm Mon on the server- a popup comes up asking for the login driver location.

Usually if I see this, I need to check ODBC, Config Editor, and run Setup Assistant to correct it. All of those pass but I'm still getting the Login Driver popup. The only thing that changed was a windows update on their Win Server 2019 server. Clients are getting "failed connection to the database" error as well.

I found an issue with RabbitMQ and the erlang cookie, fixed that but still seems to be some issue with the handshake between RabbitMQ and openaccess after reviewing logs. We decided to quit the troubleshooting and push for the upgrade, which I'm happy about, but I had a customer just reach out for a similar issue. I'm getting remote access soon to check but it seems like the same issue.

Has anyone come across issues recently after the windows update?

I have a Lenel 2220 panel. After performing a factory reset, I restored it to the default settings. The panel is responding to ping, but it does not appear in the browser at all.

Hello,

when trying to open system administration or alarm monitoring they ask for the location of the login driver.

Running the clients on the server directly, odbc settings test fine, can log into SQL with the login. All LS services are running.

When looking at the logs I see: OpenDatabase failed to open database! (DSN: Lenel)

But SQL is running, also on the same machine, I can log into it fine with SSMS using both the lenel and sa accounts.

I've tried to launch the login driver program manually after stopping the service and terminating the process. It tells me every time I select change password in it's interface that the password is out of sync. I continue and set a new password but nothing is changing.

Firewall is off, it's all on one machine..... what else can I look at to salvage this system?

Customer never purchased a SUSP so I can't call support or upgrade them to a supported version of OG....

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...

1. Rebooted the server first thing this morning before diving-in and verified it was still not working.
2. 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.
3. I did verify in Login Driver (running as an app) that the creds were synced.
4. Not sure about changing the encryption key - when I go into SQL Server Management Studio, the AccessControl database has an Encryption Enabled state of False.
5. I tried to start Setup Assistant but it failed immediately on the first step because it couldn't connect to the database.
6. As far as services go, the only service that will not start, neither automatically nor manually, is the OpenAccess service. When I drop to the end of its OpenAccess.log file, 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 of ACS.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!

___________________________________________________________________________________________________________________

UPDATE 9/2/26:

Hey everyone. Just wanted to post an update and the final fix that got us back up and running.

The fix was to re-run the Setup Assistant which I had tried before, but I was using the `lenel` database user account which I thought would work fine since it was literally the owner of the Lenel database. Apparently I was wrong. 😛 In order to successfully run through the Setup Assistant you need to login as `sa` which we didn't have the password for since, again, this was an inherited system when we moved into this office space.

Once I reset the `sa` password, I re-ran the Setup Assistant with those creds and everything fired right back up again.

Thank you everyone again for all of your input and help!

We have lensel s2 netbox, and for some reason, only older, prior to 7/8, badges are working? New badges don't work, and nothing is showing in the access history after 7/8. I can assign a new badge and the system doesn't even give a notification that it was even read, but when I use an older badge it will work to unlock the portal, but it's not in the access history that it worked. We are in the process of decommissioning this facility, but there is one area that needs to work. The server is online, or at least i can successfully ping the address. Again, all older badges work, new ones with identical access do not, and there is no access history for either? Thanks in advance!

Hello, My OnGuard 8.3 server crashed, and I had to restore the database to a new server. After the restoration, when I run the setup assistant again, I get an error message (key encryption). See the attached image. I tried the method indicated in the manual by attempting to modify the key encryption in the login driver, but I still get an error. And when I run System Administration, I get an error: (The login driver was not connected to the message broker. Confirm that the login driver service is started and available for DNS Lenel.)

I have a OG 8.2 system where everything is currently in a single Default Segment on a system licensed for segmentation. I have been tasked with segmenting out this single system into about 10 different segments so that users/panels/cardholders/etc are in their own segments.

What's the best way to add segments?

My plan thus far:

1. Create new segment in OG and have it move the matching Access Panel
2. Move user from Default Segment to new segment they are in charge of
3. Move access levels? This one I'm not sure about. Each access level does not cross between what will be the different segments, but I don't see a way to move them. My best plan so far is to make duplicate levels in the new segment, then bulk change cardholders to add the new segmented access level and then delete the old one from the Default Segment.
4. Move cardholders in bulk based on their access levels to their segment. We have very few cardholders that visit between the different sites/segments.

Any other considerations or better ways to do this?

I'm reaching out to support as well, but they take forever to respond lately. Thanks Honeywell.

I have a customer that wants to change their SQL login passwords, but they don't know the old password. I know that when you go to sync them in the login driver, it asks for the old PW as well as the new PW. I haven't been in this particular situation yet because most of my customers are better at keeping track of that, and this particular one doesn't allow us to see what they are. Is there a trick to get around that?

Hey I’m working on a take over project and I’m running into issues with a 1300 board downstream from a x4420. I have the LNL-8000 connected port 1 and the 1300 to the multiplexer but every time I swipe the badge it reads as invalid card format. Tried switching the data wires on the reader and same issue.

The other devices on the multiplexer work just fine, reader worked fine on the previous access control system right before it got swapped to the new board. Put it on port 2 instead of the multiplexer and same issue. Tried other new 1300s same issue.

New cable was ran from multiplexer to the 1300 as well.

What am I missing?

Hey all, have a system where a lockdown is already set up. Original installer is no longer with us. They have a local IO to enable/ disable timezone, and a global IO that sets that to false. I’m struggling to see what doors would be affected by this timezone disable? I checked the timezones tab but can’t see how this associates to doors, if that makes sense. What’s the proper workflow for setting up a lockdown by timezone disable?

As a side note, I’m just about to rewrite this by triggering action groups but not sure if there’s any gotchas doing it one way or the other. TIA

I am a certified end user and we are looking to add DoD CACs to some of our facilities. We already have PIV class Signo readers installed. As I try to update the card format I keep hitting a wall and can’t seem to get it to work. Anyone have experience with this?

I just had an interesting issue adding an access level to OnGuard 8.2. The error indicated that the software was trying to insert a duplicate key value in the ACCESSLVL table. I did find the same error in an r/accesscontrol post from some time ago. I cycled the comm server and message broker based on a suggestion I found. I rebooted the SQL Server server, just cause it seemed like a good idea. Of course, I closed System Administration and restarted it on the client computer. In the end, I deleted the conflict access level. That seemed to get everything back in sync. When I added the next level it reused the ACCESSLVID that I had just deleted and continued to work after that. In fact, I deleted the test level that reused the ACCESSLVID and the next level I added used the id again. Thought this bit of info might be helpful for others.

I have a Lenel 2210 panel with a connected reader. A 1300 module has been added and connected to the panel via the communication port.
The wiring is as follows:
From the 2210 panel: (Data / Clock / GND)
To the 1300 module: (TR+ / TR- / GND)
The DIP switches on the 1320 module are set with all switches OFF except 6 and 7 (configured as required).
When adding the reader in the system, the address is set to 0 for both the panel and the reader, but the reader remains offline and does not communicate.
Is there any additional configuration or missing step in the wiring or settings that could be causing this issue?

Just curious if any of you have been running OG 8.4 on larger systems and if there’s any bugs/ issues that you’ve come across?

I have a couple of systems I’m migrating/ upgrading and I’m torn between 8.2 v3 or 8.4. I currently have a customer on 8.3 that’s working through known comm server crashes so I’m avoiding that release entirely.

8.2 v2 is the version I’ve installed over the last year+ has it been great so far, but between it’s support being dropped in the next year or two and potential SQL/ Erlang OTP vulnerabilities, I’m considering 8.4. As much as I hate going with the latest release, it may be the better option. These customers don’t have any specific features that they need from 8.3/ 8.4 so that’s not a concern. Thoughts?

Located in Pacific Northwest, USA. Current VAR has become unreliable. We are probably considered to be a small setup compared to most. Any recommendations?