BizTalk 2013 R2 known bugs, issues & quirks

Featured

I’ve now posted the below article on a TechNet wiki

Below a list of know bugs, issues, & other quirks* of BizTalk 2013 R2 (mainly CU3) and Visual Studio 2013 (update 4) , but I will update with fixes as the CUs come out or when I know about a new issue, so if you have another one I will add it (and link to it if you have a blog about it) if you let me know.  This in addition to the ones listed by Microsoft on Known Issues in Installation, Configuration, and Deployment

* My definitions for classifying these are
Bug
: Causes negative impact and no known work around or requires a lot of effort to work around.
Issue: Causes negative impact but has an easy or quick work around.
Missing: A feature that BizTalk doesn’t have that would make our life easier.
Quirk:  Something strange or unusual but does not cause a negative impact so far as known.

Continue reading

Advertisements

PURGE Everything in the DTA #msbts

Tags

, ,

Due to too much message body tracking after a release of an application to Production, the DTA size grew too large in BizTalk 2013 R2.

DTA Size

This also caused backups to become too large, and the DTA Purge and Archive job running for too long and not reducing the size of the DTA database fast enough.  The large DTA database size could also be impacting BizTalk performance.

We intend to use the BHM Task “PURGE Everything in the DTA”

One of the pre-requisites to running BHM “All BizTalk SQL Agent jobs are stopped”.  Does this include the Backup jobs?  Yes

The DBA is also concerned that the Log files will blow out in size and wants to set the Recovery Model to Simple, would this approach be correct and supported by Microsoft?

BizTalk Team

  1. Do a partial stop all applications and allow running processes to finish
  2. Turn off host instances and set to manual on the BT Prod server.
  3. Stop IIS
  4. Inform SQL team to proceed with their task.

SQL Team to take back up of the SQL database with the following steps

  1. Run BizTalkMgmtDb.dbo.sp_ForceFullBackup stored procedure
  2. Run the Backup BizTalk Server (BizTalkMgmtDb) job to back up the database
  3. Stop all BizTalk SQL Agent jobs
  4. Set the Recovery Model to Simple
  5. Inform BizTalk team that Backup is complete

BizTalk Team

  1. Run BHM task to clean Orphaned Instances
  2. Run BHM task to PURGE Everything in the DTA
  3. Inform SQL team that purge is complete

SQL Team

  1. Shrink the BizTalkDTADb
  2. Set the Recovery Model to Full
  3. Start the SQL Agent jobs
  4. Inform the BizTalk team that Shrink is complete and SQL Agent jobs are running.

BizTalk Team

  1. Start SSO and Host Instances and set to Automatic Start
  2. Start IIS
  3. Enable Receive locations (Except those with DIS prefix)
  4. Monitor for any errors or issues

Question also posted on Technet

BizTalk SFTP – Open SFTP connection error

I was asked to set up some interfaces connecting a on premise FTP server and to send and receive files from two SFTP servers using BizTalk 2013 R2 (CU6).

The first one used a username & password combination and worked without any issues.  The other that used a username & public key however is throwing errors as below.

I can connect with FileZilla from the BizTalk server using the same username & .ppk file that are configured in BizTalk.

I’ve tried various things including the below.

  • Set Accept Any SSH Server Host Key = True 
  • Change Encryption Cipher from Auto to AES (same error), TripleDES (Cipher error)
  • Setting the Folder Path to / or .
  • Changing the Connection Limit = 1
  • Setting Polling Interval = 5 minutes
  • Making sure that it is running on a 64 bit host
  • Googling to try and find others that have encountered this and found a solution

I’ve posted about this on the thread Initialize error for SFTP adapter in BizTalk 2013 R2 which was very similar and on Open SFTP connection error which looks to be an identical error.  There was one fix FIX: “Open SFTP connection” error when you use the SFTP adapter in BizTalk Server, which was part of CU1, so either the issue has regressed, or it is a different issue that throws the same error.

Any clues as to what the cause might be and how to resolve this apart from?

  • Upgrading to BizTalk 2016
  • Using the bLogical adapter
  • Raising an issue with Microsoft (which will have to do if this cannot be resolved)
Receive Location:

