We use load balanced servers for our Laserfiche we applications. This week I installed Laserfiche Forms 12 Spring Release on the servers while upgrading from version 11. I only opened the FormsConfig page on the Primary Forms server so it could update the database. This morning when I tried to access Forms it sent me to the secondary server in the LB and I received an error saying that the repository was not configured. After looking at a few things I decided to log into the secondary server and open the FormsConfig page and go to the User Authentication tab. After it successfully loaded, I tried to access Forms again and it worked. Is this a bug or a new requirement?
Question
Question
Is it required to go to the FormsConfig page for each server Forms is installed on?
Replies
It's a quirk of FormsConfig being the entity that sets/updates a variety of necessary properties in the Forms web.config file on the first load/activity post-upgrade. It does seem to require some form of activity like going to a different tab to trigger. I've meant to diff the web.config before and after first FormsConfig to see exactly which parameters get set/updated to see if it could be done by other means. The params likely change version to version though, so that wouldn't a stable method.
So, the answer is probably "Working as designed, but it's an odd quirk".
You always have to go to FormsConfig after a new installation to set the database connection properties.
Hi Blake, do you use LFDS or LFS authentication? I will try reproduce the issue and see whether we can improve on this.
We use LFDS authentication.
I can reproduce the issue and have filed bug for it (#586582).
The cause was that some of the LFDS settings in the config file were not preserved during upgrade. Open User Authentication page after upgrade is the current expected workaround.