Transactional IBM MQ 9.0.0.3 .NET监控示例运行崩溃报AMQ8377错误

Let's break down how to fix the AMQ8377 error you're hitting when running your transactional .NET monitor with runmqdnm—this error typically means the tool can't load or initialize your monitor assembly/class correctly. Here are the key steps to diagnose and resolve it:

• Verify assembly path and class name accuracy
  Double-check that:

  • Your TransactionalMonitor.dll is in the current working directory where you're running runmqdnm, or specify the full path to the assembly in the -a parameter (e.g., -a C:\mq-monitors\TransactionalMonitor.dll).
  • The class name TransactionalMonitor.Monitor is 100% correct: it must match the full namespace + public class name, and the class must properly implement the IMQTransactionalMonitor interface as specified in the IBM MQ 9.0 docs (including all required methods like OnStart, OnCommit, etc.).

• Ensure .NET Framework version compatibility
  You compiled targeting .NET 2.0, so confirm:

  • The machine running runmqdnm has .NET Framework 2.0 (or a compatible higher version) installed.
  • If there's a conflict with newer .NET versions on the system, create a runmqdnm.exe.config file in the same directory as runmqdnm.exe to force it to use the .NET 2.0 runtime:

    <configuration>
      <startup>
        <supportedRuntime version="v2.0.50727"/>
      </startup>
    </configuration>
    

• Check queue manager and queue permissions
  The user account running runmqdnm needs sufficient permissions on the queue manager and target queue:

  # Grant queue manager connect/display permissions
  setmqaut -m myqmgr -t qmgr -p [your-username] +connect +dsp
  # Grant queue get/put/browse permissions (required for transactional monitoring)
  setmqaut -m myqmgr -n myqueue -t queue -p [your-username] +get +put +browse
  

  Replace [your-username] with the actual account you're using to run the command.

• Diagnose assembly dependency issues
  Compiling successfully doesn't guarantee all dependencies are present at runtime. Use the Assembly Binding Log Viewer (fuslogvw.exe) to check for failed dependency loads:

  1. Open fuslogvw.exe (part of the .NET Framework SDK).
  2. Configure it to log assembly binds to a directory.
  3. Run your runmqdnm command again, then check the logs for any missing or failed-to-load assemblies.
     Make sure all dependent DLLs are in the same directory as TransactionalMonitor.dll or registered in the Global Assembly Cache (GAC).

• Validate MQ installation and environment

  • Confirm you're using the WebSphere MQ 9.0 version of runmqdnm—if multiple MQ versions are installed, ensure the 9.0 bin directory is first in your system PATH or run the tool directly from the 9.0 installation folder.
  • Check that the MQ_INSTALLATION_PATH environment variable points correctly to your MQ 9.0 installation directory.

• Test with a minimal non-transactional monitor
  To rule out transaction-specific issues, create a simple monitor that implements IMQMonitor (not the transactional interface), compile it, and run it with runmqdnm. If this works, the problem is likely in your transactional monitor's implementation (e.g., incorrect interface methods, unhandled exceptions in initialization).

内容的提问来源于stack exchange，提问作者Marc Selis