Problem
When setting up the connection between the DS License Server and Client machines running CATIA, users may encounter communication issues between the two machines with no obvious source of error. Some common issues are that the client machine cannot communicate with the DS License Server, or the DS License Server may not be available. The DSCheckLS Tool is a command-line tool that runs from a Client computer to confirm that the Dassault Systèmes License Server (DSLS) has been set up properly.
This article explains how to use the DSCheckLS Tool and what information to expect.
Solution 1: Basic DSCheckLS Tool Usage
-
On the Client Machine, search for Command Prompt and run the program as Administrator from the Windows Start Menu
-
Open Windows File Explorer and navigate to the directory:
<LicensingClientInstallPath>\OS\code\bin
This location varies depending on the installation path. For example:
C:\Program Files\Dassault Systemes\B34\win_b64\code\bin -
Drag the DSCheckLS.exe file into the Command Prompt window, or right-click the Tool and select "Copy as path", and paste the file location into the Command Prompt window using CTRL + V on the keyboard
- Type -h at the end of the command line so the full command is:
"C:\Program Files\Dassault Systemes\B34\win_b64\code\bin\DSCheckLS.exe" -h - Hitting Enter in the Command Prompt will display the status of the license server.
-
Here are some other commands that can be run using a different syntax instead of -h:
-l: displays the status of the license servers
-r lic: requests license "lic" enrolled on the license server.
-t lic: requests Token licenses enrolled on the license server.
The "-r lic" option requests Named User and Concurrent User type licenses, and the "-t lic" option requests Token type licenses.
Note: There is no option available to request Credit type licenses.
Solution 2: Running the -l Command
This is what tends to be run first and is run by default when running the DSCheckLS Tool without additional switches. The DSCheckLS connects with the list of declared license servers in the DSLicSrv.txt file (located in C:\ProgramData\DassaultSystemes\Licenses folder) and rapidly requests and releases a license to check that license servers are operating correctly, without having to run processes such as CATIA or DSLicMgt.
It will display a status along with information about each contacted license server:
- The pathname and contents of the DSLicSrv.txt file
- *Server status
- configuration type: STANDALONE or FAILOVER or MANAGED
- version number
- build date
- if offline extraction is Enabled or Disabled
- IP address
- licensing port number
- exchange message duration with server (ms)
- OS name
- OS version
- OS architecture
- computer id
*Each status is described in the following table:
| Status | Description |
| RUNNING | License server is up and running |
| NOT_SYNCHRONIZED | License server and license client are not time-synchronized |
| HOST_UNREACHEABLE | Host did not reply (for example, the host has been shut down) |
| NOT_RUNNING | Host is up, but the license server process is not available or down |
| CANNOT_CONNECT | |
| INVALID_SERVER_RESPONSE | |
| NO_IP_ADDRESS | Unable to get license server IP address |
| INVALID_SERVER_VERSION | License server too old; the minimum license server level required is not present |
| ALREADY_DECLARED | Ignored: server is declared more than once in the DSLicSrv.txt file |
| INVALID_SERVER_DECLARATION | Incorrect license server declaration: incorrect format or invalid characters |
| INVALID AUTHENTICATION DATA | Missing or invalid authentication file (Managed Licensing Service only) |
Depending on the status displayed after having run the command, you may be able to diagnose the issue.
Solution 3: Running the -r lic Command
This grants and then releases the license of interest. You will need to spell out the entire license key feature as shown on the DSLS.
If the request succeeds, the following information related to the granted license is displayed, for example:
Information Displayed:
- feature
- internal_id
- status
- com_type
- model
- exp_date
- nb_token
- customer site
- customer country
- customer id
- server
- nb additional infos (if available)
- position in queue (if available)
If the request fails, the reason is provided.
Data such as authorization rules and MaxReleaseNumber are taken into account
For additional support, existing customers can submit a ticket or new customers can contact Hawk Ridge Systems.
Comments
Article is closed for comments.