---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Troubleshooting LDAP integration via MID Server

# Troubleshooting LDAP integration via MID Server {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

You may encounter issues in the following areas while integrating LDAP via MID
Server.

You can troubleshoot these issues by viewing the outputs found in the External Communication
Channel (ECC) Queue (DiscoveryOutput and ArtifactsECC Queue).

## Test Connection Issues

When defining OUs within the server, there is a Test connection related list that is used to verify the LDAP connection. When you click this link, the ECC Queue should show a single output message with a topic name of LDAPConnectionTesterProbe. After the test has completed on the MID Server, the ECC Queue should show an input message with the same topic name. If the Name column for the input message shows true, the test was successful. Drill down into the record to view the payload and ensure it does not contain error messages.Abbildung : 1. Test Connection

## Browse Issues

When defining OUs within the server, there is a Browse related list
that is used to view the LDAP directory records that the OU definition returns. When you click
this link, the ECC Queue should show a single output message with a topic name of
LDAPBrowseProbe. After data has been returned from the MID Server, the
ECC Queue should show an input message with the same topic name. If the
Name column for the input message shows true, the
test was successful. Drill down into the record to view the payload and ensure it does not
contain error messages.

## Load Import Issues

When uploading data (for example, using the Test Load 20 Records feature), the ECC Queue
should show a single output message with a topic name of LDAPProbe.

After data has been returned from the MID Server, the ECC Queue should show another input
message called LDAPProbeCompleted. The Name column
for this input message shows the total number of records returned.

An additional input messages, also named LDAPProbe, is displayed. The
Name column for this input message displays the highest record number in
the batch. If the total number of records returned is 258 and the batch size is 200 (the
default), two LDAPProbe (200, 258) incoming messages will be received, and one
LDAPProbeCompleted (258) incoming message will be received.  
Drill down into the record to view the payload and ensure it does not contain error messages.Abbildung : 2. Import Load  
Also keep an eye out for an output message called LDAPProbeError.Abbildung : 3. Error message

Click the link in the Name column to view the details of the error.

## LDAP paging

LDAP paging does not work if the paging size on the LDAP server is less than 1000. Set the MID
Server property glide.ldap.max_results to a value less than or equal to the
LDAP server paging size.

## LDAP fails to import binary data

To import binary data via LDAP, such as a user photo, you must include the binary attribute in
the MID Server property glide.ldap.binary_attributes. For the user photo
example, the attribute may be <kbd class="ph userinput">jpegphoto</kbd>.