Hello,
I know this has been covered a few times previously, but I just cannot get around this issue that keeps popping up in my provisioning. The situation is as follows:
ADAM MA: Already has inetUserOrg class user record with CN of "A"
SQL MA: Finds a newly created record in the database with the same CN of "A"
Provisioning DLL: If there is no connected ADAM MA records for that DN then create a new record, otherwise just pass through the DN as per below code:
if(SQLMA.Connectors.Count == 1 And ADAM.Connectors.Count == 0) //NEW RECORD csentry = ADAM.Connectors.StartNewConnector("user"); csentry.DN = DN csentry("userPrincipalName").StringValue = mventry("cn").StringValue csentry.CommitNewConnector() else //RETURNING RECORD csentry = ADAM.Connectors.ByIndex(0) csentry.DN = DN
The problem I am having at the moment is sometimes this will cause the afore-mentioned error. This is caused because it goes into the creation part of the code when it should be joining and therefore goijng into the second part of the code and just joining and modifying if needed.
I have searched the ADAM MA connector space and the record CN "A" record is there but NOT connected and the join rules are correct as they normally DO match, but not ALL the time. This is also confirmed when I stop provisioning and do full import/syncs on the SQL and ADAM managements.
So I guess I am wondering if anyone else has had this issue because it's driving me a little batty and I don't want to always have to turn provisioning on and off...
Cheers,