...
Expand | ||
---|---|---|
| ||
1. Enable detailed logand then restart the program.Settings-Other-Detailed log (Debug information for developers) 2. Restart the program3. Execute the actions that led to the error.34. Run Diagnostics.If possible, do this right during the manifestation of the problem. You can start it in several ways:
5.TransferSend the resulting file report.zip to usAfter the completion of the Diagnostics, the report.zip file will be generated, the file will be located in the directory where the program is installed (it will open automatically after the completion of the Diagnostics). The resulting file needs to be sent to support. |
...
Expand | ||
---|---|---|
| ||
1. Enable detailed logand then restart the program.Settings-Other-Detailed log (Debug information for developers) 2. Restart the program3. Execute the actions that led to the error.34. Run Diagnostics.If possible, do this right during the manifestation of the problem. You can start it in several ways:
5.TransferSend the resulting file report.zip to usAfter the completion of the Diagnostics, the report.zip file will be generated, the file will be located in the directory where the program is installed (it will open automatically after the completion of the Diagnostics). The resulting file must be sent to support. |
...
Expand | ||
---|---|---|
| ||
1. Enable detailed logand then restart the program.Settings => Program => Detailed log (debug information for developers) (above the Diagnostics button) 2. Restart the program3. Execute the actions that led to the error.34. Run Diagnostics.If possible, do this right during the manifestation of the problem. You can start it in several ways:
5.TransferSend the resulting file report.zip to usAfter the completion of the Diagnostics, the report.zip file will be generated, the file will be located in the directory where the program is installed (it will open automatically after the completion of the Diagnostics). The resulting file must be sent to support. |
...