Take a look at this:
<clear />
<add name="WroxUnited"
connectionString="Data Source=(local)\sql2005;Integrated Security=True;Initial Catalog=WroxUnited"
providerName="System.Data.SqlClient" />
<add name="WroxUnitedMembership"
connectionString="Data Source=(local)\sql2005;Integrated Security=True;Initial Catalog=WroxUnitedMembership"
providerName="System.Data.SqlClient"/>
</connectionStrings>
Notice how the <clear /> element clears out all existing connection strings including the default LocalSqlServer.
Your role manager then needs the LocalSqlServer connection string which it can't find.
There are a few ways to fix it:
1. Don't use <clear />
2. Put in a new LocalSqlServer connection string and point it to a database.
3. Remap LocalSqlServer in the <providers> element to an existing connection string.
I can imagine that it's frustrating if you don't get an answer right away. However, please try to be a little patient. Not everyone is watching these forums 24 x 7.... ;)
Imar
---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of
ASP.NET 2.0 Instant Results and
Beginning Dreamweaver MX / MX 2004