Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Apr 23, 2012 07:58 AM by laudrup
Apr 23, 2012 01:55 AM|LINK
I wanted to create logins for a website (I am very new to this). In Visual Studio 2010, I launched the ASP.Net Web Site Administration Tool and clicked the Security tab, but I am getting the error:
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: Login failed for user ''.
Do you know how I might be able to fix this?
Some further background:
I have SQL Server 2008 R2 Developer edition installed on my computer (I got rid of the SQL Server Express that came with Visual Studio). I created a blank database (myfirstlogindatabase1) that I planned to use for storing administration data. I ran the aspnet_regsql file
and selected the myfirstlogindatabase1 as the database. I assume this bit all worked fine because a bunch of tables and stored procedures had been added to the database when I looked at in SQL Server Management Studio.
In Visual Studio 2010 I altered the connection strings in the web.config file from:
source=.\SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|\aspnetdb.mdf;User Instance=true"
Source=ASSET000610;Initial Catalog=myfirsdatabase1;Integrated Security=True"
Note that there is another connection string for a data table I have got on the web page from another database (myfirstdatabase1), which works fine.
Any help would be gretaly appreciated. Am a bit stuck.
Apr 23, 2012 04:51 AM|LINK
Make sure inrole provider slao you are using the same conenctionstring:
add name="ApplicationServices" connectionString="data source=.\SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|\aspnetdb.mdf;User Instance=true" providerName="System.Data.SqlClient"/>
Apr 23, 2012 07:58 AM|LINK
Awesome, thanks for the advice, just needed to include Integrated Security=SSPI; in the connection string and it worked.