I am getting a prompt to re-enter the SQL server information, but when I do I am told that my licensing site already exists. Where do I go to view my existing licensing sites? There is no other tabs or menus.
Question
Question
Directory Server - How do you view your licensing sites?
Answer
First, it's possible you're running into a variant of Known Issue KB 1014252: Windows Authentication fails due to an incorrect automatic setting in the UserSettings.config file
Try the Resolution steps listed there first.
If that doesn't do the trick, from the server hosting LFDS:
Go to C:\ProgramData\Laserfiche\LFDS, make a backup copy of UserSettings.config somewhere, then delete it. Restart the LFDS service and try again. If prompted to enter the licensing site name again, make sure you use the exact name as before.
If that still doesn't work, also backup and delete connections.config from the same folder, restart the LFDS folder, and try again. Same note about ensuring an exact match for the licensing site name as before.
Together those are a full reset of saved connection properties and one or the other should do the trick.
Turns out it was the UserSettings.config or the Connections.config. I had to back these up and remove them to resolve being able to update the SQL credentials (another issue). It seems someone might have tampered with these text files. Sure enough it no longer says my licensing site already exists when I use the correct display name.
I learned that even though it says "Display Name" you can never change this name without breaking other systems.
Thank you!
Welcome! Glad that sorted it out for you!
What made the licensing site names click for me was thinking of them like a repository name. And in a sense, they are. A licensing site is like an "LFDS repository" for users, applications, and licenses.
Application lf.licx licenses include a <Site> node with what's effectively a LFDS connection profile. Looking at one makes it clear why changing the name in LFDS breaks other Laserfiche applications, just as changing a repository name would break a Workflow connection profile.
<Site xmlns="http://laserfiche.com/namespaces/license" Guid="<GUID>" LicenseServer="lfds.example.com" LicenseDatabase="<LicenseSiteName>" LicenseServerListeningPort="5048" LicenseServerListeningSslPort="5049" LFDSRealm="<LicenseSiteName>" id="Site">
Ah, I was thinking this was pulled from the database when using the attach option and Display Name was just a display for me to see.
How is it you can have more than one licensing site if you can only have one database?