QA00000306930_Reporting a problem with the CST Studio Suite when using it with DSLS

QA00000306930_Reporting a problem with the CST Studio Suite when using it with DSLS

Question:
How to report a problem with the CST Studio Suite when using it with DSLS?

Answer:
When reporting a problem with the CST used with DSLS, please provide the CST technical support team with a following information:
 
1. A step-by-step description of the circumstances under which the problem occurs, which should include
      - Steps to reproduce the issue (with screenshots and/or a small video)
      -  Screenshots of the error message(s)    
      - Mention the version of CST used 
 
2. Provide following details from the DSLS admin tool (please include screenshots) :

      a. Version of DSLS tool:  In the Server Definitions tab of the DSLS admin tool one can find this
      b. Details such as feature, Max Release Date, End date, Additional Info etc. from the Administration tab. Please note that a few columns are not       selected by default so select those from the select columns field. Refer the screenshot below (screenshot is available as an attachment as well in       the QA). (To get these details, one should first connect to the license server from the Server Definitions tab)


      c. Screenshot of the Authorization tab
      d. If the issue is with license check-out/check-in or with the usage of the license, then include the screenshot of Usage Per Feature and Usage Per       User (capture these screenshots when the issue is reproduced. These are real time data based on the actual check-in and check-out)  
 
3. Provide CST log and DSLS log files:
      - Model.log file from the CST project
      - DS license server log files and server statistics files (if enabled) are stored by default at:

Windows: C:\ProgramData\DassaultSystemes\LicenseServer\LogFiles
Linux: /var/DassaultSystemes/LicenseServer/LogFiles

You may find many files here, either provide the relevant file\s based on when the issue was reproduced or zip the folder and provide the same.

To get more detailed DSLS logs, make sure to enable license usage tracing from DSLS admin tool. 

Right Click on the connected server > Display Properties > Licensing Usage Tracing > Select necessary feature or all features. Refer Screenshot below.


 
4. Capture the extensive logs:

Please note that this should be done only if DS support team asks for it.

To capture the extensive logs user should follow the steps mentioned below and then reproduce the issue.

a. DSLS traces:
Enable DSLS traces by setting the following environment variables in the CST frontend (client). If you are using CST DC and facing the issues with CST DC + DSLS then, set these variables in both CST frontend and DC main controller machines  (please make sure to restart the DC main controller service after setting the variables in Main Controller machine)

On CST frontend (client) : 
DSLCC_VERBOSE=TRUE
DSLCC_TRACE_PATH=C:\temp\client_dsls_debug.txt

Repeat same steps on DC Main controller (if DC is used) :

DSLCC_VERBOSE=TRUE
DSLCC_TRACE_PATH=C:\temp\MC_dsls_debug.txt

Note: Change the paths accordingly if client and main controller are running on Linux. Contact your Linux administrator for more help.

b. Enable CST registry debug flags:

To enable CST registry debug flags: Open CST GUI > Open any project > Macros > File > Registry Debug flags > Activate the flags. After activating this setting make sure to Close and reopen CST GUI.

Once you set 5.a & 5.b, then reproduce the issue and provide the following logs:
      - All the *.log files created inside CST installation folder.
      - MC_dsls_debug.txt & client_dsls_debug.txt files
      - All *.mdg files created inside CST_project_folder\Temp dir
 
If you are using CST with Managed DSLS then along with the details mentioned above, also please check and provide details as mentioned in  QA00000306958_Reporting a problem with the CST Studio Suite when using it with Managed DSLS (M-DSLS)