Creating CmDust & CmAct Logs for CodeMeter Diagnostics

In rare troubleshooting scenarios, standard logging may not provide sufficient details. In such cases, CodeMeter’s CmDust and CmAct logs can help gather advanced diagnostic information to analyze licensing issues, identify configuration problems, and troubleshoot CodeMeter errors.

The following instructions are required only if the support team asks you to provide the requested diagnostic files.

Instructions

Creating a CmDust.log file

1. (if you are using a CmDongle, connect your CmDongle).

2. Search for and start the CmDust application in the Windows start menu: Start -> All Programs -> CodeMeter -> Tools -> CmDust or simply type “CmDust”.

3. A command line window opens automatically and closes again after a few seconds.

4. Shortly after it, a new explorer window will open and point you to the newly created file "CmDust-Result.log" in your user directory.

5. Then send the CmDust-Result.log file to Support and Services.

Finding the CmAct files

These files are located in the following directories, depending on the operating system used
Windows: Windows: C:\ProgramData\CodeMeter\CmAct
Linux: /var/lib/CodeMeter/CmAct
MacOs: /Library/Application Support/CodeMeter/CmAct

It is best to zip the contents of the entire directory and send it to Support and Services.