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.
User records may not be imported via an LDAP import throwing the error message "Row in data source exceeds row size limit" - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • User records may not be imported via an LDAP import throwing the error message "Row in data source exceeds row size limit"
KB0745546

User records may not be imported via an LDAP import throwing the error message "Row in data source exceeds row size limit"


2203 Views Last updated : Jul 24, 2025 public Copy Permalink
KB Summary by Now Assist

Issue

Symptoms

As part of a scheduled LDAP import, it may be observed that few users are not imported even though it's confirmed that these users actually exist in the OU by doing a Browse from the LDAP OU Definition. Upon checking the Import log for the data source in question, error(s) may be seen like below. 

Error during insert of ldap_import (74,335): Row in data source exceeds row size limit. Please consider excluding some fields from this import set as there are 216 fields present causing this row to be too large
 
Steps to check the Import Log errors:
Consider an example where the data source name is "LDAP User Import". 
  1. Go to "Import Log" ("System Import Sets" > "Advanced" > "Import Log") from the filter navigator.
  2. Apply the filter:
    1. Source="Loader (LDAP User Import)"
    2. Level=2

Level=2 is for checking Errors. 

Release

Applicable to all releases.

Cause

As the error log suggests, the data in the row that is being loaded exceeds the maximum row size that is allowed. Due to this, the row is not loaded in the import staging table and that's the reason you might see that this user is not getting imported. 

Resolution

To fix this issue, you need to specify the list of AD attributes that you need to import. The below documentation provides the steps to specify these attributes. 

Specify LDAP Attributes

This will make sure only the required attributes are imported and hence the row size will be much smaller than the max row size limit. 


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.