How Do I Overcome Error -1053 - Dongle not Configured?

Summary

Nearest for the Web and Pro for the Web are available in two different licensing structures. These are an annual license, and a per-click based license.

When attempting to use the asp sample pages provided with Nearest Web or Pro Web, customers using a per-click license may encounter error -1053 Dongle not Configured when attempting to carry out a lookup.

Symptoms:

After installing Nearest for the Web or Pro for the Web Versions 3.x with a per-click license, and attempting to access the ASP sample pages that are provided with Nearest for the Web, and carrying out an address lookup with these, you may be confronted with the error -1053: Dongle not configured (see screenshot below):

Solution

1. Locate the Folder where you have Installed Nearest for the Web

This error is generated by a permissions issue on the click counter, which means that IIS can not access and amend information to the click counter. In order to correct this, the appropriate permissions will need to be set on the folder containing the click counter. This folder is located within the program installation folder for Nearest for the Web or Pro for the Web. By default, this will be in c:\program files\qas\

Locate the Folder that Contains the Click Counter

Once you have located the installation folder, you should see a folder within this called QANWBEA.reg which contains the click counter.

2. Adjust the Permission on the QANWBEA.reg Folder

Right-click this folder, and select properties. From the properties box, click on the security tab, where you should see the user permissions set for the folder. You will need to add the Internet Guest Account (i.e. IUSR_TSXPTEST), and the Launch IIS Process Account (i.e. IWAM_TSXPTEST (See the screenshot below)):

NB: This solution is aimed at users using the asp sample pages on IIS. Users using asp.NET pages may also need to add the aspnet user with full permissions. Users using a web server other than IIS should add the relevant internet guest account to the folder permissions.

Should you still encounter problems after this, please contact support using the link below.