Error message when you try to configure the BizTalk Server 2006 R2 EDI/AS2 Runtime feature: "Failed to configure EDI/AS2 Status Reporting functionalities"

Article translations Article translations
Article ID: 939549 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

In Microsoft BizTalk Server 2006 R2, the EDI/AS2 Runtime feature configuration may fail. When this problem occurs, you receive an error message that resembles the following error message:
Error:
[12:09:24 PM Error EDIAS2Config] Failed to configure EDI/AS2 Status Reporting functionalities. (Microsoft.BizTalk.Configuration.EDIAS2.StatusReportingHelper)
Failed to deploy BAM activity definitions. Please make sure that all BAM related Data Transformation Services (DTS) packages are removed along with the BAM databases. (Microsoft.BizTalk.Configuration.EDIAS2.Utility)
Failed to execute process: C:\Program Files (x86)\Microsoft BizTalk Server 2006\Tracking\bm.exe. (Microsoft.BizTalk.Configuration.EDIAS2.Utility)
Microsoft (R) Business Activity Monitoring Utility Version 3.6.1230.0
Copyright (C) 2006 Microsoft Corporation. All rights reserved.
Using 'BAMPrimaryImport' BAM Primary Import database on server ‘SQL Server Name'...
Deploying Activity... ERROR: The BAM deployment failed.
DTS package BAM_DM_InterchangeStatusActivity already exists on server SQL Server Name.
(Microsoft.BizTalk.Configuration.EDIAS2.Utility)

CAUSE

The EDI/AS2 Runtime feature in BizTalk Server uses Microsoft SQL Server 2005 Integration Services (SSIS). This problem occurs if the EDI/AS2 Data Transformation Services (DTS) packages are not removed after you unconfigure the EDI/AS2 Runtime feature. Therefore, when you try to reconfigure BizTalk Server, the configuration process of the EDI/AS2 status reporting feature fails. Then, you receive the error message that is mentioned in the "Symptoms" section.

RESOLUTION

To resolve this problem, use one of the following methods.

Method 1: Use SQL Server Management Studio to remove the DTS packages

To resolve this problem, use SQL Server Management Studio to remove the DTS packages. To do this, follow these steps:
  1. Start SQL Server Management Studio, click Connect, and then select Integration Services.
  2. In the Server type box, click Integration Services, enter the server name that you want in the Server name box, and then click Connect.
  3. Expand Stored Packages, and then expand MSDB.
  4. Right-click BAM_DM_InterchangeStatusActivity, click Delete, and then click Yes.
  5. Repeat step 4 for the following packages:
    • BAM_DM_AS2InterchangeActivity
    • BAM_DM_AS2MessageActivity
    • BAM_DM_AS2MdnActivity
  6. Try to configure the BizTalk Server EDI/AS2 Runtime feature again.

Method 2: Use the Bm.exe utility to remove the DTS packages

To resolve this problem, use the Bm.exe utility to remove the DTS packages. To do this, follow these steps:
  1. Click Start, click Run, type cmd, and then click OK.
  2. Use the CD command to locate the folder where the Bm.exe file is located.

    Note By default, the Bm.exe file is located in the following folder:
    Microsoft BizTalk Server 2006\Tracking
  3. At the command prompt, type the following command, and then press ENTER:
    Bm.exe remove-all -DefinitionFile:folder\AS2ReportingActivityDefs.xml
    Note The folder placeholder is the folder where BizTalk Server 2006 R2 is installed.

    If you receive an error message that an activity could not be removed, go to step 4.
  4. At the command prompt, type the following command, and then press ENTER:
    Bm.exe remove-all -DefinitionFile:folder\EdiReportingActivityDefs.xml
    Note The folder placeholder represents the folder where BizTalk Server 2006 R2 is installed.
  5. Try to configure the BizTalk Server EDI/AS2 Runtime feature again.

MORE INFORMATION

Steps to reproduce the problem

  1. Install and configure the BizTalk Server 2006 R2 EDI/AS2 Runtime feature.
  2. Unconfigure BizTalk Server, and then uninstall BizTalk Server. When you uninstall BizTalk Server, the BAM definition files are not removed from SQL Server Integration Services because the BAM definition files may contain application-specific data.
  3. Reinstall BizTalk Server 2006 R2.
  4. Reconfigure the BizTalk Server 2006 R2 EDI/AS2 Runtime feature.

Properties

Article ID: 939549 - Last Review: April 7, 2010 - Revision: 2.0
APPLIES TO
  • Microsoft BizTalk Server 2006 R2 Standard Edition
  • Microsoft BizTalk Server 2006 R2 Enterprise Edition
  • Microsoft BizTalk Server 2006 R2 Developer Edition
Keywords: 
kbtshoot kbbtsbam kbbts kbprb KB939549

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com