ASP.NET Configuration page couldn't read security settings, wha???
I had this problem after re-creating a database that I built, that happened to use the ASP.NET membership tables. For some reason, when using ASP.NET Configuration to manage my roles and security settings, the configuration page had trouble reading the fresh schema I just generated. It turns out, it's because I need the following values in aspnet_schemaversions:
Feature | CompatibleSchemaVersion | IsCurrentVersion
common 1 1
health monitoring 1 1
membership 1 1
personalization 1 1
profile 1 1
role manager 1 1
These values are usually entered into the membership tables by default when you generate them the first time, using .NET's scripts! This is helpful to know.
Subscribe to:
Post Comments (Atom)
Posts
No comments:
Post a Comment