License reservations issues and solutions
- Last UpdatedApr 16, 2024
- 1 minute read
The following table provides common issues and solutions related to reserving licenses.
|
Operation |
Problem Description |
Solutions |
|---|---|---|
|
Reservations |
When should I use Reservations? |
We recommend license reservation when there are different licenses for a single product. Example - reservations unnecessary: On a license server with one Historian license (or sub license) and one InTouch license, there is no need to reserve because only Historian can use the Historian license and only InTouch can use the InTouch license. Example - reservations recommended: if you have an InTouch read only, InTouch read/write and InTouch runtime on the same server, then you need to reserve each to the node that should use them. |
|
Reservations |
How do I make sure that an Application Server run-time license is taken by a device instead of the DEV license? |
Reserve the run-time license to the Application Server run-time node. If this does not resolve the issue, deactivate the DEV license when not in use. This will force the run-time node to acquire the run-time license or reserve the dev license to a non existent node so that it cannot be acquired. |