Skip to main content

BizTalk Server Troubleshooting and Support

Search MSDN Online, the Microsoft Knowledge Base, and MSDN Blogs to locate resources to assist you with troubleshooting.

Advanced KB Search

EDI Leap Year hotfix: BizTalk 2009 and BizTalk 2006 R2

If using EDI in BizTalk 2009 and BizTalk 2006 R2, install the EDI leap year hotfix before 2/29/12:

2435900   FIX: "Invalid Date" EDI interchange error occurs in BizTalk Server 2006 R2 or in BizTalk Server 2009 if a data element contains a leap date value

BizTalk Server 2009

There are two ways to get this fix:

Option 1: Install any BizTalk 2009 Cumulative Update. KB 2555976 lists the available cumulative updates.

Option 2: Install the stand-alone fix by clicking View and request hotfix downloads at the top of KB article 2435900. This fix applies to 32-bit (x86) and 64-bit (x64) computers.

BizTalk Server 2006 R2

Each step is required:

  1. Install BizTalk 2006 R2 Service Pack 1.
  2. Install BizTalk 2006 R2 Service Pack 1 Cumulative Update 3.
  3. Install the stand-alone fix by clicking View and request hotfix downloads at the top of KB article 2435900. This fix applies to 32-bit (x86) and 64-bit (x64) computers.

Note BizTalk Server 2010 is not impacted by this bug.

Cumulative Update

For a list of a BizTalk Server and BizTalk Adapter Pack Service packs and cumulative updates, refer to KB article 2555976:

Service Pack and Cumulative Update list for BizTalk Server

As of December 2010, BizTalk Server has moved towards the Cumulative Update model for BizTalk Server 2009 and BizTalk Adapter Pack 2.0.

Newly Released Hotfixes and Updates

Get information about BizTalk Server newly released hotfixes and updates.

Common Call Generators

During the install the ESB Toolkit 2.1, the BAM definitions are installed using the following command line syntax:

bm.exe deploy-all -DefinitionFile:"C:\Program Files (x86)\Microsoft BizTalk ESB Toolkit 2.1\Bam\Microsoft.BizTalk.ESB.BAM.Exceptions.xml"

When this occurs, an error similar to the following may return:

Microsoft (R) Business Activity Monitoring Utility Version 3.9.469.0
Copyright (C) Microsoft Corporation. All rights reserved.

Using 'BAMPrimaryImport' BAM Primary Import database on server 'SQLServer'...

Deploying Activity... Done.
Deploying View... ERROR: The BAM deployment failed.
Internal error: The operation terminated unsuccessfully.
OLE DB error: OLE DB or ODBC error: Cannot open database "BAMStarSchema" requested by the login. The login failed.; 42000.
Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'bam_ExcByApplication', Name of 'bam_ExcByApplication'.
Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'ExcByApplication_Application', Name of 'ExcByApplication_Application'was being processed.
Errors in the OLAP storage engine: An error occurred while the 'Year' attribute of the 'ExcByApplication_ExcDatetime' dimension from the 'BAMAnalysis' database was being processed.
Server: The operation has been cancelled.



The accounts running the SQL Server services need Read access to the BAMStarSchema database:

  1. Open SQL Server Management Studio, select Database Engine and click Connect.
  2. Expand Databases, expand BAMStarSchema, expand Security and expand Users.
  3. Double-click the account running the SQL services. If the account is not listed, right-click Users, select New User and add the account.
  4. In General under Database role membership, check db_datareader.

A New Query with the syntax below can also be used:

USE BAMStarSchema
CREATE USER SQLServerAccountName FOR LOGIN SQLServerAccountName
EXEC sp_addrolemember ‘db_datareader’, ‘SQLServerAccountName

Online Resources
Installing the BizTalk ESB Toolkit Core

Microsoft BizTalk Server 2010 ESB Toolkit

When the HTTP or SOAP adapter is used, a client SSL certificate can be used by adding the certificate thumb print to a send port. In this scenario, you may receive an error similar to the following:

Event Type: Warning
Event ID: 5743
The adapter failed to transmit message going to send port "SendPortName" with URL "". It will be retransmitted after the retry interval specified for this Send Port.
Details: "The client certificate is not found in the certificate store.
Parameter name: Certificate".



Confirm the following:

  • The certificate is in Personal store of the BizTalk Service account.
  • The correct certificate thumb print is specified.
  • The private client certificate is being used. Private certificates have a .pfx extension. Public certificates have a .cer extension.

