mx_err_pid.log for Windows

When the Java Virtual Machine initializes itself, it installs a handler that gains control when segmentation violations and other unexpected signals/events occur.

The hs_err_pid.log file is generated from this handler. On Windows, an MX handler is chained to this process to catch these events, create an 3DSpace-specific error log, and then pass control back to the JVM's handler. Since tracing may not have been enabled, this means that the events don't need to be recreated to begin troubleshooting.

See Also
Additional Live Collaboration Server Configuration Troubleshooting
Checking Disk Space
Checking Memory Usage

When the MX handler is called on Windows, a file named mx_err_pidID#.log (where ID# is the process number of the failing process) is created in the same directory as the hs_err_pid123.log file (that is, the directory in which the server or MQL was started, generally SERVER_INSTALL\intel_a\code\bin\).

The mx_err_pid.log file includes the same information as monitor server output, as well as a hex dump at the end of the file. Administrators can use this file for the monitor server output. The rest of the file is meant for diagnosis by ENOVIA and should be included with the details of the problem sent to ENOVIA Customer Support.