See my earlier post. I listed a few tables that you need to check.
Easiest thing to do is look at the database schema first; this should help you understand the relation between the tables.
Then follow the wire: check your user account in aspnet_Users and aspnet_Membership. Look at the UserID and the ApplicationID it's linked to. Then look in aspnet_UsersInRoles and see to what roles your user account is linked. Then look into aspnet_Roles and see if the roles you are linked to in aspnet_UsersInRoles are linked to the same application as your account is.
Does that make any sense? It's a bit confusing as the ASP.NET infrastructure allows you to store multiple applications in the same system. The web.config (the Membership and RoleManager providers in particular) allows you to assign an applicationName which is the name you see in the aspnet_Applications table.
You could also clear out the entire aspnet_* tables, and recreate the relevant records using th WSAT.
As another alternative, you could temporarily hard code creation of roles and assignment of users in the Start event of the application in Global.asax. E.g. (untested):
Code:
Sub Application_Start(ByVal sender As Object, ByVal e As EventArgs)
' Fires when the application is started
If Not Roles.RoleExists("Administrators") Then
Roles.CreateRole("Administrators")
End If
If Membership.GetUser("YourUserName") Is Nothing Then
Membership.CreateUser("YourUserName", "P4s$w0rd")
End If
If Not Roles.IsUserInRole("YourUserName", "Administrators") Then
Roles.AddUserToRole("YourUserName", "Administrators")
End If
End Sub
You may need to repeat parts of this code for the other roles.
Hope this helps,
Imar