When using AS2 to receive a message in BizTalk Server 2010, the message is suspended with the following error:

An output message of the component "Unknown " in receive pipeline "Microsoft.BizTalk.EdiInt.DefaultPipelines.AS2EdiReceive, Microsoft.BizTalk.Edi.EdiIntPipelines, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35" is suspended due to the following error:
     Error: 1 (Field level error)
            SegmentID: UNB
            Position in TS: 1
            Data Element ID: UNB2.2
            Position in Segment: 3
            Position in Field: 2
            Data Value: 16
            12: Invalid value in data element.
The sequence number of the suspended message is 2.


The issue can occur if the IIS application pool used by the receive location is not using .Net 4.0. The application pool must be using .Net 4.0 to access the BizTalk AS2/EDI artifacts.

When custom components, like pipeline components or a custom adapter, are added, you modify the BizTalk configuration file: BTSNTSvc.exe.config or BTSNTSvc64.exe.config. After the modification, the BizTalk service fails to start and returns the following error:

A failure occurred when executing a Windows service request.
Service request: Start
BizTalk host name: BizTalkServerApplication
Windows service name: BTSSvc$BizTalkServerApplication

Additional error information:
Error code: 0x80131604
Error source: mscorlib
Error description: Exception has been thrown by the target of an invocation.


The <configSections> element must be the first element in the configuration file. To resolve this error, move the <configsections> element to the top of the configuration file.

When configuring the BizTalk Runtime using local groups in the BizTalk Configuration wizard, you may receive the following error:

No mapping between account names and security IDs was done.


When entering the group names, enter MachineName\GroupName. For example, enter MachineName\BizTalk Application Users and MachineName\BizTalk Isolated Host Users.

You are using BizTalk and installed a Cumulative Update. You unconfigure BizTalk and then reconfigure BizTalk, which succeeds. You notice some tables, including EdiMessageContent and EdiMessagePartContent, and some stored procedures are missing.


Reinstall the Cumulative Update.

When using the SMTP adapter for the first time, you may receive the errors below:

A message sent to adapter "SMTP" on send port "SendPortName" with URI "" is suspended.
Error details: The property sheet field "SMTP Server Name" is not configured for the BizTalk.SendSMTP transport component. 
MessageId:  {8021090F-ACD0-4FA4-B380-2FBA49345489}
InstanceID: {CCCC50CB-2C23-4D08-AC18-2B0C7707F899}

A message sent to adapter "SMTP" on send port "SendPortName " with URI "" is suspended.
Error details: The property sheet field "From" is not configured for the BizTalk.SendSMTP transport component. 
MessageId:  {E70027AA-0C9E-4ADD-84F3-FC6E92159109}
InstanceID: {0BDA2E23-BE2D-4E3D-A86E-7D10E6C330DA}



When using the SMPTP adapter for the first time, additional configuration is needed:

  1. Open BizTalk Administration and expand the Group.
  2. Expand Platform Settings, expand Adapters and select SMTP.
  3. Double-click the Send Handler to open the properties page. Click the Properties button and enterthe SMTP Server Name and a From address.

Symptom: If you send messages to J. D. Edwards by using the J. D. Edwards adapter, you achieve good performance if you keep sending messages. If you stop sending messages for couple minutes, however, the next message will take a long time to be sent to J. D. Edwards.


The delay is caused by the startup of RuntimeAgent.exe. By default, RuntimeAgent.exe will automatically shut down if it is idle for one minute. If you have applications with a low latency requirement, you can adjust the registry value AgentOutboundTimeout to avoid or reduce the automatic shutdowns and restarts of RuntimeAgent.exe.

In the registry, follow these steps, and then quit Registry Editor:

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate, and then select the following key in the registry:
    • 32-bit: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalkAdapters
    • 64-bit: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\BizTalkAdapters
  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Type AgentOutboundTimeout, and then press ENTER.
  5. On the Edit menu, click Modify.
  6. Select Decimal, type your value, and then click OK.

The AgentOutboundTimeout value is used to recycle the RunTimeAgent processes after a certain time of inactivity. The value should be set so it is more than the time it takes for the operation to complete on the Oracle server. The default value is 60000 milliseconds (1 minute).

For more information, see

