- 4 minutes to read

Troubleshooting the Nodinite LDAP Web API

Unlock seamless integration and robust user management with the Nodinite LDAP Web API. This troubleshooting FAQ empowers you to quickly resolve common issues, optimize your configuration, and ensure reliable operations.

✅ Rapidly diagnose and fix LDAP Web API errors
✅ Fix HTTP 500.19 and 500.30 errors caused by the .NET 10 Hosting Bundle
✅ Ensure secure, supported Application Pool identity configuration
✅ Resolve attribute conversion and data protection issues
✅ Access expert support and up-to-date resources

If you cannot resolve issues, contact our Support, read more on the Support page.

Nodinite designed, tested, and built the LDAP Web API with extensive trace outputs for transparency and troubleshooting. You can view these outputs using the SysInternals debugview tool. Check the Windows Event Logs for additional error details, and enable Logging for a trace of each call.

HTTP Error 500.19 or 500.30 after installing or updating

Version 3.1.0 and later of the LDAP Web API run on .NET 10. If IIS returns one of these errors after you install or update, the ASP.NET Core Module V2 or the .NET 10 runtime is missing:

Error Meaning
HTTP Error 500.19 - Internal Server Error (error code 0x8007000d) IIS can't read the aspNetCore section in web.config, because the ASP.NET Core Module V2 isn't registered
HTTP Error 500.30 - ASP.NET Core app failed to start or 500.31 - Failed to load ASP.NET Core runtime The module is there, but the .NET 10 runtime isn't installed

Solution

  1. Make sure the IIS Windows features are installed first; the Hosting Bundle registers the module only when IIS is present. See IIS Windows Features.
  2. Install, or run Repair on, the .NET 10 Hosting Bundle (the Hosting Bundle, not the Runtime or SDK).
  3. Restart IIS (iisreset), or reboot the server.

Review the software requirements in the Prerequisites.

The data protection operation was unsuccessful

If you receive the following exception when invoking the APIs:

The data protection operation was unsuccessful error returned by the LDAP Web API
Screenshot: Example of a data protection error in the Nodinite LDAP Web API.

<?xml version="1.0" encoding="utf-8"?>
  <ExceptionResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <Message>The data protection operation was unsuccessful. This may have been caused by not having the user profile loaded for the current thread's user context, which may be the case when the thread is impersonating.</Message>
  </ExceptionResponse>

You likely configured the Application Pool identity to run as ApplicationPoolIdentity, which Nodinite does not support for the LDAP Web API.

Solution

Run the Application Pool for the Nodinite LDAP Web API with a named account that has read/write rights. Review the Prerequisites.

msExchHideFromAddressLists Attribute Handling

Set the msExchHideFromAddressLists property by using either TRUE or FALSE (case sensitive). If you use any other value, you will encounter errors such as: Error in attribute conversion operation, data 0,v4f7c.

Example request:

<ns0:LDAP xmlns:ns0="http://integrationsoftware.se/BizTalk/Adapters/LDAP/Request/1.0">
  <Batches returnResponseMessageOnExceptions="false" guid="e1725dcb-c22d-407f-acef-ab0256368f26">
    <Batch transactionScopeOption="Suppress" transactionTimeOut="30" continueOnError="true" guid="66d47c6b-9ccb-4541-bd35-5c9245f60962">
      <User>
        <With CN="XXXXXXXXX" searchScope="Base" expectedMatchCount="1"/>
        <Operations>
          <Update>
            <Properties>
              <Property name="msExchHideFromAddressLists" value="TRUE"/>
            </Properties>
          </Update>
        </Operations>
      </User>
    </Batch>
  </Batches>
</ns0:LDAP>

Internal Server Error 500

If you see this error:

HTTP Error 500.0 - Internal Server ErrorThe page cannot be displayed because an internal server error has occurred.

A policy may prevent the app from loading the user profile.

Solution

Add the following app-setting for the Azure app service:
WEBSITE_LOAD_USER_PROFILE = 1

A connection to the directory fails or times out

A firewall often blocks one of the LDAP, LDAPS, DNS, Kerberos, or Global Catalog ports. Test each port with the TCP and UDP ports user guide. For LDAPS certificate problems, see SSL-LDAPS for Active Directory.

Uninstalling the Nodinite LDAP Web API

  • Review the Uninstall user guide for step-by-step instructions.

How do I get the latest version?

If you are a registered user with a contract, download the latest package from the Nodinite portal, and follow the Updating user guide.

How do I know when there's a new version available?

Read the Release Notes, and subscribe to updates by using our Support portal to stay informed about the latest releases and improvements.

Next Steps

  • Review Prerequisites to ensure your environment is ready
  • Follow the Updating user guide when a new version is available
  • See Uninstall for removal instructions