ActiveDirectoryMembershipProvi­der Schema Mappings Not Found

I am trying to enable password retrieval using the AD Membership
Provider with Windows Server 2003 as my AD machine.  I have followed
the examples out there and have been able to update the AD schema with
the 5 new attributes and add them to the User class.  However, when
trying to run the website I get errors that the following three
attributes are not part of the user class, but they really are.  I have
had this problem on 2 seperate machines.  The strange thing is that it
does not give me the error on the other 2 attributes that I have added
(passwordQuestion and passwordAnswer).

attributeMapFailedPasswordAnswerCount="badPasswordCount"
attributeMapFailedPasswordAnswerTime="badPasswordTime"
attributeMapFailedPasswordAnswerLockoutTime="badPasswordLockout"


I read somewhere that the ActiveDirectoryMembershipProvider hard-codes
the schema, which would make it pretty much useless to anyone not using
the standard schema.  I cannot believe this though because the example
from MSDN on configuring password retrieval instructs you to add
attributes and then reference them in the web.config file, so I don't
really buy this explanation of the problem.


Can anyone help me to shed some light on this issue, it is driving me
mad!


LVL 2
jfkruegerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jfkruegerAuthor Commented:
Well I figured this one out.  It appears that Visual Studio 2005 is caching the Schema.  It looks like that when VS 2005 starts up and you load a project with something in your web.config file that maps attributes to the schema, the schema is loaded into memory.  If you make any changes to the schema, you have to close your project (or possibly shut down VS 2005) and re-start.  You will then be able to have access to the attributes.
0
GranModCommented:
Closed, 250 points refunded.
GranMod
The Experts Exchange
Community Support Moderator of all Ages
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic.NET

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.