Symptom: Using the SOAP adapter, you may receive an error of “There is an error in XML document (1, 2608)” like this:

A response message sent to adapter "SOAP" on receive port "WebPort_MyBusiness/MyBusiness_Request" with URI "/MyBusiness/MyBusiness_Request.asmx" is suspended.
Error details: There is an error in XML document (1, 2608).
MessageId: {588B7295-6FBB-48F8-9853-7EF881CFE82B}
InstanceID: {F8D3E588-609F-469C-BDB6-2109AB3C2333}.


This error happens because of the failure in deserializing the response message. Check the bts_DocumentSpec table of BizTalkMgmtDB to make sure there are no duplicate document specifications related to the response message type.

For example, suppose you have two duplicate entries in the msgtype column of the bts_DocumentSpec table for the message type Vehicle. One entry defines the Vehicle type as a string, and another entry defines the Vehicle type as an integer. When BizTalk receives a message that contains a string as Vehicle, it might fail with an InvalidOperation exception and throw the error of "There is an error in XML document (1, 2608)".

Symptom: When installing a BizTalk Server 2010 cumulative update, the DTA Purge and Archive SQL Agent job settings might be reset to the default values.


To work around this, open SQL Server Management Studio, expand SQL Server Agent and modify the DTA Purge and Archive SQL Agent job steps to the previous values. How to Configure the DTA Purge and Archive Job provides the specific steps.

Symptom: When installing a BizTalk Server 2009 cumulative update, Execute permissions on the dtasp_MsgIn, dtasp_MsgOut and dtasp_ServiceInsert stored procedures in the BizTalkDTADb database might be removed.


To resolve this, open SQL Server Management Studio, and do the following:

  1. Expand Databases, expand BizTalkDTADb, expand Programmability, and then expand Stored Procedures.
  2. Right-click dtasp_MsgIn, and then select Properties.
  3. Select Permissions.
  4. If BizTalk Application Users is not listed, click the Search button to find this group. If BizTalk Application Users is listed, click the Execute option under Grant.
  5. Click OK to save the changes.

Follow these steps for the dtasp_MsgOut and dtasp_ServiceInsert stored procedures.

Symptom: You have a BizTalk receive location. The message received from this receive location is sent to a backend system like SAP. You want to use Single Sign On (SSO) for this message flow.  Some adapters, such as WCF-Basic and SOAP, have built-in functionality to issue the SSO ticket. For other adapters you can create a custom pipeline component to be used in the receive pipeline to issue the SSO ticket.  The ticket is redeemed during the SAP send port processing.

Assume that the receive location is running in a host with a service account Domain\Account1.  When you log on as Domain\Account1 and send a message to the receive location, it will be successful.  But if you are not logged on as Domain\Account1, it will fail with this message:

Validation of the ticket failed. The sender name must match that of the ticket issuer.
Application Name: My SAP Affiliate App
Ticket Issued By: Domain\Account1
Sender Name: Domain\Account2

The problem is caused by the mismatch of the sender and the issuer.  In this example, the sender is Domain\Account2; but the issuer is Domain\Account1.  The sender is usually the account that sends the message to the receive location. The issuer is the service account of the BizTalk host instance, inside which the receive location is running.


There are two ways to remove this error condition:

  1. Set the BizTalk host as non-trusted. A non-trusted host will always set its service account (Domain\Account1) as the sender.
  2. Turn off SSO ticket validation.

Symptom: BizTalk Server installation fails with an error message that says “5008 Registration of BizTalk WMI provider failed. Return code 1”. The problem usually happens when you are installing BizTalk Server on a computer that previously had BizTalk Server installed and subsequently uninstalled.


Copy BTSWMISchema.mof, BTSWMISchema.mof, and BTSWMISchemaXP.mof from a good installation computer to the local C:\Program Files\Microsoft BizTalk Server 2006\Bins32\ folder, and then start the BizTalk Server installation.

Symptom: In BizTalk Server 2010, you might receive the following exception when enlisting an orchestration. This happens when your orchestration defines a correlation set type with data types from a different assembly other than the orchestartion assembly. For instance, the following error happens when a correlation set is defined with MyScehma.Schemas.ID type from a MySchema.Schemas.dll assembly.

Exception type: BTXEnlistmentException
Additional error information:
Exception type: TypeLoadException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: System.Guid[] GetCreateServiceConvoySets(Microsoft.BizTalk.Agent.Interop.IBTMessageBatchEx, Microsoft.BizTalk.Agent.Interop.IBTMessageAgentFactory)


