In the case of Solid Edge closing with a 'Termination Log' message pointing to a log file named crashlogf.txt the application creates a set of log files in the %temp% folder as one of the last actions. In such a case it is advisable to reproduce the crash once again using a minimum number of steps in order to get an optimized set of log files.
How to create a set of log files so that it captures the most comprehensive information?
The following steps describe how to create such a set of log files.
- Start Solid Edge.
- Execute the steps which lead into the close. In doing so try to reduce the number of steps to the most necessary ones.
- Answer the question regarding emailing the log file with 'No' if the 'Termination Log' message pops up.
- After the session is closed open a Windows Explorer/File Explorer.
- Enter %temp% into the input field of the 'Locations'.
- Sort the column 'Date modified' descending (newest files at the top).
- Find and select the following files (where xxx is a placeholder indicating the versions like 110, 219, etc.): cmdlog Vxxx.txt, crashlogf.dmp, crashlogf.txt
- Ensure that the date/time of these files is associated to the date/time of the close.
- Copy the selected files to the clipboard (Ctrl + C).
- Create a new folder in e.g. C:\Temp.
- Choose a folder name with the syntax crashlog_yyyymmdd_index (example folder name: crashlog_20190123_a).
- Open this newly created folder in C:\Temp.
- Paste (Ctrl + V) the previously generated and copied log files to this folder.
- Go back to C:\Temp.
- Add the crashlog folder with the containing log files to an archive (e.g. crashlog_20190123_a.7z).
- Share this compressed archive file with GTAC.
Notes and References
- If it is possible, it would be very helpful to document the above steps at the same time in a video.
- If the steps which lead into the crash are not that clear it would be very useful to repeat the above steps several times, to get different sets of log files (e.g. crashlog_20190123_a.7z, crashlog_20190123_b.7z, crashlog_20190123_c.7z, ...) which will hopefully capture the routines causing the close.
OS Version: n/a