- 3 minutes to read

Updating the Nodinite LDAP Adapter for Microsoft BizTalk Server

Keep your Nodinite LDAP Adapter for Microsoft BizTalk Server up to date with this step-by-step guide. Learn how to safely upgrade, manage binaries, and validate your environment for maximum reliability and performance.

✅ Clear, repeatable update process for multi-node BizTalk environments
✅ PowerShell automation for GAC management and file operations
✅ Minimize downtime and avoid common upgrade pitfalls
✅ Validate updates with the included Test Client and Release Notes

This page describes how to update the Nodinite LDAP Adapter for Microsoft BizTalk Server

graph LR subgraph "Updating Nodinite LDAP Adapter for Microsoft BizTalk Server" rofal[fal:fa-file-archive 1. ZIP package] --> |Unzip| roFolder[fal:fa-folder 1. Install folder] roFolder --> |Restart| roRestart(fal:fa-redo 3. Host instances/MMC) end

Visual overview: Update process for the Nodinite LDAP Adapter—unzip, install, restart host instances.

Step 1: Stop applications with a reference

Note

For a BizTalk Enterprise environment with several processing nodes, repeat these steps on each server before restarting!

Unload the binaries in use:

  1. Stop all BizTalk Host Instance(s) associated with the Nodinite LDAP Adapter for Microsoft BizTalk Server
  2. Close the BizTalk administration console (MMC) to unload the DLLs from the GAC

Repeat sub-step 1 and 2 on all nodes before proceeding to the next step

Step 2: Remove the old binaries

Remove the old binaries from the GAC using an elevated PowerShell command prompt:

[System.Reflection.Assembly]::Load("System.EnterpriseServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a")  
$publish = New-Object System.EnterpriseServices.Internal.Publish  
$publish.GacRemove("C:\Program Files (x86)\IS BizTalk LDAP Adapter 1.0\Test Client Utility\IS.BizTalk.Adapters.LDAP.Mgmt_v1_0.dll")  
$publish.GacRemove("C:\Program Files (x86)\IS BizTalk LDAP Adapter 1.0\Test Client Utility\IS.BizTalk.Adapters.LDAP_v1_0.dll")  
$publish.GacRemove("C:\Program Files (x86)\IS BizTalk LDAP Adapter 1.0\Test Client Utility\Primer.dll")  

You may need to adjust the folder path. The template script uses the default settings from the installation

Step 3: Copy new binaries

Update the binaries in the installation folder:

  1. Read the Release Note to review all changes (breaking changes are rare)
  2. Unzip the ZIP package with the new version to the installation folder, usually: C:\Program Files (x86)\IS BizTalk LDAP Adapter 1.0\Test Client Utility\
  3. Unblock all new files using PowerShell:
Get-ChildItem -Path 'C:\Program Files (x86)\IS BizTalk LDAP Adapter 1.0\' -Recurse | Unblock-File  

Repeat sub-step 1 and 2 on all nodes before proceeding to the next step

Step 4: Register the new binaries

Re-register the binaries from the installation folder:

  1. Use PowerShell to register the new binaries with the GAC:
[System.Reflection.Assembly]::Load("System.EnterpriseServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a")  
$publish = New-Object System.EnterpriseServices.Internal.Publish  
$publish.GacInstall("C:\Program Files (x86)\IS BizTalk LDAP Adapter 1.0\Test Client Utility\IS.BizTalk.Adapters.LDAP.Mgmt_v1_0.dll")  
$publish.GacInstall("C:\Program Files (x86)\IS BizTalk LDAP Adapter 1.0\Test Client Utility\IS.BizTalk.Adapters.LDAP_v1_0.dll")  
$publish.GacInstall("C:\Program Files (x86)\IS BizTalk LDAP Adapter 1.0\Test Client Utility\Primer.dll")  

Repeat sub-step 1 on all nodes before proceeding to the next step

Step 5: Validate the update

Validate the new binaries:

  1. Test using the Windows Forms-based client.

Repeat sub-step 1 on all nodes before proceeding to the next step

Step 6: Restart BizTalk Host Instances

Restart the BizTalk Host Instances using the new binaries:

  1. Start the BizTalk Host instance(s)
  2. Re-open the BizTalk Server Administration console (MMC) to re-read the DLLs from the GAC

Troubleshooting

Find solutions to common update problems in the troubleshooting guide.

Support

Contact our Support for additional guidance if you cannot resolve the update problem.

Note

Additional troubleshooting information may exist in the Windows Event Logs.


Next Step

Developer guide

Prerequisites