- 4 minutes to read

Updating the Nodinite LDAP Web API

Stay in control of your integration landscape by keeping the Nodinite LDAP Web API up to date. This guide shows you how to perform a secure, reliable, and seamless manual update, so you always benefit from the latest features, improvements, and security enhancements.

✅ Follow a proven, step-by-step update process for minimal downtime
✅ Protect your configuration and data with essential backup guidance
✅ Ensure business continuity with clear instructions for every stage
✅ Access expert support and troubleshooting tips when you need them

The Nodinite LDAP Web API does not include an installer. You update it manually by following the steps below. We continuously develop the LDAP Web API, add new features, and fix bugs. Your paid Software Agreement (SA) covers all new releases.

Plan updates as part of your ALM (Application Lifecycle Management) process to ensure smooth operations.

Before you begin

Inform all clients and consumers before you start the update. The process requires a complete stop, resulting in some downtime. Always schedule updates during a planned maintenance window.

Important

Always back up the installation folder before you replace any files!

Updating from 3.0.x to 3.1.0 or later

Version 3.1.0 and later run on .NET 10, the same runtime as Nodinite v7. Earlier versions run on ASP.NET Core 8.0 or older, so the runtime on the server must change before the new binaries can start.

Hosting What to do before Step 1
IIS Install the latest .NET 10.0 Hosting Bundle, then run iisreset. Skip this if the server already hosts Nodinite v7 and is on the latest .NET 10 patch. See Prerequisites
Azure App Service Change the runtime stack of the App Service to .NET 10 (Settings > Configuration > General settings)

Note

The new Hosting Bundle installs side by side with older ones. Remove older ASP.NET Core Hosting Bundles only when no other application on the server uses them.

Update Process Overview

The update follows three sequential steps to ensure a safe and predictable upgrade:

graph TD A[" Step 1: Stop Application Pool"] --> B[" Step 2: Update Content"] B --> C[" Step 3: Start Application Pool"] style A fill:#FFD525 style B fill:#2678BD style C fill:#93d16d

Diagram: Three-step update process — stop the Application Pool, replace binaries, then restart.

Step 1: Stop Application Pool

Stop the Application Pool for the IIS Application hosting the LDAP Web API.
Use the Internet Information Server (IIS) Manager.

inetmgr.msc

Then, stop the Application Pool:
Stop Application Pool
Example of stopping the Application Pool in IIS Manager.

Step 2: Update Content

Update the binaries and review the Configuration. The default path, as documented in the Installation, is C:\Program Files\Nodinite\LDAP Web API

Installation Folder
Example of the default installation folder for the LDAP Web API.

  • Replace the files, but do not overwrite the appsettings.json and settings.json files if they already exist from a previous installation.

Important

The appsettings.json and settings.json files are part of the ZIP package. Do not overwrite these on existing installations.

Step 3: Start the Application Pool

After you replace the binaries and review the Configuration, restart the Application Pool in use.

Start Application Pool
Example of starting the Application Pool in IIS Manager after the update.


Troubleshooting

If you encounter issues updating the LDAP Web API or have questions about the process, contact our support team.

HTTP 500.19 or 500.30 after the update

The server doesn't have a working .NET 10 runtime for IIS:

  • 500.19: the ASP.NET Core Module V2 isn't registered in IIS. Run the .NET 10 Hosting Bundle installer again and select Repair, then run iisreset. See Verify ASP.NET Core Module.
  • 500.30: the API failed to start, often because the .NET 10 runtime is missing. Install the .NET 10 Hosting Bundle (see Prerequisites) and check the Windows Event Log (Application) for details.

Support

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

Tip

Check the Windows Event Logs for additional troubleshooting information.

Next Steps