q&a

IconDangerInjury Caution: When you select this option, the License Server changes to a 10-day interim mode after the selected repair is finished. An activation key must be entered within 10 days!

Connection problems to License Server - FAQ-03116

Question: Why does my License Manager report problems connecting to the License Server when starting, although the License Manager is installed locally?

Answer: In most cases, the name resolution in the DNS/WINS does not work.

Procedure:

1.Check DNS/WINS configuration and correct if necessary.

Alternative:

2.Enter the IP address of the License Server in "Settings > License Server Address" instead of the name in the License Manager.

IconNote Note: This alternative should only be applied in case of need a correct DNS configuration should have priority.

Different number of workstations in the License Manager Overview - FAQ-03114

Question: In the License Manager overview, five licenses, for example, are shown in the "Used" column for floating licenses. If you click one of these licenses, a different number of workstations with assigned licenses is displayed

What is the reason for this discrepancy?

Answer: The License Manager Overview is not updated automatically but by request only. Clicking an option field, however, shows the current licensing state of this option. The selected field is now updated.

Printready dongle for the License Server - FAQ-03110

Question: Can I use my Printready dongle for the License Server?

Answer: No! There is a blue or black-and-blue "Prinect License Server" dongle. None of the purple product dongles (e. g. for Printready) can be used for the License Server.

License Key of a new product is refused by the License Server - FAQ-03112

Question: Why is the license key of a new product rejected by the License Server?

Answer: First of all, the new product must be "registered" at the License Server. This is done during when the product accesses the License Server for the first time.

Procedure:

1.Install the product

2.Start the License Manager on the product workstation

3.Enter the License Key in the License Manager

4.Start the product

Porting a License Server - FAQ-03115

Question: Can I port the License Server from one computer to another?

Answer: Yes!

Procedure:

1.Export the LDS of the existing License Server (see the Export LDS).

2.Shut down the License Server PC and pull out the License Server dongle.

3.Install the Licensing software on the target computer.

4.Shut down the new License Server, plug in the dongle and start the computer.

5.Import the backup LDS file in the License Manager (see the Import LDS).

6.Make the new License Server known to all applications.

LDS backup path cannot be created - FAQ-03113

Question: The License Manager lets you specify a path for the LDS backup on a remote computer. A backup, however, is not executed. But it is possible with the Windows Explorer.

Answer: The same accounts must exist on the local and remote computer. By default, the License Server Service runs under the "System Account". For safety reasons, the "Guest Account" is often disabled, and access to the "System Account" is denied.

Procedure:

Let the License Server Service run under an account available on both computers that has write permissions for the target computer.

Slow computer although the License Server does not run.

Question: My computer's speed slows down after installation of the licensing software. But I don't use the License Server at all.

Answer: During installation of the License Server, a "Heidelberg License Server Windows Service" is automatically set up and started, ensuring the License Server is always active in the background. It keeps testing the presence of the License Server dongle, which may be detrimental to the system performance.

For this reason, you must stop the Windows Service and set the start-up type to "Manual" if you do not wish operate the License Server although it has been installed.

License error "LDS file does not exist" - FAQ-03235

Question: What can cause the "LDS file does not exist" error message?

Answer: In most cases, the reason for the error is: A License Server dongle may create a single LDS folder only once. The LDS folder and the dongle belong together and you cannot use one without the other. To move the dongle to another system, you have to move both: The dongle and the LDS folder.

If the LDS folder is not found, the reason for this can be that only the License Server dongle was plugged from one system to the other or you restored the system (for example, by writing back a Norton Ghost backup) or reinstalled the system without creating a backup of the LDS folder and restoring it to the correct location in the file system (%HD_STD_USERDATA%\Common Services\LDS). Another reason may have been a system disk failure, and there is no valid backup, making a new installation absolutely necessary.

Procedure:

A repair key can be used to create a new LDS. For information on this topic, please refer to "Create new LDS" Option.

Hint:

There is a workaround also for the case that the system disk is down: You can specify a share in the network as the backup path in the "Settings > LDS" tab of the License Manager (see FAQ-03113). An automatically synchronized copy of the LDS will be created. You can use this copy for restoration. In the License Manager, a user name and password must be entered for the share.

License Server host name (correct designation) - SI-03301

An underscore in the server host name results in a failure to connect to the License Server.

Explanation:

"_" (underscores) are illegal in host names.
Permitted characters are: numbers (0-9), letters (A-Z, a-z), dash (-), dot (.)
TCP/IP does not make any difference between lowercase and uppercase letters in the host name.

License Server: Quick questions - quick answers - FAQ-03266

Question: Do I have to click "Save" in the LDS Assistant every time I want to back up the LDS or does it do it by itself automatically once I specify a backup path?

Answer: Automatically!

License Server: Quick questions - quick answers - FAQ-03266

Question: When I need to repair a LDS and have received the "activation key" (AKEY), does the key work for all products or do I need new activation keys for each product?

Answer: One key for all products.

License Server: Quick questions - quick answers - FAQ-03266

Question: If a dongle breaks and I have a spare one that I plug in, clicking "repair LDS" will allow me to work for 10 days. What will happen if I receive the activation key, do I need new licenses for all products because I have a new dongle?

Answer: A broken dongle can be replaced with an activation key. In this case, the new dongle works like the old one: the LSN from the old dongle is applied to the new one. ALL existing license keys stay valid as a result. It is NOT necessary to request new license keys or to specify any.

License Server: Quick questions - quick answers - FAQ-03266

Question: What will happen if the system time on a product workstation (like Prinect Signa Station) shifts by 10 hours compared to the License Server system time; will this disable all the product licenses (Prinect Signa Station)? And how to fix it, is it enough to repair the system time of the product workstation or do I have to generate a request key and enter an activation key?

Answer: There are two different time tampering situations:

aThe product workstation system time is different to the License Server system time:

In this case, NO LDS repair (including request and activation keys) is necessary. Just correct the product workstation system time. If the License Server system time is wrong, see b).

bThe License Server system time was set back:

This is recorded in the License Server dongle and has to be repaired with an LDS repair (difference > 6h = warning, difference > 12h = error).