This project is read-only.

20 lashes message after switch to sql membership and roles

Topics: ASP.NET 2.0
Feb 19, 2010 at 3:45 PM



I am doing a clean install og v 1.6, using sql server 2008, and have got to the point where the blog is on sql server and I can comment on the default blog.  Membership and roles are still in xml.

So far so good!

I then changed the default membership and role provider settings in web.config to the sql option and tried to login.
Then I got this uninformative message:

Ooops! An unexpected error has occurred.

This one's down to me! Please accept my apologies for this - I'll see to it that the developer responsible for this happening is given 20 lashes (but only after he or she has fixed this problem).

I need to have the membership and roles in the database to integrate with other parts of a webisite
What should I do to resolve this!  Please help!







Feb 19, 2010 at 4:24 PM

Answered my own problem but not sure what I missed...
After watching the install video I  noticed that he started with the sqlserverwebconfig, so I deleted my modified default web.config and used the sql one instead,
the only change being the connection string.

Life is too short to check line by line what is different so I am happily moving forward!

Moral: don't be a mug - watch the video first.