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: "Some of the X12 protocol properties are invalid" error when you export Global Party settings from BizTalk Server 2010 to BizTalk Server 2013

FIX: "Some of the X12 protocol properties are invalid" error when you export Global Party settings from BizTalk Server 2010 to BizTalk Server 2013

View products that this article applies to.

Symptoms

Consider the following scenario:

  • You have a BizTalk Server 2010 environment and a BizTalk Server 2013 environment.
  • You export a binding file that contains Global Party settings from BizTalk Server 2010, and then you import the binding file into BizTalk Server 2013.
In this scenario, you receive the following error message when you import the binding file:

Failed to update binding information. (mscorlib)
===================================
Some of the x12 protocol properties are invalid. (Microsoft.BizTalk.B2B.PartnerManagement)
------------------------------
Program Location:
at Microsoft.BizTalk.B2B.PartnerManagement.X12ProtocolSettings.Microsoft.BizTalk.B2B.PartnerManagement.ISaveCallback.OnSave(TpmContext context)
at Microsoft.BizTalk.B2B.PartnerManagement.TpmContext.OnSavingChanges(Object sender, EventArgs args)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Data.Objects.ObjectContext.OnSavingChanges()
at System.Data.Objects.ObjectContext.SaveChanges(SaveOptions options)
at Microsoft.BizTalk.B2B.PartnerManagement.TpmContext.SaveChanges(Boolean acceptChangesDuringSave)
at Microsoft.BizTalk.B2B.PartnerManagement.TpmContext.SaveChanges()
at Microsoft.BizTalk.Deployment.B2B.PartnerManagement.DeploymentManager.SaveData(PartyCollection data, Boolean bindingActionOverwrite) at Microsoft.BizTalk.Deployment.Binding.BindingInfo.UpdateParties(String connectionString, Boolean overwrite)
at Microsoft.BizTalk.Deployment.Binding.BindingInfo.Update(SqlConnection sqlConnection, BindingParameters bindingParameters, String applicationName)

↑ Back to the top

Cause

This issue occurs because some enabled Global Party settings are changed when the binding file is are imported into BizTalk Server 2013. For example, the Functional Acknowledgement Version setting in the Acknowledgements section is changed to FunctionalAckVersion when the binding file is imported into BizTalk Server 2013.

↑ Back to the top

Resolution

Cumulative update information

The fix that resolves this issue is included in Cumulative Update 3 for BizTalk Server 2013.

↑ 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

Keywords: kbqfe, kbfix, kbexpertiseinter, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 3029912
Revision : 1
Created on : 1/7/2017
Published on : 10/10/2015
Exists online : False
Views : 306