You are viewing limited content. For full access, please sign in.

Question

Question

Do upgrades overwrite the various config files?

Forms Directory Server Web Client
Updated July 5, 2018
asked on June 15, 2018

Since upgrading to 10.2 we have had to make tons of modifications to web.config files (for WA, Forms and LFDS) as well as the various exe.config files. These were all made in accordance with official help files as well as instructions from LF support when troubleshooting tickets.

Now we have a pending upgrade to 10.3.1 and frankly I'm a bit worried that the installers will overwrite the config files and break stuff.

Can someone from LF comment on this? Do we need to back up any of the files before doing the upgrade?

0 0

Replies

replied on June 15, 2018

Those files should not be overwritten during upgrading Web Access (I can't speak to the other applications).  When we make changes, we have a custom action that writes changes to the web.config file through an XML api, rather than having the installer blindly copy the new file over.  Of course you should always have backups of modifications that you have made.

1 0
replied on June 18, 2018

Forms also should respect your changes after updating to the newest version. As Brian states, definitely keep a backup of any modifications you've made, but we do have a mechanism that updates the web.config while retaining your changes. 

0 0
replied on July 4, 2018

I'm afraid neither Forms nor Web Access respects our changes. We just upgraded from 10.2.1 to 10.3.1, and both applications completely overwrote the WCF configuration blocks in all web.config files:

C:\Program Files\Laserfiche\Web Access\Web Files\web.config
C:\Program Files\Laserfiche\Laserfiche Forms\Config\web.config
C:\Program Files\Laserfiche\Laserfiche Forms\Forms\web.config
C:\Program Files\Laserfiche\Laserfiche Forms\Forms\bin\RoutingEngineServiceHost.exe.config

They reverted to their original "localhost" values, and the identity settings were also erased.

As a result, Web Access config page now gives this error:

Forms Config page has issues connecting to LFDS:

What is worse is that the issues remain after attempting to copy the proper settings and values from the web.config files we have backed up to the modified ones.

We were hoping the upgrade would be seamless but I guess not.

0 0
View 1 previous reply
replied on July 5, 2018

Was this an upgrade or an uninstall of 10.2 followed by an install of 10.3.1?

Is LFDS operational? Forms saves its configuration to the database.

Is there a stack trace to go with the Forms error?

0 0
replied on July 5, 2018

Straight upgrade from 10.2.1 to 10.3.1.

LFDS was operational. Everything worked on the internal network.

No stack trace - I checked the event viewer. I was going to have the customer's IT department run a trace but we ran out of time and had to roll back.

The Forms database update process was a bit strange. We went to FormsConfig (on the internal Forms Server, which is what we upgraded first) and got prompted to update as usual. However, after we clicked Yes, the spinner kept spinning for 20+ minutes. I opened the browser console and saw some errors. Thinking the update had failed, I refreshed the browser page. I was able to use Forms after that but I don't know if something broke in the meantime that caused the problems with the DMZ Forms Server.

Internal Forms server was able to reach LFDS though, so I really thing it was a problem with the configs. I opened a support ticket and provided the original (backed up) config files as well as the new ones.

0 0
replied on July 5, 2018

What exactly got reverted to "localhost"?

The Web Access error indicates it reached LFDS and LFDS can't load the database.

0 0
replied on July 5, 2018

What exactly got reverted to "localhost"?

 

The endpoint URLs inside the WCF configuration section inside each web.config file. They used to point to the internal server, but after we ran the upgrade they pointed to default, i.e. localhost. It's as if we never ran the endpoint configuration utilities.

The Web Access error indicates it reached LFDS and LFDS can't load the database.

 

Well, I've had my fair share of misleading (or flat out incorrect) error messages in Laserfiche. For example, if the LF Server license is invalid and you try to login with an LFDS user, it will give a "username or password incorrect" message even if you're typing in the correct credentials. So this is probably a similar situation since LFDS did not change and it worked fine on the internal network.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...