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.
Troubleshooting an import that does not complete or is missing data - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Troubleshooting an import that does not complete or is missing data
KB0538437

Troubleshooting an import that does not complete or is missing data


5266 Views Last updated : Feb 8, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

This article guides you through the process of troubleshooting an import that does not complete or is missing data. It provides steps to help you eliminate common causes of your problem by verifying that the configuration of your networking is correct.
 

Symptoms

Symptoms may include the following:
  • No rows are returned
  • Connectivity issues (log message)
  • Import takes a really long time
  • Import does not complete
  • Import stopped in the middle
  • Import says complete, but not all data is present
  • User cannot log in through LDAP
  • Scheduled import does not run at the defined time
  • Data discrepancy after report
  • Data is truncated
  • Import fails after upgrade

Resolution

Determine whether any of the troubleshooting steps below are true for your environment. Each step provides a link to an article that can help you eliminate possible causes and take corrective action as necessary. 

  1. Determine if the import set picked up all records from the ECC queue. For more information, see KB0538460: Troubleshooting Import - Missing data when importing JDBC source via MID server.
  2. Determine if the column length is too short for the import set. KB0538123: Troubleshooting Import: Missing data when column length is too short for import.
  3. Determine if there is an LDAP configuration issue impacting the import. KB0538124: Troubleshooting Import: Missing data as a result of LDAP configuration issue.
  4. Determine if LDAP attribute data is too large. KB0538128: Troubleshooting Import: Missing data as a result of LDAP large attribute data.
  5. Determine if there is a date format issue causing the data to be truncated. KB0538141: Troubleshooting Import: Missing data as a result of a wrong date format.

 

Note: If your problem still exists after trying the steps in this article: Submit a Case to Technical Support and note this Knowledge Base article ID (KB0538437) in the problem description. For more information, see How to submit a case.

 


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.