After creating the scripts and installing them on a SQL Server 2005, instance, I was still getting a random error about a mdf file. As it turns out, I had configured my membership provider to go against my SQL Server database, but my role provider was still hitting the local Access db. Here’s how I configured them correctly in my web.config.
<membership userIsOnlineTimeWindow=”20″ defaultProvider=”SqlProvider”>
<providers>
<remove name=”AspNetSqlProvider” />
<remove name=”SqlProvider” />
<add name=”SqlProvider”
connectionStringName=”JJ_DBConnection”
enablePasswordRetrieval=”false”
enablePasswordReset=”true”
requiresQuestionAndAnswer=”true”
passwordFormat=”Clear”
applicationName=”JJ”
type=”System.Web.Security.SqlMembershipProvider” />
</providers>
</membership>
<roleManager enabled=”true” defaultProvider=”SqlRoleManager”>
<providers>
<add name=”SqlRoleManager”
type=”System.Web.Security.SqlRoleProvider”
connectionStringName=”JJ_DBConnection”
applicationName=”JumpingJupiters” />
</providers>
</roleManager>