Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: Error message when you try to send a signed outgoing AS2/EDI message in BizTalk Server: "The Signing Certificate has not been configured for AS2 party"

FIX: Error message when you try to send a signed outgoing AS2/EDI message in BizTalk Server: "The Signing Certificate has not been configured for AS2 party"

View products that this article applies to.

Symptoms

Consider the following scenario:
  • On a computer that is running BizTalk Server 2006, BizTalk Server 2006 R2, or BizTalk Server 2009, you create a BizTalk server host instance. 
  • You rename the BizTalk group. 
  • You configure a BizTalk application to sign outgoing AS2/EDI messages.
In this scenario, BizTalk Server suspends outgoing messages. Additionally, events that resemble the following are logged in the Application log:
Event 1:
Event Type: Error
Event Source: BizTalk Server 2006 EDI
Event Category: None
Event ID: 8132

Description:
A BTS MIME error was encountered when you try to encode a message. Error: The Signing Certificate has not been configured for AS2 party. AS2-From: <AS2-From party> AS2-To: <AS2-To party>

Event 2:
Event Type: Error
Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006
Event ID: 5720

Description:
There was a failure executing the send pipeline: "Microsoft.BizTalk.EdiInt.DefaultPipelines.AS2Send, Microsoft.BizTalk.Edi.EdiIntPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "AS2 encoder" Send Port: "<send port>" URI: "<URI>" Reason: The Signing Certificate has not been configured for AS2 party. AS2-From: <AS2-From party> AS2-To: <AS2-To party>

Event 3:
Event Type: Error
Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006
Event ID: 5754

Description:
A message sent to adapter "HTTP" on send port "<send port>" with URI "<URI>" is suspended.

Error details: There was a failure executing the send pipeline: "Microsoft.BizTalk.EdiInt.DefaultPipelines.AS2Send, Microsoft.BizTalk.Edi.EdiIntPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "AS2 encoder" Send Port: "<send port>" URI: "<uri>" Reason: The Signing Certificate has not been configured for AS2 party. AS2-From: SandvikAS2 AS2-To: 5565782504AS2

MessageId: {<messsage ID>}
InstanceID: {<instance ID>}

Note By default, the outgoing AS2 messages are signed by using a default group signature certificate that is defined as part of the BizTalk Group properties. The issue does not occur when you configure the AS2 party to use a specific certificate to sign the outgoing messages.

↑ Back to the top

Cause

The issue occurs because the startup parameter of the BizTalk host instance includes the BizTalk group name. If you rename the BizTalk group after you create the BizTalk host instance, the old BizTalk group name is not updated with the new BizTalk group name in the startup parameter. This makes BizTalk server unable to find the group signature certificate when the BizTalk host instance in running.

↑ Back to the top

Resolution

Hotfix information

Note A hotfix is available to resolve this issue in BizTalk Server 2006 R2. If you are using BizTalk Server 2006 or BizTalk Server 2009, see the "Workaround" section. 

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have BizTalk Server 2006 R2 Service Pack 1 (SP1) installed to apply this hotfix. To obtain BizTalk Server 2006 R2 SP1, visit the following Microsoft Download Center website: 
BizTalk Server 2006 R2 SP1
Additionally, the following components have some corresponding hotfixes in this hotfix. To apply the corresponding hotfixes, the component must be installed.
  • Microsoft BizTalk Adapters for Enterprise Applications (also known as BizTalk LOB Adapters)
  • Microsoft BizTalk Accelerator for HL7 2.0
  • Microsoft BizTalk FileAct and InterAct Adapters for SWIFT 2.3 SP1
If a Readme.txt file is included in this hotfix, see the Readme.txt file for more information about how to install this hotfix.

Restart requirement

You may have to restart the computer after you apply this hotfix.

File information

The English (United States) version of this hotfix uses a Microsoft Windows Installer package to install the hotfix. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
File nameFile versionFile sizeDateTimePlatform
Admin_server_logic.sqlNot applicable72,80007-Jul-201116:18Not applicable
Bts_administration_logic.sql.enNot applicable468,35007-Jul-201116:18Not applicable
Bts_deployment_logic.sqlNot applicable97,48207-Jul-201116:18Not applicable
Microsoft.xlangs.basetypes.dll3.6.2224.12104,31207-Jul-201116:18x86

↑ Back to the top

Workaround

To work around this issue, follow these steps:
  1. Update the BizTalkGroupName registry entry of the following locations with the new group name:
    HKEY_LOCAL_MACHINE\Software\Microsoft\BizTalk Server\3.0\Administration
    HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\BizTalk Server\3.0\Administration
  2. Use either of the following two methods:
    • In the following registry entry, manually update the -group startup parameter in the ImagePath value to include the new group name:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTSSvc$<BizTalk host name>
      For example, update the ImagePath value as follows:
      "C:\Program Files\Microsoft BizTalk Server 2006\BTSNTSvc.exe" -group "New BizTalk group name" -name "BizTalk host name" -btsapp "{guid}"
    • Delete the BizTalk host instance and re-create it after you rename the BizTalk group.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

For more information about how to configure certificates for use with AS2, visit the following MSDN webpage:
Configuring Certificates for AS2
For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
2003907 Information on BizTalk Server hotfixes

↑ Back to the top

Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbexpertiseinter, kbsurveynew

↑ Back to the top

Article Info
Article ID : 2482548
Revision : 2
Created on : 9/10/2018
Published on : 9/11/2018
Exists online : False
Views : 313