SQL to Xref BizTalk SendPort to Party

If you try to delete an application or a SendPort, you might find that SendPort is used on an EDI Trading-Partner (party). There is no easy xref in BizTalk to show you which party might be tied to that send port. Usually the naming conventions will help, but not always. This SQL query gives you […]

List of all CmdLets (Commands) for the BizTalk Provider for Powershell

You can list the cmdlets yourself with this command: <pre>Get-Command | where { $_.ModuleName -like "BizTalk*" } </pre> But here is a convenient list in text format: CommandType Name ———– —- Cmdlet Add-ApplicationReference Cmdlet Add-ApplicationResource Cmdlet Deploy-Policy Cmdlet Disable-ReceiveLocation Cmdlet Enable-ReceiveLocation Cmdlet Enlist-Orchestration Cmdlet Enlist-SendPort Cmdlet Enlist-SendPortGroup Cmdlet Export-Application Cmdlet Export-Bindings Cmdlet Export-Policy Cmdlet Get-ApplicationResourceSpec […]

Two ways to loop through BizTalk Sendports using Powershell Extensions (ForEach & ForEach-Object)

The sample below shows the use of the “ForEach” and the “ForEach-Object”. I think the first method results in cleaner code. The second method using piping and the $_ to represent the anonymous object. Using Powershell ISE (Integrated Scripting Environment), both methods should give you command completion (i.e. if you type in $SendPort., you will […]

Restart Certain Receive Location with BizTalk Provider for Powershell

We have a custom Rabbit-MQ adapter that has a few issues. When we restart the host-instances, the adapter may get “stuck” unless we restart the associated receive locations. So, I wrote a Powershell to restart all RabbitMQ receive locations that are currently enabled. <pre> cls # # Restart All RabbitMQ Receive Locations that are currently […]

Powershell to build BTDF PortBindingMaster File

One of the pains of the BizTalk Deployment Framework (BTDF) is that frequently, you build a PortBindingMaster file, then you change your port names, or make other changes, and have to rebuild it manually. The manual process is to export the binding file, then carefully go through the file, making the changes to the BTDF […]

Powershell to Export BizTalk Bindings for An Application

I’m starting to write a script to build my BizTalk Deployment Framework Binding (BTDF) files. I’m planning to substite the few things that are unique with the BTDF variables. So the first step is to automate the export of the binding file. $appName = "Echo.BSSR.FrontEnd.LTLShipmentOut" $bindingsDirectory = "c:\Users\NWalters\AppData\Local\BizTalk\Binding Files" $exportFilename = "$bindingsDirectory.\$appName.xml" cd "Biztalk:\Applications" $app […]

Powershell to List Process IDs of BizTalk Host Instances

When you have many BizTalk host instances and you want to do a “Debug Attach” to one specific one (for example to debug a pipeline component), it really helps to know the process ID (else you might have to attach to many host instances). The Powershell code below conveniently lists the process ids along with […]

EDI. promoted properties (such as ISA06) not appearing in Orchestration Expression dropdown

I had an orchestration from a BizTalk 2010 that had the following code: vISA06 = msg_EDI_997(EDI.ISA06); vISA08 = msg_EDI_997(EDI.ISA08); We were updating and refactoring to 2016. When I put that code in my 2016 orchestration, it got an error. I checked, and the EDI. fields were not showing up in the Intellinsense “drop down”. The […]

BizTalk The database associated with the deployment driver does not match database of the during product configuration.

Error When trying to deploy a Business Rule Engine Policy in BizTalk Server 2013, I was getting the error: The database “Server:Instance” associated with the deployment driver does not match database “Server2:Instance2” of the during product configuration. Solution You can run a SQL script like the following (on my machine, there was only one row […]

BizTalk and “Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.”

Error Microsoft.ServiceModel.Channels.Common.ConnectionException: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. —> System.Data.SqlClient.SqlException: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. The user was correct, and that was driving me crazy. I had just built the database from a script, […]