Export (0) Print
Expand All

Troubleshoot Azure BizTalk Services

Updated: October 12, 2014

When troubleshooting Microsoft Azure BizTalk Services, you can use Tracking in the Microsoft Azure BizTalk Services Portal and use the Debug logs stored in the Storage account. This topic provides information on using the Tracking and Debug logs.


Every time the message sending client gets a response (whether it’s a failure or a success), the response header includes a tracking ID. In cases where there is a failure, you can extract this tracking ID from the header and use the Tracking Messages in BizTalk Services portal feature in Microsoft Azure BizTalk Services Portal to troubleshoot. The following code snippet demonstrates how to extract the tracking ID from the response:

byte[] requestBytes; // message transferred to bytes.

  WebClient webClient = new WebClient();                 
  UriBuilder builder = new UriBuilder(this.bridgeRuntimeAddress) { Scheme = Uri.UriSchemeHttps };

  // one can also use GetWebResponse instead of UploadData.
  byte[] responseBytes = webClient.UploadData(builder.Uri, "POST", requestBytes);

Catch (WebException we)
  Console.Writeline("Received WebException while sending message. Details: ");
  HttpWebResponse httpWebExceptionResponse = we.Response as HttpWebResponse;
  if (httpWebExceptionResponse == null)
    Console.Writeline("WebException contains no Http exception response. Status = {0}", we.Status);
    if (!String.IsNullOrEmpty(httpWebExceptionResponse.Headers["TrackingId"]))
      Console.Writeline ("TrackingId={0}", httpWebExceptionResponse.Headers["TrackingId"]);
      Console.Writeline ("Did not find TrackingId header on the WebException");
    Console.Writeline ("StatusCode = {0} and StatusDescription = {1}", httpWebExceptionResponse.StatusCode, 

Debug Logs

During the development process, debug logs are available in the WADLogsTable in the Storage Account. To view these log files, you can use the following tools:

The debug log files include the following events:

  • Loading an assembly

  • Adding or updating an artifact, like a Transform

  • Adding, updating, or deleting Bridge Configuration

  • Message submitted to the Bridge pipeline

  • Bridge stages including their Begin Execute and End Execute events

  • Faults

See Also

Community Additions

© 2014 Microsoft