You can work around the problem by combining the data type (schema) project and the orchestration project into one single project.

Symptom: BizTalk Server is installed in \Program Files instead of \Program Files (x86). A Windows Installer package is imported and the following error is logged:

Event ID: 11721
Product: Not x86 -- Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: CA_Install, location: C:\Program Files (x86)\Generated by BizTalk\Not x86\13B141CC-B7D4-4773-B5D8-968FFFE6FE74\, command: C:\Program Files (x86)\BTS2010\CustomAction.exe /installtype=notransaction /action=install /LogFile= /LOGFILE="" /PRODUCTNAME="Not x86" /PRODUCTVERSION="" /PRODUCTCODE="{13B141CC-B7D4-4773-B5D8-968FFFE6FE74}" /UILEVEL=5 /EXTRACTCABSONLY= /NOINSTALL= /DEPLOY= /MSITargetDir="C:\Program Files (x86)\Generated by BizTalk\Not x86\13B141CC-B7D4-4773-B5D8-968FFFE6FE74\\" "" "C:\Users\ADMINI~1\AppData\Local\Temp\CFGCBC9.tmp"


To resolve this, create a folder named C:\Program Files (x86)\Microsoft BizTalk Server 2010. Copy CustomAction.exe and CustomAction.exe.config from the BizTalk installation folder to this folder. Installation of the Windows Installer package (MSI) should now succeed.

This is a known MSI limitation. On 64-bit machines, 32-bit MSIs append (x86) to the “\Program Files”’ path before using it. BizTalk application MSIs are always 32-bit. Starting with BizTalk Server 2010, the MSI executes CustomAction.exe in the BizTalk installation folder. In previous BizTalk versions, the custom actions were embedded within the application MSI as a dynamic-link library (DLL). This limitation was also there earlier, but it was not seen in this scenario.


Symptom: When installing Enterprise Single Sign-On in BizTalk Server 2010 on a Windows 7 64-bit computer, the following error might occur:

Error 1928.Error registering COM+ application. Please ensure that DTC is enabled. Contact your support personnel for more information.
If you open Component Services, you might see a red arrow next to My Computer. Selecting COM+ Applications may return error:
You do not have permission to perform the requested action. If security is enabled on the System Application of the target computer make sure you are included on the appropriate roles.


This can happen if Windows Easy Transfer was used. To resolve this, use the Easy Transfer tool on a working Windows 7 64-bit computer. For migration, select SharedItems, and then select Windows Settings. Import this into the failing computer. You might also be able to download a .mig file that contains just these items. For more information, see
Permission error when trying to access COM+ applications under Component Services.

Symptom: After installing a cumulative update package, you might encounter a crash when you open the BizTalk Server Administration console. Also, the follow error is logged in the event log: “EventType clr20r3, P1 mmc.exe, P2 5.2.3790.3959, P3 45d6a11d, P4 microsoft.biztalk.administration.ediext, P5, P6 4d7e5b5f, P7 225, P8 0, P9 system.nullreferenceexception, P10 NIL”.

This problem usually happens when the BizTalk Server Administration console is installed on a separate computer, and it is at a different cumulative update package level than the computers running BizTalk Server. To fix the problem, make sure the computer with the BizTalk Server Administration console has the same cumulative update package installed as any other computer running BizTalk Server in the group does.


Symptom: You experience the issue in You understand that the fix is included in BizTalk Server 2009 Cumulative Update (CU) 2 from After installing the CU2, you find the issue is still unresolved.

The fix involves some schema changes. The schema change is not automatically applied by the CU2 installation. After installation, you can unzip MicrosoftEdiXSDTemplatesKb2191569.exe to obtain the changed schemas. MicrosoftEdiXSDTemplatesKb2191569.exe is part of the CU2 package.


Symptom: The BAM tracking tables in Messagebox are increasing in size very fast. Data is being moved from BAM tracking tables in MessageBox to BAMPrimaryImport, but at a very slow pace. The TDDS_FailedTrackingData table is also growing at a slow pace with errors like "TDDS failed to execute event. Parameter is not valid." You check the Windows event log, and find no errors or warnings.

