The Membership Manager Control requires additional stored procedures for complete
functionality
The Membership Manager Control was designed with the goal of simply dropping it
onto a web page and having it work. With the exception of limitations imposed by
your
Sql Membership Provider,
most of the control's functionality is immediately available without having to perform
any configuration.
A useful capability which is not available in the underlying SqlMembershipProvider,
is the ability to change a UserName. This is the member's login ID and is used by
the SqlMembership Provider as a lookup key in most of its internal database procedures.
In order to provide you with this functionality, the Membership Manager Control attempts
to create a stored procedure named
qd_aspnet_Membership_ChangeUserName
which changes the username value for a particular member.
Another useful capability which is also not available in the underlying SqlMembershipProvider,
is the ability to show you a password answer if it is being stored in clear text. To provide this functionality, the Membership Manager Control
attempts to create a stored procedure named
qd_aspnet_Membership_GetPasswordAnswer
which, as you might expect, simply retrieves the password answer.
A frequently requested feature has been recently added to allow filtering on users
that are not approved. Since the underlying SqlMembershipProvider has no built-in
mechanism for listing unapproved members, the Membership Manager Control attempts
to create a stored procedure named
qd_aspnet_Membership_FindUnapprovedUsers
in order to list the members who are unapproved.
If you are using SQL Server 2005 Express (in user instance mode), then the Membership
Manager Control will normally have the security privileges to create and execute
the two required stored procedures. If you are connecting to SQL Server using SQL
Server or Windows Authentication, then it is likely that the Membership Manager
Control will not have the rights to automatically create the stored procedures.
Missing Stored Procedures will not cripple the control
If the required stored procedures are not available, then the control will simply
disable your ability to change user names and inform you of the problem when you
attempt to do so.
Manually installing the stored procedures
If the Membership Manager Control was not able to set up the stored procedures for
you, then you may do so manually by running the Sql Script,
membershipManager.sql
in a "New Query" window of Sql Server 2005 (or in Query Analyzer in Sql Server 2000.)
This script, available in the Program Files Folder where you installed the Membership
Manager Control, basically creates the two required stored procedures.
You must
then provide execute rights for the account whose identity is being impersonated
by your web application.
On Windows Server 2003, this is generally the "NETWORK SERVICE" account.
If you require assistance in doing this, please contact our
Support Department
.
Related Topics
Membership Manager Help
Membership Manager Configuration