The site's display name is what is displayed in the site picker drop down, to the right of the LFDS logo. You can also see it in the URL when navigating to the overview page of the licensing site: https://myLfdsServer.domain.com/LFDS/#!/myLfdsServer/myLfdsSiteDisplayName

Ok I thought so, this error is not accurate. After trying again and again with what we thought was the correct display name, we re-installed forms. Then after re-entering the DB connection info into the fresh install config, it pulled the same LFDS Auth config we already had been trying to work with and connected just fine, accepting the display name we were trying the whole time, since it was saved to the database.

This error happened after the display name was forcefully changed due to an error in DS that the display name already existed, but without the specifics of where it exsisted. The customer got this message and said the only option was to enter a new display name. After the customer changed the DS display anme it did not tell them they should go to their forms config and update it, but they found the forms config and updated it to match, yet it would not accept until we re-installed the entire product. Something is wrong here.

When you say that the customer ran into the "display name already exists" error in LFDS, what were they trying to do? Create a new licensing site? If so, they do need to re-license Forms from the new site in order to get Forms to connect to the licensing site.

It is true though that the error string isn't very helpful in this case. Forms is likely complaining that you are trying to connect it to a licensing site that it wasn't licensed from.

They were just updating the SQL connection credentials, it sounded familiar to me as well, I remember running into the same thing.

It seems when you try to change the SQL connection info it suddenly says that the site name your using already exists, well of course, we are not creating a new site. Yet it will not let you continue unless you change it. Yet there should be no reason to be changing the site name unless you want to or specify to.

Did they use the "Modify connection string" UI in LFDS to update the SQL connection? Or did they detach the licensing site and re-attach the same database with the new credentials?

I was not there to see it myself but they said the only option was to detach, that also sounds familiar to me, when the connection fails I seem to remember it only gives one button called Detach.

I was working in an older version at the time it happened to me, but they are up to date with the 11.0 build. Can't say for sure without seeing it myself.

Ah I see, so the connection failed before they tried to update the connection string. They likely ran into bug 355208 where the detach button does not work when a database is unreachable. This has been resolved in LFDS 11 Update 2 (11.0.2204.1467). In the future, detaching should work successfully in this scenario and they will be able to re-attach without changing the display name.

Ok well that explains why they had to change the site name, but not why Forms would not accept the new name and had to be re-installed to accept it.

Unless what your saying about the license is true and Forms does not accept new site names. There really is no option to re-license with DS without manually replacing hidden files.

As far as I can tell, there are two places where the old display name may have been hiding: 1 ) in the Forms application license, and 2) in the Forms config (which they were unable to set in the UI, probably because of the outdated license). Did the customer re-license Forms manually after the display name change? You can see the licensing site name value in an app license under the LFDSRealm attribute like this:  LFDSRealm="myLicensingSiteDisplayName".

Well the re-install actually re-licensed Forms since we uninstalled, then re-installed from scratch, so that is why it could explain it. The license is not stored in the database and gets reset on a new install.