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


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)


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.


Cumulative update information

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


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

ID Artikel: 3029912 - Tinjauan Terakhir: 10 Okt 2015 - Revisi: 1