VIC Aia test fails on the server and produces the error code - HTTP Error 400.605
RecTrac 3.1.10.30.01
Table of Contents
Problem
During the final stages of a Rectrac Server Migration, it has been found that the VIC EXE program will not connect to RecTrac on any front-end workstation and produces the following error message.
Error Message
HTTP Error 400.605
Solution
You will need to visit IIS in the Rectrac Database server and remove and then re-add the Tomcat Server Farm entry. For new Tomcat Server Farm entries, some Proxy changes are necessary. Additionally, the Tomcat server also requires the VIC Aia routing rule to be in place.
Steps For Solution
To remove the Tomcat Server Farm:
- On the Rectrac database server, open IIS (Internet Information Services).
- Open the folder labeled Server Farms.
- Remove the Tomcat server farm entry.
To create a new Tomcat Server Farm:
- Click Create Server Farm.
- Enter Tomcat as the Server farm name.
- Disable Online toggle.
- Click Next.
- Enter localhost as the Server address.
- Click Show Advanced settings.
- Expand applicationRequestRouting.
- Locate and change httpPort to 8085.
- Change httpsPort to 8443.
- Click Finish.
- Click No.
To make Proxy changes:
- Click Tomcat.
- Click Proxy.
- Toggle off Include TCP port from client IP.
- Change the Response buffer threshold (KB) to 0.
- Click Apply.
To check your Routing Rules:
- Click Tomcat.
- Click Routing Rules.
- Click URL Rewrite on the righthand side.
- Verify that the VSI AIA TRAFFIC routing rule is present. If not:
- Click Add Rule(s)….
- Click Blank rule.
- Set Name to VSI AIA TRAFFIC.
- Set Using to Wildcards.
- Set Pattern to *aia/Aia* and note that this is case-sensitive.
- Toggle off Ignore case.
- Change Action Type to Route to Server Farm.
- Toggle on Stop processing of subsequent rules.
- Click Apply.
- Click Tomcat.
- Click Bring Server Farm Online on the righthand side.
To restart your RecTrac site from IIS:
- Expand Sites on the left.
- Highlight VSI3_CLIENT.
- Click Restart under
- Restart the RecTrac site in IIS.
Verify the fix by performing a new VIC Aia connection test on the server.