If your WebSphere MQ Automation Classes for ActiveX script fails, there are a number of sources of information.
Independently of the trace facility, for unexpected and internal errors, a First failure symptom report may be produced.
This report is found in a file named OMQnnnnn.fdc, where nnnnn is the number of the ActiveX process that is running at the time. You find this file in the working directory from which you started ActiveX or in the path specified in the OMQ_PATH environment variable.
WebSphere MQ provides various error logs and trace information, depending on the platform involved. See your Winodws NT application event log.