Recently at my work we’ve started using SSO Affiliate Applications to store credentials for Receive Locations and Send Ports to avoid either having the credentials in the Bindings (which is insecure) or having to re-enter the credentials after each release (which causes releases to take too long). I won’t go into details how we do that in this post, however as part of documenting this ability I went through all the adapters to see which could use SSO Affiliate Applications and which couldn’t.
We are using BizTalk Health Monitor 3.0 in a clients environments and we get the warning message
Caption: ‘maxconnection’ property
Value: Is not present in some BizTalk process config files – You can configure the number of concurrent connections that the SOAP adapter opens for a particular destination server by adding “maxconnection” entry
However I have checked both the BTSNTSvc.exe.config and the BTSNTSvc64.exe.config and the both do have the maxconnection property.
A new critical warning has appeared in the BizTalk Health Monitor for all of our BizTalk 2013 R2 servers after the latest repository update from Microsoft as shown in the screenshot below. How did this occur? We built our BizTalk servers using .Net 4.5. This is the supported version of .Net for BizTalk servers. On […]
I encountered a situation in BizTalk 2010 where when using the WCF-Custom send port with a sapBinding that was subscribing to a WCF-CustomIsolated with wsHttpBinding was throwing back a Microsoft BizTalk Server Negative Acknowledgement SOAP messages as below. These occurred after about 15 minutes of the request.
I had an issue recently at a clients site where after a deployment of an application to their test environment where everything seemed to go fine that when smoke testing it it was complaining that the BRE Policy it needed was not deployed, as the policy was a resource in the MSI that was deployed and this seemed very odd.