LDAP Import hasn't imported New Starter

[Ann-MarieHolloway]

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.

 

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

With the details

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.

[Victor]

@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...

[Ann-MarieHolloway]

Thank you @Victor,

I will run this past my managers, to provide you with a response (I'm not sure I can access it from my machine).

Ann-Marie

[Ann-MarieHolloway]

Good Morning @Victor

I can see our instance is already in the DeBug stage 

I can also see the LDAP import started on 19/01/19 at 22:00:03 but did not finish

I'm just in the process of obtaining the import tool logs for you.

Many Thanks

[Ann-MarieHolloway]

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

[Victor]

Ok, happy to hear is sorted