LDAP Server Import set state shows 'Loading' and won't process ahead

TechLead_vikas
Tera Contributor

Hi All,

 

We have setup the LDAP server to import the user and group data from customers AD to ServiceNow.

All the import set and transform map has been created and tested successfully.

 

However, import sets (for both Users and Groups) which are created by the scheduled job which runs on daily basis shows the state as 'Loading' for more than 24 hours and there is no data in that Import set runs / Import Set Rows / Import Log related lists of the same import set.

 

Also, import sets which are created from the LDAP listener are working fine and processing and shows the data in the Import set runs / Import Set Rows / Import Log related lists.

 

viki1_1-1720513034862.png

Can someone please tell me what could be the cause and possible solution for this?

#LDAP Integration

 

Thanks!

Vikas

3 REPLIES 3

Mahathi
Mega Sage
Mega Sage

Hi @TechLead_vikas ,

Are you seeing any error in the transaction logs?  Has it been successful in the past? Did you try loading it without a scheduled job using test load 20 records?

Do check in the import logs table for error/comments column to see if there is any error popping up.

Also check if the LDAP Server is connected and working without any errors.?

If my answer helped in any way, please mark it as Correct & 👍Helpful

Thanks,

Mahathi

TechLead_vikas
Tera Contributor

Hi @Mahathi ,


Thanks for your reply.

I have checked the LDAP connection, there is no error, everything is in green.

 

Yes I have tried using the test load 20 records and it worked successfully.

However, it won't work using the schedule job and it's has not worked in the Past as well. 

Also, there is nothing in import logs as well, please see the screenshot of a import set which is in 'Loading State'.

 

viki1_0-1720520803654.png

Is there anything I should be validating? please let me know.

 

Thanks,

Vikas

Hi @TechLead_vikas ,

Is it working for Load all records as well? 

Just trying to figure where the issue could be.. If all records works then it could be an issue with the datasource  scheduling.

Can you check so it will be easy to drill down to find out the issue.

If my answer helped in any way, please mark it as Correct & 👍Helpful

Thanks,
Mahathi