1. Procmon Logs
   • Use Cases
   • When and How To Include
2. Dump Files
3. CET Distributed Render Server Logs
4. Revlink Logs
5. Sketchup
   • Import
   • Export
   • Warehouse

Procmon Logs

Procmon (Process Monitor) is a Microsoft SysInternals utility that can record the system-related actions that are done by a program, i.e. registry access, disk access, network activity. This means it can determine which file that CET is trying to access at a given point in time. You can find it on this Microsoft Documents webpage.

Use Cases

One use case would be let's say CET complains about some DLL file (e.g. smlib.dll) being unloadable, but the DLL file in question indeed exists on the disk and is not corrupted, so what is going on here? Procmon can tell us that smlib.dll depends on vcredist10.dll and CET tries to load vcredist after loading smlib and cannot find vcredist, so it crashes. This allows us to tell the user to install the latest version of Microsoft VC++ Redistributable to resolve their issue.

Another use case would be, CET hangs for a long time when opening the print dialog, by using procmon, we can determine that CET is attempting to reach an unreachable network printer (through its network activity) and is failing.

When and How To Include

When to include: When CET has missing dlls or any files, hanging/slow for unknown reasons that aren't shown in the logs

Procmon logs are very powerful, but at the same time the amount of data is huge as well, so please make sure the filters are set correctly, and the correct observation time is noted down so we can cross-reference easily with the CET log files.

Always include a fresh set of CET log files (log0-4, bgInstall, launchlog, etc) from the same session when obtaining procmon logs, and please note down the computer date/time (down to the seconds) during the issue occurrence. Procmon logs are extremely detailed, hence we need to know the exact time when the issue occurs.

Please make sure the correct Filters are set when capturing procmon logs, e.g. should filter by CETDesigner.exe (Build) / _cm.exe (Develop).

Dump Files

Dump files are basically snapshots of the memory at a point of time created by Windows, and contain any information related to crashes, but can be very hard or technically demanding to read or analyze. They are also often very huge.

When to include: When CET crashes to desktop unexpectedly, when it doesn't even show any error dialogs, or when it crashes by showing the Windows "Program has stopped working" dialog.

How to get: Usually if the process has not died, you can just go to Task Manager > Details > _cm.exe / CETDesigner.exe and right-click > Create Dump File.

However, if the process died, you might have to tweak Windows settings a little to get Windows to automatically create dump files upon crash. Reference: https://docs.acrolinx.com/kb/en/how-do-i-capture-a-process-dump-of-a-crashing-application-for-support-13731081.html Note: The "automatically create full dump files" process documented in the links above should be disabled as soon as we got what we need, as the files are HUGE.

CET Distributed Render Server Logs

For the CET Distributed Render Server, the log files serve the same purpose as the CET Local Rendering logs, except they are located in a different location. You may find the logs by opening the Render Server Controller and look for the Logs link at the bottom right corner of the dialog.

It is located in either of the following directories for different versions:

Revlink Logs

The Revlink Plugin for Revit has its own copy of log files for actions including importing layout or importing family files.

To find the log files, go to Add-Ins > Revlink > Settings > bottom left corner there is a link to "Log Files", which directs you to the %LocalAppData%\RevLink\ directory. There can be up to 10 (0-9) log files in the directory.

When to include? When the user is facing an issue related to Revlink plugin in Revit or a crash/exception has occurred in Revit.

Sketchup

The Sketchup Extension has separate logging as well, one for import/export, and one for the warehouse.

Import

Located in /CET Data/custom/sketchUp/[Model Name_Some Random Number]/. Contains model data and various resources extracted from the sketchup file during the import process. Include when the user is having issues importing specific models.

Export

Located in /CET Data/custom/sketchUp/export/. Also contains temporary files created during the export process, and may be helpful in determining export issues. Include when the user is having trouble exporting sketchup models.

Warehouse

Located in /CET Data/custom/sketchUp/downloads/skpWarehouseLog.log