Following are ways you can resolve this problem:


Scenario 1: Backup Server is Running

  1. Quit out of the Backup Server and the Primary Server (or Stop the Service).
  2. Pull the following files from the QLA Primary Server folder to the Trash (but do not empty the Trash):

    EKL.log
    HistChkinChkOut.log
    HWMUsage.dat
    LogOptions.properties
    QLA.log
    QLALicense.dat
    QLANotification.properties
    QLAOld.log
    Save.dat
    users.dat
  3. Load the new QLALicense.dat file into the QLA (Primary) Server folder.
  4. Launch the QLA Primary Server.
  5. Pull the log and properties files from the QLA Backup Server folder.
  6. Place the new QLALicesne.dat into the QLA Backup Server folder.
  7. Launch the QLA Backup Server.

Scenario 2: Log or properties files are damaged.

  1. Quit out of QLA Server (or Stop the Service).
  2. Pull the following files from the QLA Server folder to the Trash (but do not empty the Trash):

    EKL.log
    HistChkinChkOut.log
    HWMUsage.dat
    LogOptions.properties
    QLA.log
    QLALicense.dat
    QLANotification.properties
    QLAOld.log
    Save.dat
    users.dat
  3. Load the new QLALicense.dat file into the QLA (Primary) Server folder.
  4. Launch the QLA Server or Start the QLA Service.

Note: Following are the locations of the QLA Server folder for each platform:

  • For Mac: Hard Drive:Applications:Quark:Quark_License_Administrator:Server
  • For Windows: C:\Program Files\Quark\Quark_License_Administrator\Server folder

Background:
There a two reasons that the QLA Server would not show the full number of licenses in the QLA Server window. The first scenario occurs when you you are running with a Backup Server. If you quit out of the QLA Primary Server (or stopped the QLA Primary Service), but have not stopped the Backup Server, the Primary Server will attempt to pull log and properties information from the Backup Server when you launch it after loading the new QLALicense.dat file. If the License information in the Backup Server is different from that of the Primary Server, the old information will display in the Primary Server window.

The second scenario where this can occur is if the one of the QLA Server log and properties files has become damaged. In this case, you will need to replace these fiiles and reinitialize the QLA Server. To ensure that a QLA Backup Server is not contributing to the problem, you will also need to Quit out of the Backup Server so that the Primary Server does not attempt to pull Backup Server information.