We have a FBA based system. It's uses a Novell LDAP directory. We've been running for about a year with over 300 site collections and lots of users (over 20k). Recently the profile import corrupted (it was working for a long time). I rebuilt the SSP. Now, while importing, the profile import status on the 'User Profiles and Properties' page, goes over 20k. Once it's complete, view profiles show zero. The event log has errors related to some custom properties. First there is a set that goes like - Event ID: 5159Provisioning for Shared Services Provider '<propname>' is in progress.Reason: urn:schemas-microsoft-com:sharepoint:portal:<underlyingpropname>Technical Support Details: (null) The next set (one to match the first set) are along the lines of- Event ID: 3501The data type of the '<propname>' in the Active Directory direcotry service cannot be converted to the data type of the user profile property ''urn:schemas-microsoft.com:sharepoint:portal:profile:<underlying propname>'. The property will not be mapped during import The properties do not exist in AD, but do in our LDAP server schema. I have 5 import connections, to the same ldap server. I break up the imports by letters of the alphabet (causes the import to run in 15 minutes instead of hours). Any suggestions would be appreciated. Thanks.GregM

Hi GregM, Sounds like something in the LDAP server is corrupt (ie, some attribute got updated improperly and cannot be mapped right). An example, the property in SharePoint is steup as an Integer, but the LDAP property is a city 'Seattle'. If all else fails, remove the properties until you don't see that error, then start adding them back. You might need to do some cleansing in your LDAP directory. ChrisChris Givens CEO, Architecting Connected Systems Blog Twitter

So, I removed all my custom properties. I still get the same error on 1 property. SharePoint calls it 'Account name' and it's automatically mapped to the 'username attribute' entry in the import connection. That LDAP attribute is defined as a 255 character case-insensitive string in our LDAP server, and define as type 'Person' in SharePoint. On our other 3 farms, we have the same mapping, and it works. Anyone have any ideas? Thanks. GregM

Do you have the same filter setup for the accounts you are pulling down in this 4th farm? Possibly pulling in accounts you shouldn't be? ChrisChris Givens CEO, Architecting Connected Systems Blog Twitter

It's more restrictive. The funny thing is, during the import, the count will go up to 10K+, and there are tons of 'Crawled' LDAP items in the import log. But the only profiles in the system are AD ones. No LDAP ones.

Interesting, maybe try deleting all the connections, adding the LDAP one first, and the AD one second? To be honest, I have never setup two LDAP based connections at the same time. I have always had a primary and then a "joined" secondary, not a "union". ChrisChris Givens CEO, Architecting Connected Systems Blog Twitter

Ok, turns out that the eDirectory LDAP server was failing to return the schema to SharePoint. We pointed to a different server (that did), and the import works.GregM