Jump to content

Recommended Posts

Posted

Good Afternoon,

I have had a quick look at other topics regarding LDAP import failures, but have not been able to find the same issue.

We appear to have an anomaly with our LDAP import in that a new member of staff (REDWA) who joined the office on 24/01/19 is not in the list of basic users.

image.png.a1e912ac69897e05383be0019ed0496e.pngimage.png.0ce45197bbc1bb326d2aac9d81e0b5bf.png

 

It looks as though an error occurred with the LDAP import on 18/01/19, which is the day the AD Account was created

image.png.f43d8578e8d491f583d6cf7f2b563f71.png

With the details

image.png.4734695b12d1c2b1ffaf43a4edec9556.png

Other New Starters have been successfully imported during the same period, therefore could you provide some advice on why Richard Edwards may not have imported successfully?

Many Thanks and have a great weekend.

Posted

@Ann-MarieJones we would need to review the import tool logs which are located on the machine that ran the import. The tool needs to be run while having the log level set to "Debug" in order to see why this happened.

You can PM me the logs once you have them...

image.png

Posted

Good Afternoon @Victor,

This topic can now be closed, it appears the fault was an issue with our firewall which caused the import to fail.  The rules have now been updated and the import restarted successfully.

Thank you for your assistance with this.

Ann-Marie

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...