Strange AttributeDoesNotExistOnObjectExcep tion error
Hi, I'm trying to use the Password Management Extension feature for an Extensible Connectivity MA and I keep getting an AttributeDoesNotExistOnObjectException error in my password management dll. This is what I did: Import my Extensible MA from an XML file and configure the password extension stuff Provision a user with a password to the newly created MA (connector space contains nothing except the newly created objet) Export the user to the connected DB The user is created on the connected DB but the password is not set. Instead I get the previously mentioned exception. Here is the line of code that triggers the exception: if (csentry["customAttribute"].IsPresent) { // Behaviour A, accesses customAttribute value } else { // Behaviour B, doesn't access customAttribute value } Of course the "customAttribute" is not present for the object being treated but that's the reason why I'm calling the IsPresent method before accessing the value. So what am I doing wrong ? PS: I already checked some posts mentioning this exception being caught when the MA schema has been modified and the metadata for the the attribute in question is not in place but that's not my case. PPS: for testing purposes if I force a value for the attribute customAttribute then everything goes right. I'm using build 4.0.3576.2 Thanks in advance Regards
April 11th, 2011 7:48am

Do you have multiple object types within your connector space? Are you doing something that hits the customAttribute in the Behaviour B part.Need realtime FIM synchronization? check out the new http://www.traxionsolutions.com/imsequencer that supports FIM 2010 and Omada Identity Manager real time synchronization!
Free Windows Admin Tool Kit Click here and download it now
April 11th, 2011 9:25am

Hi Paul, I have multiple object types configured for this MA but at the time the exception is triggered there is only one object in the CS: the object that generates the error. No need to discuss the logic behind behaviourA or behaviourB because the debugging clearly states that the error is triggered by the IsPresent call. Regards
April 14th, 2011 6:03am

But if that objecttype does not include the attribute defined within the schema for the management agent, than the IsPresent call will fail if I am not mistaken but unsure if this exception is throwed.Need realtime FIM synchronization? check out the new http://www.traxionsolutions.com/imsequencer that supports FIM 2010 and Omada Identity Manager real time synchronization!
Free Windows Admin Tool Kit Click here and download it now
April 14th, 2011 6:22am

I do not think the IsPresent method mentioned above can reference an attribute to check if the attribute is present or not. The IsPresent check is to check if the attribute has value or not Hope that help Issam Andoni http://www.zevainc.com/andoni Best Regards, Issam Andoni http://zevainc.com/andoni
April 14th, 2011 11:08am

Hi Paul, I have multiple object types configured for this MA but at the time the exception is triggered there is only one object in the CS: the object that generates the error. No need to discuss the logic behind behaviourA or behaviourB because the debugging clearly states that the error is triggered by the IsPresent call. Regards So does this one object in the CS have "customAttribute" defined in its schema?My Book - Active Directory, 4th Edition My Blog - www.briandesmond.com
Free Windows Admin Tool Kit Click here and download it now
April 15th, 2011 12:10am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics