Last post Dec 27, 2008 05:51 PM by BKirk
Dec 27, 2008 04:41 AM|BKirk|LINK
Why do Microsoft insist on making it so difficult?
Trying to get started with Memberships using the ASP.NET configuration tools and keep getting the following error when i click on the Sercurity tab:
There is a problem with your selected data store. This can be caused by an invalid server name or credentials, or by insufficient permission. It can also be caused by the role manager feature not being enabled. Click the button below to be redirected to
a page where you can choose a new data store.
The following message may help in diagnosing the problem:
Unable to connect to SQL Server database.
Can someone tell me if in fact VSWB 2008 SP1 can Add New Items for SQL Server 2005 Standard Edition?
And yes i have tried going into Options for Database Connections and set it to my specific SQL Server Name. I've tried all combinations?
Please help since i'm getting all OLEDB connections to the SQL Server 2005 instance working fine but cannot add a new database to my website and cannot use the ASP.NET config tool to set up Forms based Authentications. This is very frustrating and all forum
posts are not helping.
Dec 27, 2008 05:32 AM|kinjalin|LINK
Can you put ur Data Source string here. It seems to be somthing missing in there.
Dec 27, 2008 05:51 PM|BKirk|LINK
On my local client machine and within my web.config file i have an OLDDB connection string that works just fine as follows:
Using OLEDB i can easily connect to my SQL Server Standard Edition 2005 instance on my local client machine (named 'BRENDAN-PC', database named 'mydoordev'). It is when i open the ASP.NET Configuration tool and i can see the homepage
screen, but when i click on Security the error occurs as mentioned in my previous post. This of course stops me from configuring my web.config file for Memberships and forms based authentication, etc...
Also, in the Solution Explorer if i right click my App_Data folder and 'Add New Item', then select SQL Server Database i get the following message:
Connections to SQL Server Files (*.mdf) require SQL Server Express 2005 to function properly. Please verify the installation of the component or download from the URL:
There is obviously an issue with Visual Web Developer 2008 SP1 attempting to connect to my SQL Server Standard Edition 2005 which i bought through the Microsoft Partner Pack some time ago. The problem i
have is that this same SQL Server instance is what we run on our production servers, so how am i expected to develop in ASP.NET without these connections working properly?
Any help appreciated...