Go to documentation repository
Page History
| Section | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Installation
| Note | ||
|---|---|---|
| ||
|
To install the private License Server in server in Windows OS, do the following:
- Create an activation request (see Creating an activation request). Contact an AxxonSoft manager
- Contact AxxonSoft technical support to get the necessary
- License-server_InstallerWix.zip package and the keyfile.zip license key package for the private License Server.
Certificate: ngp.licserver.crt
- Private key: ngp.licserver.key
Server key: server.license.key
Client key: license.key
- .
- Run the License-server.msi file from the received package. The installation is performed in the C:\Program Files\Common Files\VMS\VMS \VMS
- License Server directory.
- Once installed, the following will be
- is added:
- The VMS License Server program
will be - is added
to - to Programs and Features.
- The VMS_License_Service
will be - is added
to - to Services. It
will start - starts immediately after the installation. After restarting the
Server- server, the service
will start - starts automatically. In Task Manager in Processes, the process of the running service is called license_service.exe. After completing the process
is finished- , a new process
will start - starts in one minute.
- Create an activation request. To do this, you must collect the computer's HIDs using the LS_tool utility by running it in the command line:
Code Block Stop the C:\Program Files\Common Files\VMS\VMS License Server>LS_tool.exe --collect-hwinfoNote title Attention! The key binds to the License server, not to Axxon One. When you use the Guardant key, make sure that the USB key is connected to the server where you install the License server.
- Add the LEASE_ACCOUNTER_TLS_AUTH_ENABLED system variable with the true value (see Creating system variable).
- Stop the VMS_License_Service in Services. Add the
- Send a file with collected HIDs of the computer to the AxxonSoft manager and request the keyfile.zip package for the private License server that contains:
Certificate: ngp.licserver.crt.
- Private key: ngp.licserver.key.
Server key: server.license.key.
Client key: license.key.
- Unpack the keyfile.zip archive received from the AxxonSoft manager.
- Add the server.license.key to the C:\Program Files\Common Files\VMS\VMS License Server\keys folder.
- Rename the ngp.licserver.key private key to ls
- private.key and the ngp.licserver.crt certificate to ls
- keyfile.crt and add them to the C:\Program Files\Common Files\VMS\VMS License Server folder. Confirm the file replacement.
Note title Attention! When you use the License server of a version lower than 2.1.1, you must rename the ngp.licserver.key and ngp.licserver.crt files to ls.key and ls.crt,respectively.
- Start the VMS_License_Service.
- Stop the VMS_License_Service.
- In the C:\Program Files\Common Files\VMS\VMS License Server\keys folder, delete the server.license.key. Only the key named as the system ID must remain in the folder.
- Start the VMS_License_Service.
- Activate the Client license.key on all Axxon One Servers in the domain using the activation utility (see Activation by applying license file).
The keyfile.zip key package contains
Installing the private License Server in Windows OS is complete.
Possible errors:
- Axxon One doesn’t see the License Server—try disabling firewall on both computers, also check if 443 port isn’t already in use.
- The following error is in the License Server logs: C:\Program Files\Common Files\VMS\VMS License Server\logs
Installation of the private License server in Windows OS is complete. The License server web interface is available at https://127.0.0.1:444/ (see Logging in to the License server web interface).
Possible issues
Connection error
Axxon One can fail to establish a connection with the License server. This is due to the network-level connection blocking.
In this case, we recommend disabling the firewall on both the Axxon One computer and the License server computer.
Make sure that port 443 isn't occupied by another process.
License server certificate replacement
In some cases, antivirus software can replace the certificate received from the License server (including public certificates), which results in errors in the logs:
| Code Block |
|---|
~[22384]; 2024-05-28; 10:34:59.557; DEBUG; /LicenseService/App/: ngp certificate path: C:/ProgramData\ITV\IntellectX\Tickets\ngp.ca
~[22384]; 2024-05-28; 10:34:59.620; ERROR; /LicenseService/App/: HttpClient: error in performing http request - err:Peer certificate cannot be authenticated with given CA certificates, method:POST, headers: |
In this case, we recommend disabling traffic interception in the antivirus software. As a result, the certificate from the License server is accepted without modifications, allowing the system to function correctly.
License server error: port 8080 is occupied
The following error can appear in the License server logs:
| Code Block |
|---|
{"app":"LicenseServer","err":"listen tcp :8080: bind: An attempt was made to access a socket in a way forbidden by its access permissions.","level":"error","msg":"exited with error","time":"2022-06-09T09:23:59.471","version":{"PlanKey":"ASIP-LSG","BranchName":"develop","BuildNumber":"69","RevisionNumber":"e89e4088018e47ed982d6f74ed9c4abecde94859"}} |
This error indicates that the server cannot use port 8080 due to the operating system-level restrictions.
In this case, we recommend disabling the IIS (Internet Information Services) service. As a result, it frees up port 8080, allowing the License server to function properly try stopping the IIS service.