I come back with another problem on another new fresh install : 1 SQL Server, 2 WFE. And I still have the problem 'Membership provider etc'. (Come back because I had the problem here).
Now I understand things a little bit better, I followed this, and everything's fine, except this error.
STS AppPool run with 'sp_farm' and MyApp with 'sp_pool'.
On SQL Side, 'sp_pool' owned schemas full access, and 'sp_farm' membership db_owner, on my Extranet_User_DB. Also, in general security/login in SQL, 'sp_farm' is mapped to be dbo on the database (same for 'sp_pool').
I used FBAConfigMgr to set the web.config, I check them and they seem fine. I double check them, they all have connectionString ok, etc.
Should I still create the IIS 'blank site' ? Or this is not needed anymore ?
(Should I Just edit my precedent post ?) TIA
I have to say that I would like to avoid using the "machine.config". But when I look at the machine.config located in : "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config"
I can see that in I have :
<membership> <providers> <add name="AspNetSqlMembershipProvider"
Should I modify this machine.config to match my SQL_Role and SQL_Membership plus my SQL-SERVER ?
I investigate a little bit more. If I go to IIS -> WebApp website, If I try adding a .NET users, it says that default provider is not a trusted provider... when
Trusted_Connection=true is present in connection strings. I guess the problem is coming from here.
Idea to troubleshoot this error ?
EDIT : I got this in my web.config ... the
is normal ?
<roleManager> <providers> <add connectionStringName="fbaSQL" applicationName="/" name="SQL_Role" type="System.Web.Security.SqlRoleProvider, System.Web,
Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> </providers> </roleManager>
Woh ... I can delete it from CA and STS web.config, and all still working. But If I delete it from WebApp web.config, the site of the app doesn't respond anymore (got a blank page).
Ok ... So
is the carriage return, bad interpreted by XML. So I get rid of it, and now my site respond without this. But Still membership error.