Troubleshooting with .NET sample applications and error messages

You can use the .NET sample applications and error messages to help with troubleshooting problems.

Procedure

If an IBM® MQ .NET application 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 you need to contact the IBM Support team, you might be asked to turn on the trace facility. For information on using the trace facility, see Tracing IBM MQ .NET applications.
If the An unhandled exception of type System.IO.FileNotFoundException occurred in unknown module error occurs for either amqmdnet.dll or amqmdxcs.dll, take one of the following actions:
- Ensure that both are registered in the global assembly cache.
- Create a configuration file that points to the amqmdnet.dll and amqmdxcs.dll assemblies.
You can examine and change the contents of the assembly cache using mscorcfg.msc, which is supplied as part of .NET Framework.
If .NET Framework was unavailable when IBM MQ was installed, the classes might not be registered in the global assembly cache. You 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, which is logfile.txt in this example.