Location:  United Kingdom  (clear)

How to resolve the 'Licence Not Found' warning message

Document type: Tech doc  
Associated product(s): Product name: Pro Version: 4.0 + OS: Windows (more products)
Product name: Batch Version: 4.0 + OS: Windows
Product name: Pro Web Version: 4.0 + Implementation: Web APIOS: Windows

Views: 1182  |  Created: Last yearLast updated: Last year

Summary

This document illustrates how to resolve the ‘Licence Not Found’ warning message received during use of QAS products.

This warning message can be presented in one of two ways:

  • Data Warning Dialog (shown below)
  • Within an Administrator Notification Email (configured on the QAS Server)

The error message indicates that one or more of your installed QAS data sets cannot be used as they do not have a valid licence key. All QAS data sets across all platforms require a valid licence key in order to function.

The dialog box/Administrator Notification email lists the data sets that do not have a licence key.

Licence Not Found Warning Dialog

In the example shown above two Australian (AUS) QAS data sets require a valid licence key in order for them to function.

All QAS data sets that are installed using the Windows QAS Data Installer (present on every QAS data CD/DVD) prompt for a licence key to be entered during installation.

If, however, your QAS data files were installed via another method, such as the manual copying of data files from the QAS Data CDROM, a licence key may not have been entered, and an error as shown above would occur.

Solution

Windows

1. Note down all QAS data set(s) that are without a licence key.

2. Locate your QAS Licence Key Information

Licence keys for all purchased QAS data sets can be found in an email sent to the nominated contact at the time of purchase.

3. Start up the QAS Product Licence Manager

This will differ depending on your product, QAS Pro/Pro Web or Batch.

Pro/Pro Web

Start up the Configuration Editor which is located in the same Windows Program Group as QAS Pro.

To start the Configuration Editor:

  • Click on Windows Start menu and select Programs.
  • Select the QAS Pro/Pro Web folder and then click on Configuration Editor

Cancel any licensing error dialog boxes that appear by pressing the Cancel button.

  • Click on the Database Manager option in the left hand pane of the Configuration Editor.

You will see a window similar to the one below.

Batch

Startup QAS Batch.

To start Batch:

  • Click on the Windows Start menu and select the Programs menu.
  • Select the QAS Batch Program Menu and select QAS Batch

Cancel any licensing error dialog boxes that appear and close down any Open Sessions by pressing the Cancel button.

Select the Tools menu and open the Country Manager... and you will be presented with a screen as shown below.

4. Add Licence Keys

Click on the Licences... button (shown in respective product screenshots) to activate the Licence Manager dialog box. You will be presented with a dialog box shown below.

For all the QAS data sets that reported they were unlicensed, input appropriate licence keys. Your licence keys will be listed on the email you located earlier. After each licence key is entered click on the Add... button and repeat this process until all your unlicensed data sets have been registered. Once all licence keys have been entered click the OK button on the dialog box.

(Please note licence keys are case insensitive)

5. Restart your QAS product

Close down your QAS dialog boxes and restart your QAS application. It will start up without any licensing errors.

UNIX

1. Note down all QAS data set(s) that are without a licence key.

2. Locate your QAS Licence Key Information

Licence keys for all purchased QAS data sets can be found in an email sent to the nominated contact at the time of purchase.

3. Locate the qalicn.ini file for the product(s) reporting licensing errors

Open this file in a text editor and add the missing licence keys to the end of the file. Save and close the file.

4. Restart your QAS processes

Programs will need to be restarted for the changes to take effect.

Was this document helpful?

What can we do to improve this information?