Skip to main content
Skip table of contents

Upgrade from 3.7.x to 3.8.x/3.9.x

Version 3.8.x introduces the following new functionality:

  • Better support for EzeScan Cloud.

  • User defined values for user profiles.

  • Consolidated auxiliary databases into single storage database.

  • Remote Indexing Assistant (RIA) indexed items recycle bin.

  • Digital Forms Assistant (DFA) history events.

  • Digital Forms Assistant (DFA) client side saving of saved form tokens.

  • Digital Forms Assistant (DFA) ability to email saved from tokens.

Upgrade Steps

If you require assistance upgrading your installation then please reach out to our support team.


Download the latest version of EWA from our website.


Extract the zip file to a temporary location.


Stop IIS application pool.


Backup databases in SQL Server Management Studio.


Browse to the location of your EWA installation in windows explorer.


Backup your EzeScan WebApps installation files.


Record any customisations applied to the web.config file.


Remove all of the files except the App_Data folder and the appsettings.json file.


Copy 3.8.x installation files into EzeScan WebApps directory.


When asked if you want to replace or skip the files with the same names, be sure to click the Replace option.


Decide which way you with to proceed with changes to the auxiliary databases.

After upgrade this version takes our 6 small auxiliary databases and combines them into one.

This one “storage” database can be kept as SQLite or migrated to SQL Server as part of the upgrade process.

Upgrading the “storage” database to use SQL Server is recommended for optimal performance.

Please expand and follow one of the following options:

Option 1 - Use continue to use SQLite for auxiliary database.

Add TrustServerCertificate=True to your existing connection strings in the appsettings.json file.

Option 2 - Migrate auxiliary databases to MS SQL Server.

Add TrustServerCertificate=True to your existing connection strings in the appsettings.json file.

From the latest appsettings.template.json file copy and add the “_storage” node that contains the new connection string to your appsettings.json file.

Modify the connection string as necessary.

Remove the underscore from the front of the “_storage” node


Reapply any customisations to the web.config file.


Start IIS application pool and navigate to the site.


Check the log file for any error messages between the "EzeScan WebApps Starting" and "Application started. Press Ctrl+C to shut down." log entries.


Confirm the storage database has been created and is in use by clicking the databases panel on the admin dashboard.

Why have the connection strings changed?

Due to underlying updates in the Microsoft SQL packages used by EzeScan WebApps encrypted communication to the database server is now enabled by default.

If your database server doesn’t have a certificate signed by a trusted CA (e.g. using the default built in self signed cert) then your connection strings will need to force your server to trust the database servers certificate.

If your IIS server doesn’t trust your database servers certificate you will see a log entry like: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.

This can be achieved by adding the following setting to the end of the connection strings:


So for example the following connection string:

Server=.\\SQLEXPRESS;Database=ezescan.webapps.indexing.event;Integrated Security=true;

Would become:

Server=.\\SQLEXPRESS;Database=ezescan.webapps.indexing.event;Integrated Security=true;TrustServerCertificate=True;

If your MS SQL installation runs on the same server as IIS then the above solution is perfectly acceptable as network traffic is never leaving the box and is therefor not susceptible to man in the middle attacks.
If you are using MS SQL hosted on a separate server then the recommended approach is to configure the MS SQL Server with a valid certificate that is trusted by the IIS host.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.