The Messaging Engine failed to add a receive location "{ReceiveLocation}" with URL "sftp://{SERVER}:{PORT}/{FILEMASK}*.xml" to the adapter "SFTP". Reason: "Microsoft.BizTalk.Adapter.SftpInvoker.SftpException: Open SFTP connection error.
   at Microsoft.BizTalk.Adapter.SftpInvoker.SftpInvoker.Open()
   at Microsoft.BizTalk.Adapter.Sftp.SftpConnection.OpenUnderlyingConnection(SftpConnectionProperties connectionProperties)
   at Microsoft.BizTalk.Adapters.CommonHelpers.Connection`3.ConnectionPool`3.GetConnection(T1 connectionProperties, TimeSpan timeout)
   at Microsoft.BizTalk.Adapters.CommonHelpers.Connection`3.GetConnection(T connectionProperties, TimeSpan timeout)
   at Microsoft.BizTalk.Adapter.Sftp.SftpRLConfig.ValidateConfiguration(SftpReceivePropertyBag receivePropertyBag)
   at Microsoft.BizTalk.Adapter.Sftp.SftpRLConfig.CreateBinding(RHConfig rhConfig)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.BtsServiceHostBase.InitializeRuntime()
   at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiveEndpoint.Enable()
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiveEndpoint..ctor(BizTalkEndpointContext endpointContext, IBTTransportProxy transportProxy, ControlledTermination control)


Send Port:

The adapter failed to transmit message going to send port "{SENDPORT}" with URL "sftp://{SERVER}:{PORT}/%SourceFileName%". It will be retransmitted after the retry interval specified for this Send Port. Details:"Microsoft.BizTalk.Adapter.SftpInvoker.SftpException: Open SFTP connection error.

Server stack trace: 
   at Microsoft.BizTalk.Adapter.SftpInvoker.SftpInvoker.Open()
   at Microsoft.BizTalk.Adapter.Sftp.SftpConnection.OpenUnderlyingConnection(SftpConnectionProperties connectionProperties)
   at Microsoft.BizTalk.Adapters.CommonHelpers.Connection`3.ConnectionPool`3.GetConnection(T1 connectionProperties, TimeSpan timeout)
   at Microsoft.BizTalk.Adapters.CommonHelpers.Connection`3.GetConnection(T connectionProperties, TimeSpan timeout)
   at Microsoft.BizTalk.Adapter.Sftp.SftpOutputChannel.Send(Message message, TimeSpan timeOut)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)

Exception rethrown at [0]: 
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)

Exception rethrown at [1]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at System.ServiceModel.Channels.IOutputChannel.EndSend(IAsyncResult result)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.SendCallback(IAsyncResult result)".

 

As we were getting no were fast resolving this, we also tried the nSoftware adapter from a BizTalk 2010 server.  Unfortunately this also didn’t work, but at least gave a meaningful error.

The adapter “nsoftware.SFTP v3” raised an error message. Details “Transmission failed for message “f99728a0-8791-42d7-b27e-c1d53feabd3e”: Error uploading SFTP file: Could not negotiate key exchange algorithm. Remote host supports the following algorithms: “diffie-hellman-group-exchange-sha256″.”.

According to the nSoftware documentation, this is supported (in V4), however the client only has V3 of that adapter (for which I cannot find the documentation so cannot confirm what is has to say about supporting that).  I’ve confirmed it does work with V4 now.

 

Quote

How to fix BizTalk Server 2016 SSO Administration Console with PowerShell — SANDRO PEREIRA BIZTALK BLOG

Have you ever noticed that your SSO Administration Console tool doesn’t open in BizTalk Server 2016? Fortunately for Microsoft BizTalk Server team this tool is not heavily used by the customer, nevertheless, this is an existing and valid tool that needs to be working properly. What is this tool? You can install the Enterprise Single Sign-On…

via How to fix BizTalk Server 2016 SSO Administration Console with PowerShell — SANDRO PEREIRA BIZTALK BLOG

Quote

Cost saving tip for Azure VMs — Trying to be different

Everyone knows two things about saving money on Azure VMs: 1, chose a smaller size and 2, turn it off when you are not using it. It turns out that the second one has an additional demand: you need to not use premium disks. What are premium disks? These are great! Great for performance and…

via Cost saving tip for Azure VMs — Trying to be different

Quote

BizTalk Administration Console: An internal failure occurred for unknown reasons (WinMgmt) fixed by July 30, 2018 Microsoft Security Updates — SANDRO PEREIRA BIZTALK BLOG

Last month I wrote a blog post regarding the “An internal failure occurred for unknown reasons (WinMgmt)” error in the BizTalk Server Administration Console caused by the July 10, 2018 Microsoft Security Updates, you can see the entire blog post here: July 10, 2018 Microsoft Security Updates cause errors on the BizTalk Administration Console: An…

via BizTalk Administration Console: An internal failure occurred for unknown reasons (WinMgmt) fixed by July 30, 2018 Microsoft Security Updates — SANDRO PEREIRA BIZTALK BLOG

Microsoft IIS issue after July patches: The service did not respond to the start or control request in a timely fashion. (2147943453, 8007041d).”

After the July security patches from the 10th, not only did we have BizTalk issues we also hit the error the following error after doing a IIS Reset. “The service did not respond to the start or control request in a timely fashion. (2147943453, 8007041d).”

See this thread IISRESET results in W3SVC stuck in stopping status after July 2018 patches that has some details about it.

According to that thread, it looks like Microsoft already has Mitigation patches for this issue already (released on the 17th).

Windows Server 2008 SP2 KB4345397

Windows Server 2008 R2, KB4345459

Windows Server 2012 KB4345425.

Windows Server 2012 R2 KB4345424

Windows Server 2016 KB4345418