The issue can happen when you use BufferedEventStream (vs DirectEventStream), and there is some problem in the event data. BufferedEventStream uses an asynchronous pattern, so there are no immediate errors/warnings to indicate any problem in the event data. A common problem in the event data is invalid activity. You can monitor these two performance counters: “Total Failed Batches” and “Total Failed Events.” If they are large and increasing, you may want to double-check any possible problem in the event data, for example, whether the activity name is valid. For debugging purposes, you can temporarily replace BufferedEventStream with DirectEventStream. DirectEventStream is synchronous, and will show the errors immediately.


Symptom:In the BizTalk group, there are two BizTalk computers. On BizTalk1, there is an isolated host. On BizTalk2, a client application submits messages to the isolated host on BizTalk1. This returns the following error: “The Messaging Engine failed to register the adapter for "Submit" for the receive location "Test Receive Location". Please verify that the receive location exists, and that the isolated adapter runs under an account that has access to the BizTalk databases.”

This error occurs even when the account is a member of the BizTalk Isolated Host Users group.

Create the isolated host instance on the BizTalk computer that hosts the client application.


Symptom:There is a BizTalk application that used Pipeline1 and now uses Pipeline2. The BizTalk application is deployed. You modify the application in Visual Studio and redeploy from Visual Studio. When you redeploy, Pipeline1 is used instead of Pipeline2.

This occurs when a binding file from a previous deployment is applied. To resolve this, delete the residue binding file and then redeploy. Binding file locations:
C:\Documents and Settings\{user}\Application data\Microsoft\BizTalk Server\Deployment\BindingFiles


More Common Call Generators...

Potential Scenarios

Scenario 1: Once you have implemented the BizTalk Enterprise Service Bus (ESB) Toolkit, you can use the Management Portal to perform some very useful operations, like managing exceptions, registering UDDI, auditing, viewing history information, and configuring alerts and notifications. The Management Portal is hosted in IIS on BizTalk Server, and usually you want to be able to view it from remote computers.

To connect to the Management Portal from a remote computer with Internet Explorer:

  1. Enable Integrated Windows Authentication in Internet Explorer.
  2. Set registry value HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\EnableNegotiate to 1.
  3. On the server with the Management Portal, modify the group policy or local security policy, so that the Internet Explorer user account and the BizTalk Server machine account are trusted for delegation.

For detailed instructions, see How to configure an ASP.NET application for a delegation scenario.

Scenario 2: Visual Studio 2008 fails to open/create a BizTalk Server 2009 project. This is caused when Visual Studio 2008 is repaired or when a Visual Studio 2008 update is installed; the registry entry is inadvertently changed from csproj;btproj to csproj. You can resolve this as follows:

  1. Locate the following key in the Windows Registry:
    • For 32-bit versions of Visual Studio 2008:
    • For 64-bit versions of Visual Studio 2008:
  2. Change "PossibleProjectExtensions"="csproj" to "PossibleProjectExtensions"="csproj;btproj"

For more information, see Visual Studio 2008 fails to create new BizTalk projects from the BizTalk Customer Response Team blog.

Scenario 3: You process a load of messages and notice that the message process time slows down. This could be caused by the Message count in database setting. By default, it is set to 50,000 messages; it can be increased to allow for a burst of messages. A good starting number is 75,000, if you suspect this to be a problem.

Scenario 4: A System.OutOfMemory exception can occur with a Host instance. There could be many reasons for this, but increasing the Process memory usage setting can help. On a 32-bit server, setting this to 50 is a good value. On a 64-bit server, it can be set to 100. For troubleshooting and potential design issues, see KB article 918643: How to troubleshoot a memory leak or an out-of-memory exception in the BizTalk Server process.

Scenario 5: “The Signing Certificate has not been configured" error occurs using BizTalk EDI. For information, see KB article 971193: "The Signing Certificate has not been configured" error using certificates with EDI/AS2. Also, confirm that the BizTalk Group name in BizTalk Administration is "BizTalk Group."


Ask an Expert Online

Search and Post a New Question to the MSDN Forums
The MSDN BizTalk Server Forums allow you to search an array of technical questions and answers. You can also ask a new question, be notified when there are replies, and mark the appropriate reply as an answer.

Get Help from Microsoft

Assisted Support

Contact a Microsoft Support Professional.

Assisted Support for MSDN Subscribers

Use a Technical Support incident provided with your MSDN Subscription for assistance with technical break-fix issues that you encounter in a non-production environment.

Autres options de support