Appendix 2 - Troubleshooting

Retired Content

This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

This section contains the following troubleshooting tables:

  • Installation
  • General Issues



You receive an "Error assigning permissions" exception during installation.

The ESB Guidance uses the standard BizTalk account groups, which must exist during the installation process or the installation will fail. In addition, the guidance assumes either a standalone installation where the computer is a member of a workgroup or an enterprise installation where the computer is a member of a domain.

You receive a "Failed to deploy tracking profile, assembly not found" exception message while running the deploy_exception_tracking.cmd program.

Ensure that BAM is installed correctly in the BizTalk environment and that the ESB Guidance BAM installation files are present. The installation assumes BizTalk is installed in the default path.

Application import fails with an error message that warns of trust level mismatch.

The Microsoft.BizTalk.ESB binding files are configured to work with the default BizTalkServerApplication and BizTalkServerIsolatedHost, which are in turn configured to execute in untrusted mode. If you have changed your host to run in trusted mode, the binding file will not import. To correct this, you must either change the trust level to untrusted or edit the binding file to suit your environment.



You receive an "Internal SOAP Processing" exception when sending a message to the generic ESB Itinerary On-Ramp Web service.

Use the BizTalk Server Administration Console to ensure that the Microsoft.Practices.ESB application is running; if it is not running, start it.

You receive a "Fatal error C1083: Cannot open include file: 'cmqc.h': No such file or directory" exception while building the JMS component.

The header file that the project references is part of the IBM WebSphere MQ Series installation. You must install this; if you do not install it, you will not be able to build this project.

Exception messages are not appearing in the ESB Management Portal site.

Check the BizTalk Administrator Group Overview page and the Windows Application Event Log for entries that indicate failures to send messages. You may need to reconfigure the exception Send Adapter (part of the Microsoft.Practices.ESB application) to match your environment. In addition, be aware that both the BizTalk Failed Message Routing feature and the ESB Guidance Exception Management Framework generate exceptions messages. Therefore, ensure that you enable the Route on Failed Messages option for send and receive ports.