Error profiler.cgi: Invalid Attribute Name - attrib_extensionattribute3_edit

After installing and configuring Profiler, you use profiler.cgi to view a record and click Account Recovery, but you receive this error:

:profiler.cgi: Invalid Attribute Name - attrib_extensionattribute3_edit

“Invalid Attribute Name' error occurs if Profiler attempts to set an attribute that was not detected in your AD Schema during setup.

The Account Recovery and Password Reset functions utilizes extension attributes 1, 2 and 3. These attributes would be present if the schema was extended as it normally is for Exchange 200x (Forest Prep).

====Solutions:

:1. If the attributes exist, re run Config.cgi and SAVE:\ Check ADSI Edit and see if the extension attributes exist. If they do exist, is it possible you configured Profiler and then later ran Forest Prep (So the attributes are there now, but were not there when Profiler was installed). If so, simply go back to Config.cgi Global Catalog page and click SAVE. (This re reads the AD schema, so Profiler can now see the current attribute set). In Profiler.cgi, refresh the page and click Account Recovery again. You should see the q/a are displayed instead of the error.

:2. If the attributes do not exist, add them:\ If this is only AD and you do not want Exchange, you can add the necessary attributes to your schema.\ :extenstionattribute1\ extenstionattribute2\ extenstionattribute3 :These can be added either manually or by simply running Forest Prep). Then go back to Config.cgi Global Catalog page and click SAVE. (This re reads the AD schema, so Profiler can now see the current attribute set). In Profiler.cgi, refresh the page and click Account Recovery again. You should see the q/a are displayed instead of the error.

:3. If the attributes do not exist, use different attributes:\ If you do not have the extension attributes in the schema, and you do not want to add them or run Forest Prep… you may modify the password reset template files to use attributes other than extensionattributes. Technically, only one q/a set is required. For strictly testing purposes, you could try using ‘department’ or ‘title’. Although for a permanent implementation we’ll want to give more thought to storage attribute(s) that would be suitable long term.

=====Details on how to change your templates to use different attributes:

Did you create a [[435|custom Template]] yet

The following template files should be modified with the same customizations as they both utilize the extension attributes for their process:

:pwrecovery.tmpl :forgotpw.tmpl

Ultimately, whatever attribute(s) you use to hold your q/a answers, you will want to update other templates to remove this attribute from being editable anywhere else (i.e. person-edit.tmpl, user-create.tmpl).

As you might have realized, Option 2 is easier than option 3.