Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
LDAP server paging mismatch between the client and server could result on missing records when large queries are performed. A large import set of users from LDAP servers that do not support paging can fail. - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • LDAP server paging mismatch between the client and server could result on missing records when large queries are performed. A large import set of users from LDAP servers that do not support paging can fail.
KB0657310

LDAP server paging mismatch between the client and server could result on missing records when large queries are performed. A large import set of users from LDAP servers that do not support paging can fail.


2218 Views Last updated : Jul 3, 2025 public Copy Permalink
KB Summary by Now Assist

Description

Paging mismatch between the client instance and the LDAP server could result on missing records when large queries are performed. The LDAP server can limit queries on the server-side, but for LDAP Server with versions 3, you can use pagination. Pagination allows you to make repeated smaller queries that overcome this server-side limits and retrieve much larger result sets. A large import set of users from LDAP servers that do not support paging can partially fail.

 

 

Steps to Reproduce

  • Setup an LDAP directory that do not support paging.
  • Create 5000 users with sAMAccountName with 8 digits starting 'ZZ'
  • Configure this LDAP server on ServiceNow
  • Configure the OU to have a filter of (sAMAccountName=ZZ*)
  • Load all records in data source


The result is that only 1000 users are imported instead of the 5000 users available.

Workaround

The solution is to activate your LDAP server support for LDAP v3 pagination (rfc2696).
Alternatively, split the LDAP OU Definition on smaller queries (less than 1000 records per query).

 


Related Problem: PRB1238634

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.