How to resolve common issues setting up ASP.NET sample pages
Associated product(s): Product name: Pro Web
Views: 1819 | Created: 4 years ago | Last updated: 3 years ago
This document highlights the configuration steps required in order to resolve common issues running QAS Pro Web 4.5’s ASP.NET sample pages in a Windows environment.
It assumes that Pro Web and the associated country data has been installed correctly. Where possible, this should be tested by running the test harness, WebConsole.exe; ensuring that it returns addresses.
The ASP.NET pages, i.e. the VB.NET and C# examples, after a standard installation will display the following .NET error page:
To overcome the error, the virtual directory needs to be configured to run as an application under IIS.
In the Microsoft Management console (Control Panels > Administrative Tools), drill down to the Web Site directories and then right click on the QAS installation directory (figure 2) and select ‘properties’:
Within the directory tag, click on ‘create’ to create an application:
By default this will be named the same as the directory, ProWebCS as shown in figure 4:
This will ensure that the Pro Web pages run as an application and will overcome the .NET configuration error.
In additional to the steps above, it may be necessary to configure the pages to connect to the QAS Server.
A standard installation configures the QAS server to listen on port 2021. However, if the QAS Server is configured to listen on another port then the pages will need to direct requests to the new port. This is covered extensively in the QAS Pro Web Integration guide, however the table below highlights where these changes are required:
Updated during installation?