Error Reference

LDAP import: user record not created after sync

LDAP import: user record not created after sync

Where this appears

This error appears in the System Log under System Diagnostics > Log > Application Log or in the LDAP Import Status page after an LDAP import operation completes. The import shows as successful but expected user records are missing from the sys_user table.

Sourdough
Chrome Extension

Debugging this in a real instance?

Sourdough lets you trace "LDAP import: user record not created after sync" through system logs, script errors, and API health in the ServiceNow tab you are already using.

Add to Chrome

Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.

Overview
Tasks
CMDB
API
Metrics
Monitor
Internals
Instance:sourdoughdev·Version:Yokohama
Instance StateONLINE
System StatusFully Operational
Session Timeout90 minutes
Logged-In Sessions2 (20 active)
Build Nameyokohama-12-18-2024_p1
IP Address10.159.128.43
Instance HealthHealth Score: 90%
🔥 5dSourdough (Chrome Plugin)Dark Mode

Cause

Transform map coalesce field is not matching existing records correctly, causing the system to skip record creation when it should create new users or update existing ones. (high likelihood)

LDAP query filter is too restrictive and excludes users that should be imported, or the query syntax contains errors that silently filter out records. (high likelihood)

Required field mappings are missing or incorrect in the transform map, causing record creation to fail validation without generating obvious error messages. (medium likelihood)

Business rules or ACLs on the sys_user table are preventing record creation during the import process, particularly those that run on insert operations. (medium likelihood)

The LDAP server connection or authentication failed during the sync, but the import process continued and appeared successful while actually retrieving no data. (low likelihood)

Fix

Step 1: Navigate to System Import Sets > Administration > Transform Maps and locate your LDAP import transform map to verify the coalesce field settings match your intended logic for creating vs updating records.

Step 2: Check System Diagnostics > Log > Application Log for any additional error messages during the import timeframe that might indicate validation failures or business rule issues.

Step 3: Go to System Import Sets > Import Set Tables and examine the import set table data to confirm that records were actually retrieved from LDAP and populated in the staging table.

Step 4: Review the LDAP server configuration at System LDAP > LDAP Servers and test the connection, then verify the query filter syntax and scope are correct for your intended user population.

Step 5: In the transform map, verify all required field mappings exist and check that mapped LDAP attributes contain valid data by examining sample records in the import set table.

Step 6: Navigate to System Definition > Business Rules and review any business rules on sys_user table that run on insert operations to ensure they aren't preventing record creation.

Step 7: Use System Import Sets > Run Transform to manually execute the transform on a small subset of records with debug logging enabled to identify specific failure points.

Step 8: If records still aren't created, check User Administration > Users to confirm the users don't already exist with different values in the coalesce field than expected.

Test Your Knowledge

Quick 3-question quiz. See how your ServiceNow skills stack up.

Question 1 of 3Performance

A list view on a table with millions of records is slow. Best fix?

Select an answer to continue