/
QESTField Scheduler Installation Guide

QESTField Scheduler Installation Guide

QEST Platform 4.92 and 4.93
Applies to QESTField Scheduler


This article details the installation process for the QESTField Scheduler product. This includes installation, configuration and solutions to common problems.

Contents

Overview

QESTField Scheduler is a React.js front-end + ASP.NET back-end web application, which is hosted via Internet Information Services (IIS). A connection to an instance of the QESTNet service is required, through which it can operate on the QEST Platform database.

Prerequisites

The following must be present in the target environment to support QESTField Scheduler.

Machine

  • Google Chrome (or other Webkit-based web browser)
  • Windows Server 2008 R2, Windows 7 or later (64-bit).
  • Microsoft .NET Framework 4.6.2 or later. If required, this will be installed via the QESTNet installer if the environment has internet access.
  • Internet Information Services 7.0 or later with default features plus ASP.NET v4.5.
  • QESTField v4.6.

Services

  • QESTNet v4.6 with the QESTLab API for QESTNet installed (default), accessible via TCP or HTTP.

Installation Files

  • Installer QESTFieldScheduler.Installer.Ma.Mi.B.R.exe where Ma, Mi, B and R are the major version, minor version, build and revision numbers. E.g. QESTFieldScheduler.Installer.4.6.2895.26827.exe

Installing QESTField Scheduler

  1. Run the provided installer.

  2. If required, click on Options to change the installation options listed in the section below.

  3. Agree to the terms and conditions and click Install. The installer will install and turn on any required Windows features before installing QESTField Scheduler.

Installation Options

SettingDescriptionDefault
Install locationPath to which the QESTField Scheduler files will be installed (under sub-folder QESTField Scheduler). If an existing installation of the QEST Platform website exists, this should match the path of that website.[WindowsVolume]inetpub\QEST Platform
Configure QEST Platform website and QESTField Scheduler applicationIf checked, the installer will automatically set up the IIS configuration for the QEST Platform website and QESTField Scheduler application. Uncheck this option for systems which require manual configuration via the IIS Manager.Checked
Force start QEST Platform websiteIf checked, the installer will attempt to stop all websites running on the default port (80) so that the QEST Platform site can be started.Unchecked

Configuring QESTField Scheduler

  1. If required, open the Web.config file which was installed into the QESTField Scheduler folder with a text editor. At the bottom of the file change all client endpoint address host names from localhost to the name or IP of the QESTNet server to which QESTField Scheduler will be connecting. Close and save the file. If any other configuration changes were made to the QESTNet such as port or protocol then the same changes must be made here.

      <system.serviceModel>
        <bindings>
          ...
        </bindings>
        <client>
          <endpoint address="net.tcp://localhost:52525/Lab" binding="netTcpBinding" bindingConfiguration="Lab_Session" contract="Spectra.QESTNET.Contracts.ISessionService" name="Lab_Session" />
          <endpoint address="net.tcp://localhost:52525/Lab/query" binding="netTcpBinding" bindingConfiguration="Lab_Query" contract="Spectra.QESTLab.Contracts.ILabQueryService" name="Lab_Query" />
          <endpoint address="net.tcp://localhost:52525/Lab/file" binding="netTcpBinding" bindingConfiguration="Lab_File" contract="Spectra.QESTLab.Contracts.ILabFileService" name="Lab_File" />
        </client>
      </system.serviceModel>
  2. Depending on the installation options used, the QEST Platform website and QESTField Scheduler application may need to be manually configured and/or started via the IIS Manager. Note if you are manually configuring the QESTField Scheduler application, it must be configured with alias "Scheduler".

QESTField Scheduler is now installed and ready for use. If you navigate to the URL where QESTField Scheduler is hosted, you should see the login screen.

Troubleshooting guide

Installation

Unspecified Error

If you get the following installation error ‘0x80072ee7 – Unspecified Error’, this is most likely due to the installer being unable to download and install .NET Framework 4.6.2.

You can confirm that this is the issue by viewing the log file and looking for the following: Failed attempt to download URL: 'http://go.microsoft.com/fwlink/?LinkId=671728' to: 'C:\Windows\Temp{B321459C-617D-4C9F-8C70-15AEEE5945CF}\NetFx462Web'

Fix: To install QESTField Scheduler you will need to download .NET Framework 4.6.2 and install it prior to installing QESTField Scheduler. The .NET Framework 4.6.2 Installer can be found here: https://www.microsoft.com/en-au/download/details.aspx?id=53344

HTTP Error 500.19 - Internal Server Error

An error page with the following message appears when attempting to access the QESTField Scheduler:

HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.

Resolution

  1. Open Internet Information Services (IIS) Manager through Control Panel -> Administrative Tools -> Internet Information Services (IIS) Manager.
  2. Select the QESTField site, then the action View Applications.
  3. Check that the "Physical Path" of the application exists and contains the QESTField Scheduler files (including the file Web.config in the root directory).

To change the path of the application, select Edit Application -> Basic Settings... in the IIS Manager.

Configuration error - Unrecognised attribute 'targetFramework'

