Troubleshooting IBM MQ .NET problems

We can use the .NET sample applications to help with troubleshooting problems.

Use the sample applications

If a program does not complete successfully, run one of the .NET sample applications, and follow the advice given in the diagnostic messages. These sample applications are described in Sample applications for .NET.

If the problems continue and we need to contact the IBM service team, you might be asked to turn on the trace facility. For information on using the trace facility, see Tracing IBM MQ .NET programs.

Error messages

We might see the following common error message:

An unhandled exception of type System.IO.FileNotFoundException occurred in unknown module

If this error occurs for either amqmdnet.dll or amqmdxcs.dll, either ensure that both are registered in the Global Assembly Cache or create a configuration file that points to the amqmdnet.dll and amqmdxcs.dll assemblies. We can examine and change the contents of the assembly cache using mscorcfg.msc, which is supplied as part of the .NET framework. If the .NET framework was unavailable when IBM MQ was installed, the classes might not be registered in the global assembly cache. We can manually rerun the registration process using the command

amqidnet -c MQ_INSTALLATION_PATH\bin\amqidotn.txt -l logfile.txt

MQ_INSTALLATION_PATH represents the high-level directory in which IBM MQ is installed.

Information about this installation is written to the specified log file ( logfile.txt in this example).

Parent topic: Getting started with IBM MQ classes for .NET