EzeScan WebApps
EzeScan WebApps
Breadcrumbs

Installation

Windows Server Step-by-step guide

Prerequisites

  1. Please ensure your server has the minimum requirements installed.

  2. Please ensure you have the ASP.NET Core Runtime Hosting Bundle installed.For EzeScan WebApps versions 3.10.x or higher, please ensure you have the ASP.NET Core Runtime Hosting Bundle 8.0.x installed.For EzeScan WebApps versions 3.9.x or lower, please ensure you have the ASP.NET Core Runtime Hosting Bundle 6.0.x installed.Make sure you select the "Hosting Bundle" option for your respective version.


The ASP.NET Core Runtime hosing bundle must be installed after the IIS components. 

If you have installed the hosting bundle before installing IIS then please rerun the ASP.NET Core Runtime hosting bundle installer.
If you don't then you will see an error messaging from IIS saying it doesn't understand the sites web.config file.


Installation files

  1. Go to the EzeScan website www.ezescan.com.au

  2. Logon using your User ID & PasswordContact support@ezescan.com.au if you are unsure as to what this is.

  3. Go to Downloads > Software Downloads > EzeScan Webapps
    image2020-10-12_15-59-52.png

  4. Download and then extract the installation files to the Downloads folder.

  5. Copy the extracted folder to C:\ or whichever drive or folder to your liking.
    image2020-10-12_16-9-5.png

  6. Rename the folder to EzeScan.WebApps to remove the version number.

  7. Check the folder contains the application files.
    image2020-10-12_16-10-10.png

Create Application Pool in IIS

  1. Open Internet Information Services (IIS) Manager.
    image2018-2-5_5-52-37.png

  2. Right click Application Pools > select Add Application Pool.

  3. Set the following options and click OK:

    Name

    EzeScanWebApps

    .NET CLR Version

    No Managed Code

    Managed pipeline mode

    Integrated

    image2020-10-12_16-52-8.png

  4. Confirm your application pool appears in the list.
    image2020-10-12_16-53-10.png

Set Application Pool settings

  1. Right click EzeScanWebApps > select Advanced Settings...
    image2021-3-11_16-2-45.png

  2. Set the Start Mode to AlwaysRunning.
    image2021-3-11_16-4-17.png

  3. Set the Disable Overlapped Recycle to True.
    image2022-9-5_14-11-3.png

  4. Click the OK button to save the settings.

Set Permissions

EzeScan WebApps application pool’s identity needs to have read/write access to the App_Data folder in order to move files around and function correctly.

  1. Navigate to the c:\EzeScan.WebApps directory.

  2. Right click the App_Data folder and select Properties.
    image2020-10-12_17-23-11.png

  3. Select the Security Tab and then click the Edit button.
    image2020-10-12_17-23-52.png

  4. Click the Add button.
    image2020-10-12_17-24-23.png

  5. Enter IIS AppPool\EzeScanWebApps and click the Check Names button.

    Make sure the "From this location" is set to the local machine and not the domain.

    image2020-10-12_17-20-43.png

  6. Confirm the name is changed to EzeScanWebApps and click the OK button.
    image2020-10-12_17-26-34.png

  7.  Tick the Modify checkbox and then click the OK button.

  8. image2020-10-12_17-20-54.png

Setup IIS

  1. Open Internet Information Services (IIS) Manager.
    image2018-2-5_5-52-37.png

  2. Right click Default Web Site and then click Add Application.
    image2020-10-13_8-55-17.png

  3. Set the following values:

    Site Alias

    ewa

    Application Pool

    EzeScanWebApps (click Select button)

    Physical Path

    C:\EzeScan.WebApps (click ... to navigate)

    Enable Preload

    Ticked

    image2021-3-11_16-6-25.png

  4. Click OK to finish and confirm your application is shown under Default Web Site.
    image2020-10-13_8-58-41.png

Testing the site

  1. Right click on ewa > Manage Application > Browse.
    image2020-10-13_9-28-35.png

    If page load fails with an error 500. One possible cause could be that in Prerequisites section, you did not check that IIS was installed and enabled before you installed the ASP.NET Core Runtime Hosting Bundle 6.0.x bundle.

    If you had installed and enabled IIS only after you had installed the ASP.NET Core Runtime Hosting Bundle 6.0.x bundle, you will need to go back and reinstall the ASP.NET Core Runtime Hosting Bundle 6.0 again, and choose to 'Repair' it's prior install.

    Once its repaired, stop and start the IIS site and retry step 1 above to retest the site.


    If page load still fails, another possible cause is the slow execution of the EWA initialisation routines after a fresh software install. When the first browse to an EWA web site occurs,, the EWA startup code actually performs the initialisation of the SQLite databases files. 

    As each database file written out,  a virus scanner may cause the creation of each file to pause whilst it is scanned. Only when each of the 8 databases files and the connectors.json file are created will the EWA website respond with the EWA home page.

    Once that has happened. Stop and start the IIS site and retry step 1 above to retest the site.


  2. If the page loads, then installation is complete.
    image2020-10-13_9-28-3.png