An error page with the following message appears when attempting to access the QESTField Scheduler:

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Unrecognized attribute 'targetFramework'. Note that attribute names are case-sensitive.

Resolution

  1. Open Internet Information Services (IIS) Manager through Control Panel -> Administrative Tools -> Internet Information Services (IIS) Manager.
  2. Select the QESTField site, then the action View Applications.
  3. Check that the "Application Pool" of the QESTField Scheduler application uses .NET v4.0 or highter.

Images fail to load

Image files (such as the QESTField logo on the login page) do not load.

Resolution

  1. Open Internet Information Services (IIS) Manager through Control Panel -> Administrative Tools -> Internet Information Services (IIS) Manager.

  2. Select the QESTField site, then the action View Applications.

  3. Check that QESTField Scheduler is installed as an application under the QESTField site with virtual path "/Scheduler". 

  4. If QESTField Scheduler is not installed as in Step 3, follow the steps provided in the 1023836215 to install it correctly.

    If QESTField Scheduler is already installed as in Step 3, there may be an issue with the configuration of the QESTField Scheduler build that was supplied. Please contact Spectra QEST for further information (see below).

"The underlying provider failed on Open" error on login

When attempting to login, the error message "The underlying provider failed on Open" appears.

Resolution

  1. Check that the database connection for QESTNet is properly configured in the QESTNet configuration file (refer to the QESTNet Configuration Guide section "connectionStrings").
  2. Check that the server running the QESTNet service has sufficient permissions for this database.

"Could not Connect" error on login

When attempting to login, an error message similar to the below appears:

Could not connect to net.tcp://localhost:52525/Lab.
The connection attempt lasted for a time span of 00:00:02.0026098.
TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:52525.

Resolution

  1. Confirm that the QESTNet service is running.
  2. Open the Web.config file in the root QESTField Scheduler directory and check the client endpoint addresses match the address of the QESTNet server to which the QESTField Scheduler is connecting. These addresses are specified in a section similar to the one below:
      <system.serviceModel>
        <bindings>
          ...
        </bindings>
        <client>
          <endpoint address="net.tcp://localhost:52525/Lab" binding="netTcpBinding" bindingConfiguration="Lab_Session" contract="Spectra.QESTNET.Contracts.ISessionService" name="Lab_Session" />
          <endpoint address="net.tcp://localhost:52525/Lab/query" binding="netTcpBinding" bindingConfiguration="Lab_Query" contract="Spectra.QESTLab.Contracts.ILabQueryService" name="Lab_Query" />
          <endpoint address="net.tcp://localhost:52525/Lab/file" binding="netTcpBinding" bindingConfiguration="Lab_File" contract="Spectra.QESTLab.Contracts.ILabFileService" name="Lab_File" />
        </client>
      </system.serviceModel>
    For more information, refer to the QESTField Scheduler Configuration Guide section "system.serviceModel".

General Usage

"Gateway Timeout" error

After performing an action in QESTField Scheduler, a "Gateway Timeout" error message appears. Multiple instances of this error may occur at once. This error occurs when the QESTField Scheduler's web server becomes inaccessible.

Resolution

Check that the web server hosting the QESTField Scheduler application is running normally.

Redirected to Login page unexpectedly

When performing an action in QESTField Scheduler, the page redirects to the Login page unexpectedly. This occurs when the QESTNET service is no longer available, or the current user's session has expired from inactivity.

Resolution

  1. Check that the QESTNet service is running normally.
  2. If user sessions are being invalidated too quickly, the session lifetime specified in the QESTNet configuration file can be changed (refer to the QESTNet Configuration Guide section "engine sessions").

Spinner loops constantly, page never loads

When accessing the QESTField Scheduler site, a red spinner loops constantly but the page never loads.

Resolution

Check that the site is being accessed via a recent version of a supported browser:

  • Google Chrome
  • Mozilla Firefox

"Could not find work order" error

After performing an action on a work order, an error message similar to "Could not find work order with QestUUID <uuid>" appears. This error occurs when the work order has been deleted by another user since it was loaded into the QESTField Scheduler.

Resolution

Click the "refresh work orders" button at the top of the scheduler page to remove deleted work orders from the QESTField Scheduler.

Reporting Errors

If the information above has not resolved your issue, the Spectra QEST Service Desk procedure (Product Support Procedure Overview) should be followed to report the problem.

Specific errors that occur in the QESTField Scheduler have a "Copy details to clipboard" link. This will include a lot of extra information that is useful for diagnosing problems. Please paste these into tickets raised in Spectra QEST's service desk.


Products described on these pages, including but not limited to QESTLab®, QESTNet, QESTField, Construction Hive, and associated products are Trademarks () of Spectra QEST Australia Pty Ltd and/or related companies.

The content of this page is confidential. Do not share, duplicate or distribute without permission.

© 2020 Spectra QEST® Australia Pty Ltd and/or related companies.  Terms of Use and Privacy Statement


Integrity | Curiosity | Empathy | Unity

The content of this page is confidential and for internal Spectra QEST use only. Do not share, duplicate or distribute without permission.