QESTField Installation Guide
Applies to QESTField
This article details the installation process for the QESTField product. This includes installation, configuration and solutions to common problems.
Contents
Overview
QESTField is an ASP.NET web application which is hosted via Microsoft Internet Information Services (IIS). An instance of QESTNet must already exist as a connection to the QESTNet service is required, through which QESTField will communicate with the QEST Platform database.
Prerequisites
The following must be present in the target environment to support QESTField.
Machine
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 QEST Web API installer if the environment has internet access.
Internet Information Services 7.0 or later with default features plus ASP.NET v4.5.
Services
QESTNet v4.6 with the QESTLab API for QESTNet installed (default), accessible via TCP or HTTP.
Installation Files
The QESTField installer file QESTField v4.5.B.R.exe (where B and R are the build and revision numbers). e.g. QESTField v4.5.1140.35145.exe
A sample configuration file - Web.Config to add to the QestField installation, or inform about what needs to be updated for existing installations.
Installing QESTField
If Microsoft .NET Framework 4.6.2 requires installation, internet access is needed during the QEST Web API installation process.
Run the provided installer.
If required, click on Options to change the installation options listed in the Installation Options section below.
Copy the Web.config file into QESTField (or alternative) folder. The default directory is
[WindowsVolume]inetpub\QEST Platform\QESTField
Installation Options
Setting | Description | Default |
---|---|---|
Install location | Path to which the QESTField files will be installed (under sub-folder |
|
Configure QEST Platform website and QESTField application | If checked, the installer will automatically set up the IIS configuration for the QEST Platform website and QESTField application. Uncheck this option for systems which require manual configuration via the IIS Manager. | Checked |
Force start QEST Platform website | If 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
Open the Web.config file 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 that QESTField will be connecting to. 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>
If any custom workflows will be used ensure that all required additions to the
<qestfield>
section are added. These are all specified in an example configuration file distributed with QESTField.
Verifying Installation
Open Internet Information Services (IIS) Manager through Control Panel -> Administrative Tools -> Internet Information Services (IIS) Manager.
With the QEST Platform site selected click the start button.
Select the QESTField application and click the Browse action and ensure the QESTField login page is displayed in the browser that opens. . Configure network settings to provide the necessary access for this environment. e.g. provide access to this site on the public Internet.
If this installation is for public use, we recommend securing the connection via SSL/HTTPS security.
QESTField is now installed and ready for use.
Troubleshooting guide
Installation
"Could not load file or assembly" error
When attempting to access QESTField, an error message similar to the below appears:
Server Error in '/' Application.
Could not load file or assembly 'Newtonsoft.Json, Version=4.5.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Resolution
Open Internet Information Services (IIS) Manager through Control Panel -> Administrative Tools -> Internet Information Services (IIS) Manager.
Select the QESTField site, then select Basic Settings....
Check that the "Physical Path" of the site exists and contains the QESTField files (including a valid
Web.config
file in the root directory).
Configuration error - Unrecognised attribute 'targetFramework'
When attempting to access QESTField, an error message similar to the below appears:
Server Error in '/' Application.
Configuration Error
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
Open Internet Information Services (IIS) Manager through Control Panel -> Administrative Tools -> Internet Information Services (IIS) Manager.
Select the QESTField site, then Basic Settings.
Check that the "Application Pool" selected uses .NET v4.0 or higher (click 'Select...' to see more details of the selected Application Pool).
"No connection could be made because the target machine actively refused it" error
When attempting to access QESTField, an error message similar to the below appears:
Server Error in '/' Application.
No connection could be made because the target machine actively refused it 127.0.0.1:52525
Resolution
Confirm that the QESTNet service is running.
Open the
Web.config
file in the root QESTField directory and check the client endpoint addresses match the address of the QESTNet server to which QESTField 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 Configuration Guide section system.serviceModel (above).
"The underlying provider failed on Open" error on login
When attempting to login, the error message "The underlying provider failed on Open" appears.
Resolution
Check that the database connection for QESTNet is properly configured in the QESTNet configuration file. Refer to the QESTNet Configuration Guide section connectionStrings (above).
Check that the server running the QESTNet service has sufficient permissions for this database.
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 QESTField will have a "Show Details" link. This will display a lot of extra information that is useful for diagnosing problems. Please paste this information into the bottom of the Support Request Form when sending the form.
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.