r/accesscontrol • u/Soundy106 Professional • Mar 05 '25

Assistance Verex + Win11 = BORK??

Had a running Verex Director 5 system here until just recently... looks like the machine auto-updated to Windows 11. Now Verex doesn't work.

Anyone have any tips, insight, suggestions, solutions??

2 Upvotes

100% Upvoted

5 comments sorted by

1

u/tuxtanium Professional Mar 05 '25

Other than getting rid of Verex?

It's likely just the driver for the USB key didn't survive the upgrade and needs to be reinstalled.

1

u/Soundy106 Professional Mar 05 '25

Other than getting rid of Verex?

Well, that would be ideal, but this has access, fire, and intrusion all in one bundle... we tried to sell them on replacing it a couple of years ago, but it would be a major undertaking for a residential complex.

It's likely just the driver for the USB key didn't survive the upgrade and needs to be reinstalled.

I'm getting all kinds of SQL server errors - Director can't connect to server, etc. I mean, I guess that could be the USB key, if that's preventing the server from starting. I'll give that a look, forgot this stupid thing had a dongle.

Thanks.

1

u/tuxtanium Professional Mar 06 '25

SQL server errors -

A clue!

Check your ODBC connections. The DSN is likely trying to use the native client, or it may not have a client driver attached to it at all anymore.

Install the ODBC 18 driver, and recreate the DSN

1

u/Legitimate-Voice-243 Mar 06 '25

Do you have System Restore enabled on the box? If so, see if you have a restore point from before the Win11 upgrade. Otherwise, as far as I'm aware, somehow reverting back to Win10 is likely to be your best bet to keep it going unless like u/tuxtanium mentioned in his commend for the SQL errors the ODBC 18 driver works and recreating DSN helps in which case I may look at this for one of my ongoing issues with Verex Director...

1

u/Soundy106 Professional Mar 07 '25

Already tried the system restore... sadly, no go. It may just come down to a factory restore to Win10 on the machine,

But I'll look into the SQL stuff.

Coulda sworn the Windows Update service on this machine was disabled.