Tracking Server Logs

You can consult license server logs using the Server Logs tab. A maximum of 1GB of logs is transferred from the license server to the license admin tool: above truncated.

  1. Select the Server Logs tab.

    The tab looks like this:

    Ctrl-F allows searching in the log.

    Clicking at the top of the column headers allows you to sort the lines by timestamp, severity, type or message.

  2. Specify the dates from when and until when you want to view log information, and select the server:



    The exact moment corresponding to the From : date is at 00H01 local time (time zone) of the computer on which the License Administration Tool is running.

    The exact moment corresponding to the To : date is at 23H59 local time (time zone) of the computer on which the License Administration Tool is running.

    However, time values displayed are formatted according to the local time (time zone) of the computer on which the license server is running.

    The From : date value (respectively To :) is automatically set to the To : date value (respectively From :) if the To : date value (respectively From :) is manually set to a value lower (respectively higher) than the current From : (To :) date value.

    Every event is time-stamped.

    The log contains:

    • information (identified by the letter I) about license server events such as starting and stopping the server, enrolling licenses, etc.
    • warning messages (identified by the letter W) displayed in blue
    • error messages (identified by the letter E) displayed in red

    organized into categories, each describing a specific area being monitored. For a full list of categories, see Error, Information and Warning Messages

    In the case of a failover cluster, each member has its own log files.

    If you activated the License usage tracing... option in the Server Configuration dialog box, detailed traces of license request and detach operations and timeouts will be logged.

    Detailed monitoring of license usage is available with the USGTRACING category. The messages comprise 13 fields separated by the character "!":

    • Field 1: Action; The possible values are:
      • Grant: the license server has received a license request from a client, and the license server has granted a license
      • Detachment: the license server has received an end-of-use event from a client, and the license server has then detached the license.
      • TimeOut: the license server has not received a still-alive (heartbeat) event during the expected period, and the license server has then detached the license.
        Note: Detaching of licenses granted to the 3DSpace server is not traced by default. Instead, timeouts appear for these licenses unless you set the following variable:
        MX_NUL_FULL_USAGE_REPORT=true

        in the enovia.ini file (Windows) or mxEnv.sh (Linux). For more information about this variable, see the 3DSpace server documentation.

      • Extraction: the license server has received a license offline extraction request from a client, and the license server has granted an offline license
      • Return: the client has returned an offline license
      • Recovery: the offline extraction duration has ended.
    • Field 2: Offline extraction duration (in days), or empty if field 1 is different from Extraction
    • Field 3: Feature.
    • Field 4: ID.

      Every time a session is opened by a client, the license server allocates it an ID. Several different licenses granted to a given session share the same ID (but not the same feature). Several different sessions do not share the same ID, even if run by the same user on the same client computer.

      For example, if a user launches simultaneously two V5 sessions requesting an HD2 license, only one HD2 license is granted, but two grants are logged with two different IDs. This allows very precise matching between grants and detachments, for example.

      The format of this ID is slightly different between offline licenses and non-offline licenses.

    • Field 5: Editor Name
    • Field 6: Model: refers to the type of license (such as named user or concurrent user)
    • Field 7: Quantity: 1, or N in the case of tokens or credits
    • Field 8: Commercial Type
    • Field 9: Client Hostname.

      FQDN appears if the following environment variable is set on the Windows client process environment and if the Windows client process takes it into account:

      DSY_SendFQDNtoDSLS=TRUE

      In addition to the hostname, this field contains in parenthesis the ComputerID, the IP address in hexadecimal notation and the Windows session number or Linux display number.

    • Field 10: Client IPv4/IPv6 address
    • Field 11: Client Username
    • Field 12: Client InternalID
    • Field 13: Client exe name for non-offline licenses, or Client ComputerID for offline licenses.

      Examples: 3DEXPERIENCE.exe, CATAsyncProcess.exe, CATBatchStarter.exe, CATUTIL.exe.

    • Field 14: Client process level. The value begins with "5" for V5 licensing client processes, and with "6" for V6 and 3DEXPERIENCE licensing client processes.
    • Field 15: Pricing structure value.

    If the Managed Licensing Service is used, an additional field containing the CustomerID is inserted between fields 3 and 4.

    The following example illustrates log information for offline extraction of an MDG V6 license:

    Extraction!20!MDG!2DA0Q-ZO8S2-YC5ST-874ZO-JJVXI!
Dassault Systemes!NamedUser!1!STD!COMPUTER2 (426814856456C759-0a32103f.1)
!10.50.16.63!V6USER!V6USER!CSR-426814856456C759!3DExperience!

    In the case of an offline extension, two lines are logged:

    • the first one is a Return, with the same ID as the one tagged in the previous matching Extraction
    • The second one is an Extraction, with a new different ID.

    When the license server is stopped, it cannot receive end-of-use and still-alive (heartbeat) events from clients. When the server is restarted, if the expected period has passed, a TimeOut is logged.