A critical vulnerability was discovered in React Server Components (Next.js). Our Systems Remain Fully Protected. Learn More.
AI OnAI Off
A critical vulnerability was discovered in React Server Components (Next.js). Our Systems Remain Fully Protected. Learn More.
Greetings,
I am having a few issues with using the web.config administration tool, on an EpiServer project that has been setup (Via EpiServer) to use the ASP.NET membership stuff.
The issue is, after launching the WAT tool from VS 2008, when you go to the Security tab, of the WAT tool - it tells you the following:
The Membership provider it set to SqlServerMembershipProvider and tests successfully, the Role provider is SqlServerRoleProvider, and tests successfully.
The following items are present and correct in web.config and connectionstrings.config
1.) Role manager/Providers stuff (All generated by EpiServer)
2.) Role manager enabled
3.) SqlServerMembershipProvider Test succeeds
4.) DB Server (Network server, rather than local SQL)
Now, the SQL Server in question here is a networked SQL server 2005 box, i have managed to get it all to work, but only on a local SQL database, using SQL Express. (By setting up a-fresh copy, with local Express connection string rather than networked 2005)
Can anybody tell me why it refuses to work, using a "proper" installation/instance of SQL Server, that is not local to my machine, nor SQLExpress? The error message is so vague, so i don't know if it's trying to tell me that i've missed a key configuration entry that is required, or whether I have to do something specific to make it work on a SQL 2005 instance, rather than local Express instance.
Any relevant ideas/advice welcomed. Happy to provide more info on request, if i've missed anything out.
Thanks
Matt