A ViewX remote client licensed with its own license file needs the “Geo SCADA Expert License Server” service to be running so the license will be recognized and ViewX can connect to the remote Geo SCADA Expert (GSE) server successfully.
It may happen that the “Geo SCADA Expert License Server” service fails to start automatically. A possible cause would be that a corporate group security policy changes some user rights; specifically the "Log on as a service" one.
This can be checked the following way:
In Windows, run the "Local Security Policy" editor and navigate to "Security Settings\Local Policies\User Rights Assignment\Log on as a service". Check that "NT SERVICE\ALL SERVICES" is included. This is required as the license server runs under a Virtual Service Account (VSA).
The GSE installer ensures that this is configured correctly, but, as mentioned above, something (e.g. a corporate group policy) may change this policy after the installer runs, thus causing this problem.
A trick to repair this issue (tested in Windows 10) is to change the service from log on as "NT SERVICE\LICENCESERVER" to "Local System account" and then back again (leaving the password blank).
Released for:Schneider Electric Nigeria
A ViewX remote client licensed with its own license file needs the “Geo SCADA Expert License Server” service to be running so the license will be recognized and ViewX can connect to the remote Geo SCADA Expert (GSE) server successfully.
It may happen that the “Geo SCADA Expert License Server” service fails to start automatically. A possible cause would be that a corporate group security policy changes some user rights; specifically the "Log on as a service" one.
This can be checked the following way:
In Windows, run the "Local Security Policy" editor and navigate to "Security Settings\Local Policies\User Rights Assignment\Log on as a service". Check that "NT SERVICE\ALL SERVICES" is included. This is required as the license server runs under a Virtual Service Account (VSA).
The GSE installer ensures that this is configured correctly, but, as mentioned above, something (e.g. a corporate group policy) may change this policy after the installer runs, thus causing this problem.
A trick to repair this issue (tested in Windows 10) is to change the service from log on as "NT SERVICE\LICENCESERVER" to "Local System account" and then back again (leaving the password blank).