Troubleshoot the BizTalk Adapter Service

 

Important

Microsoft Azure BizTalk Services (MABS) is being retired, and replaced with Azure Logic Apps. If you currently use MABS, then Move from BizTalk Services to Logic Appsprovides some guidance on moving your integration solutions to Logic Apps.

If you're brand new to Logic Apps, then we suggest getting started here:

• What are logic apps

• Create your first logic app, or quickly get started using a pre-built template

• View all the available connectors you can use in your logic apps

Enable tracing and performance counters in the BizTalk Adapter Service.

The BizTalk Adapter Service Runtime and BizTalk Adapter Service Management components use the .Net Framework System.Diagnostics trace source and the XML Trace Listener. In a BizTalk Adapter Service Runtime Application, tracing events can be enabled for the BizTalk Adapter Service Runtime and BizTalk Adapter Service Management components.

To enable runtime tracing

1. Go to the Microsoft BizTalk Adapter Service Runtime folder. By default, the folder is C:\Program Files\Microsoft BizTalk Adapter Service\BAServiceRuntime.

2. Open the web.config file in Notepad.

3. In the <configuration> node, add the following <system.diagnostics> section:

   <system.diagnostics>
      <sources>
         <source name="Microsoft.ApplicationServer.Integration.BAService.Runtime" switchValue="Information">
            <listeners>
            <add name="BAServiceRuntimeTrace" />
            </listeners>
         </source>
      </sources>
      <trace autoflush="true" />
      <sharedListeners>
         <add name="BAServiceRuntimeTrace" type="System.Diagnostics.XmlWriterTraceListener" initializeData="c:\temp\RuntimeTraceFile.xml" />
      </sharedListeners>
   </system.diagnostics>
   

   Important

   The trace file name and location can be any name and path you prefer. In the <sharedListeners> section above, RuntimeTraceFile.xml is the trace file name and is created in the c:\temp folder.

4. Within the <system.servicemodel> node inside the web.config, add the following <diagnostics> section:

   <diagnostics>
     <messageLogging
       logEntireMessage="true"
       logMalformedMessages="true"
       logMessagesAtServiceLevel="true"
       logMessagesAtTransportLevel="true"
       maxMessagesToLog="3000"
       maxSizeOfMessageToLog="2000"/>
   </diagnostics>
   

5. Save changes to the web.config.

To enable management tracing

1. Go to the Microsoft BizTalk Adapter Service Management folder. By default, the folder is C:\Program Files\Microsoft BizTalk Adapter Service\BAService.

2. Open the web.config file in Notepad.

3. In the <configuration> section, add the following <system.diagnostics> section:

   <system.diagnostics>
      <sources>
         <source name="Microsoft.ApplicationServer.Integration.BAService.Management" switchValue="Information">
            <listeners>
            <add name="BAServiceManagementTrace" />
            </listeners>
         </source>
      </sources>
      <trace autoflush="true" />
      <sharedListeners>
         <add name="BAServiceManagementTrace" type="System.Diagnostics.XmlWriterTraceListener" initializeData="c:\temp\ManagementTraceFile.xml" />
      </sharedListeners>
   </system.diagnostics>
   

   Important

   The trace file name and location can be any name and path you prefer. In the <sharedListeners> section above, ManagementTraceFile.xml is the trace file name and i created in the c:\temp folder.

4. Within the <system.servicemodel> node inside the web.config, add the following <diagnostics> section:

   <diagnostics>
     <messageLogging
       logEntireMessage="true"
       logMalformedMessages="true"
       logMessagesAtServiceLevel="true"
       logMessagesAtTransportLevel="true"
       maxMessagesToLog="3000"
       maxSizeOfMessageToLog="2000"/>
   </diagnostics>
   

5. Save changes to the web.config.

Supported switchValue options

BizTalk Adapter Service supports the following switchValue options:

• Off

• Critical

• Error

• Warning

• Information

• Verbose

• ActivityTracing

• All

Configuring Tracing lists the tracked events of the different Tracing levels.

To enable Performance Monitor counters

The BizTalk Adapter Service Runtime and BizTalk Adapter Service Management components utilize Performance Monitor. By default, these performance counters are enabled.

1. To enable or disable the Management performance counters:

   1. In IIS, expand Sites, and expand BizTalk Adapter Service.

   2. Select the BAService application and select Application Settings.

   3. To enable the performance counters, set EnablePerfCounter to True. To disable the performance counters, set EnablePerfCounter to False.

   Performance counters can also be enabled in the web.config file (\Program Files\Microsoft BizTalk Adapter Service\BAService):

   <appSettings>
       <add key="EnablePerfCounters" value="True" />
   </appSettings>
   

   When enabled, the BizTalk Adapter Service Management object is available in Performance Monitor with the following counters:

   • AverageTimeToCreateRelay

   • AverageTimeToCreateTarget

   • AverageTimeToDeleteRelay

   • AverageTimeToDeleteTarget

   • AverageTimeToUpdateRelay

   • AverageTimeToUpdateTarget

2. To enable or disable the Runtime performance counters:

   1. In IIS, expand Sites and expand BizTalk Adapter Service.

   2. Select the application that corresponds to the relay and select Application Settings.

   3. To enable the performance counters, set EnablePerfCounter to True. To disable the performance counters, set EnablePerfCounter to False.

   Performance counters can also be enabled in the web.config file (\Program Files\Microsoft BizTalk Adapter Service\BAServiceRuntime):

   <appSettings>
       <add key="EnablePerfCounters" value="True" />
       <add key="ReConnectIntervalInSeconds" value="30" />
   </appSettings>
   

   When enabled, the BizTalk Adapter Service Runtime object is available in Performance Monitor with the following counters:

   • AverageTimeToOpenChannel

   • AverageTimeToSend

Runtime URL: Unable to connect

During the BizTalk Adapter Service installation, you choose whether to allow SSL connections. The Runtime URL automatically defaults to HTTP or HTTPS depending on your SSL choice. In some scenarios, you may be unable to connect to the Runtime URL.

In the following scenarios, you may need to change from the default HTTP/HTTPS setting:

• You installed the BizTalk Adapter Service with the no SSL option. From another computer, you connect to the Runtime URL. In this scenario, you must enter HTTP for the Runtime URL:

  https://ServerName:8080/BAService/ManagementService.svc/

• You installed the BizTalk Adapter Service locally and allowed SSL connections. You reinstall the BizTalk Adapter Service and don’t allow SSL connections. In this scenario, you must enter HTTP for the Runtime URL:

  https://localhost:8080/BAService/ManagementService.svc/

See Also

Troubleshoot Azure BizTalk Services
Windows Performance Monitor