LDAP import missing values

bennyphipps
Giga Expert

Hi,

 

we've got a LDAP data source setup (using a MID Server) which is only pulling in 6000 out of 7000 records.   I can see AD groups that are virtually identical in name and all other attributes (except the obvious ones like ObjectSID, ObjectGUID samAccountname etc) some which are included and others which are not there's no fields with massive values in either etc.

 

This is not a problem with Transform map as the data is missing from the import itself.   I've tried clearing down the Filter in the OU Definition and that made no difference either.

 

I can view the AD Groups from the instance when I use the LDAP Browse functionality ok though.

 

Can anyone help or suggest anything?   My import table field sizes are all pretty large to account for truncation etc but some of the groups.

 

Cheers,

Ben

29 REPLIES 29

oh... and I asked out AD guys if there was any difference in a selection of these AD groups that were missing or not and they could not see any differences.



In some cases the difference between a missing group and one that is imported may be as subtle as just   number in the SamAccoutnname (and other linked fields like DN, source, Object SID etc)


And on the top one the groups appear when you do a browse ?


It is odd as normally, AD / LDAP is case sensitive, but seems OK when i tried adding objectclass=group instead of objectClass=group, but I would change it incase it is something silly like that.



also, what do you see if you add objectClass as an Attribute for these groups ?


Does it show objectClass group as one of the Attribute names when you click on the group ?


Personally, I see two objectClass values.   top and group





Not got any Business Rules enabled on the import table ?


Not that I know of


It's tricky to tell whether the groups appear by browsing as browsing only shows back 1000 results...   I can see the groups by browsing when I change the filter to be more specific but that again also allows me to import the data...



It has to be something stoopid to do with the filter or teh specificity of it somehow... Grrr