Client gets wrong license

Hi Frederic,
When you run Citect as a Windows Service, it runs the client process in a special "headless" mode which effectively frees up one Control Client license. This "free" license is then available for consumption in the Floating License Pool which can be shared with other client nodes, either locally on the same machine or remotely via the floating license mechanism in Citect SCADA. Now the [Client]PointCountRequired parameter is set on the Client side and allows you to control what license point count the client will request, and if available, acquire. It can get a little complicated, since you don't have control over which server the client will collect the license from. It will basically send out a broadcast to all connected servers, and the first one, with the required license type available to respond, will then be the provider. The [Client]ComputerRole and FullLicense parameter also control what type of license the client will try to acquire.
It would help to troubleshoot this issue if you provide a little background about your architecture and what you are trying to achieve. It might also be worth looking at technical note 9043 in the KSC for some further information about licensing.
One final tip, the Kernel > General window for the Client process is an excellent way to see what licenses are available and also what is being used. If you run Citect as a Windows Service, it is not possible to open the kernel, but it is possible to perform a "Dump Kernel" which will give you a snap shot of all the information you require (General window details will be in the log).
Kind regards
Olivier

Hi Frederic,
When you run Citect as a Windows Service, it runs the client process in a special "headless" mode which effectively frees up one Control Client license. This "free" license is then available for consumption in the Floating License Pool which can be shared with other client nodes, either locally on the same machine or remotely via the floating license mechanism in Citect SCADA. Now the [Client]PointCountRequired parameter is set on the Client side and allows you to control what license point count the client will request, and if available, acquire. It can get a little complicated, since you don't have control over which server the client will collect the license from. It will basically send out a broadcast to all connected servers, and the first one, with the required license type available to respond, will then be the provider. The [Client]ComputerRole and FullLicense parameter also control what type of license the client will try to acquire.
It would help to troubleshoot this issue if you provide a little background about your architecture and what you are trying to achieve. It might also be worth looking at technical note 9043 in the KSC for some further information about licensing.
One final tip, the Kernel > General window for the Client process is an excellent way to see what licenses are available and also what is being used. If you run Citect as a Windows Service, it is not possible to open the kernel, but it is possible to perform a "Dump Kernel" which will give you a snap shot of all the information you require (General window details will be in the log).
Kind regards
Olivier