BizTalk Server 2013 Hot fixes

While configuring BAM section, BizTalk configuration tool completes the action with error that is detailed in log file. The error is classic access problem to SQL database. “A network-related or instance-specific error occurred” is irrelevant because the users that will do operation in sql database are defined on the database. I have searched the problem through the internet and have found the solution which is all related with a bug. Microsoft has launched the hot fixes in order to solve that kind of problems.

 

To apply this cumulative update package, you must have BizTalk Server 2013 installed.

Cumulative update package 1 for BizTalk Server 2013 – here

• FIX: User cannot perform certain database-related operations in BizTalk Server 2013 
• FIX: The vertical scroll bar on the target schema does not work correctly when you use Visual Studio to design a BizTalk Server 2013 map
• FIX: BAM tools cannot be configured in a multi-node BizTalk Server 2013 environment

 

Cumulative update package 2 for BizTalk Server 2013 – here

• FIX: The value for the “maxOccurs” attribute is invalid when you validate the BizTalk X12 EDI 835 schema in a BizTalk EDI application in BizTalk Server 2010 or in in BizTalk Server 2013
• FIX: The memory that a BizTalk host process consumes increases when there are no messages in the queue in BizTalk Server 2010 or in BizTalk Server 2013
• FIX: “The InnerText property is write only” error message when you use System.Xml.XmlDocument in BizTalk Server 2010 or in BizTalk Server 2013
• FIX: Pipeline on receive locations reverts to pass-through after you update the schema assembly in BizTalk Server 2010 or in BizTalk Server 2013
• FIX: “Could not load file or assembly ‘Microsoft.BizTalk.Interop.SSOClient Version=5.0.1.0” error when you use the ESB configuration tool in BizTalk Server 2013
• FIX: SQL connection leak when you use WCF-based SQL Adapter one-way send port to return a result set from a database in BizTalk Server 2010 or in BizTalk Server 2013
• FIX: 2-way WCF-BasicHttp receive port does not respond to a WCF client when the “failed message routing” feature is enabled in BizTalk Server 2010 or in BizTalk Server 2013
• FIX: Message is suspended when you try to receive an encrypted AS2 message together with asynchronous MDN in BizTalk Server 2010 or in BizTalk Server 2013
• FIX: An update for Message Box Viewer is available in Microsoft BizTalk Server 2013 cumulative update 2
• FIX: Support for HIX EDI transactions 005010×306 (820) and 005010×220 (834) for BizTalk Server 2013, BizTalk Server 2010, and BizTalk Server 2009
• FIX: XpathMutatorStream class does not work as expected when you execute Xpath statements against XmlDocuments in BizTalk Server 2013
• FIX: BizTalk Server 2013 cannot receive the messages from the view in document library or from the SharePoint online library
• FIX: High CPU usage after you install BizTalk Server 2013 and SQL Server 2012 on a computer
• FIX: “System.ArgumentException” error when you browse WCF services from ESB Toolkit 2.2 in BizTalk Server 2013