i am developing a web site that will make use of Login

now, im having a hard time what's wrong with its data store.

say we are on ASP.NET Web Site Administration Tool,

and under the security tab..

this error appears

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: The database filename can not contain the following 3 characters: [ (open square brace), ] (close square brace) and ' (single quote)

i don't know that database it says, and my database explorer is empty.

i really appreciate your help thanks!

You should have a connectionstring in your web.config, check it name. If this is the asp.net membership provider then this by default use aspnetdb.mdb in the app_data folder.

A good write up on the membership is at http://aspnet.4guysfromrolla.com/articles/120705-1.aspx

Hope it helps

jeremyh:

You should have a connectionstring in your web.config, check it name. If this is the asp.net membership provider then this by default use aspnetdb.mdb in the app_data folder.

A good write up on the membership is at http://aspnet.4guysfromrolla.com/articles/120705-1.aspx

Hope it helps

i tried it but i got an error message,

" Could not find stored procedure 'dbo.aspnet_CheckSchemaVersion'."

i watch a couple of tutorials about making Login Portals

they have no previous databases and yet the web site administration tool works, especially the security tab, and after the wizard completes, VWD automatically creates a database for the users registered.

 

Can I ask a little more about how you are doing things, So you created a site using vwd then you have tried to run the site how? Are you using IIS or the webserver within vwd?

The error usually means that the website can not find the database, ie wrong info in the connection string or that the membership schema has not been put into the database.

Let me have some more details about what is your doing and I will try to help.

jeremyh:

o run the site how? Are you using IIS or the

im using the localhost.

Ok so you are using the web development server but have you got a database (aspnetdb.mdf) in the app_data folder or have you got another sql server db you are using?

jeremyh:

Ok so you are using the web development server but have you got a database (aspnetdb.mdf) in the app_data folder or have you got another sql server db you are using?

ive got a 2 databases, one is named 'Customers' and the other is ASPNETDB.MDF that i just created because i saw it on the video and hope it will work,

but it is still gives the same error, like i have posted on my other post 

Sorry but you did not say, are these in the app_data folder or with a sql server?

You need to make sure that the database has the membership tables in it, to do that that a read of this http://weblogs.asp.net/scottgu/archive/2005/08/25/423703.aspx

If this database is created by asp.net then you need to make sure that you have premissions to access it. Check that the aspnetdb.mdf is not readonly, check that your user account has access to app_data folder and that the sql login details are correct.

Hope it helps

jeremyh:

Sorry but you did not say, are these in the app_data folder or with a sql server?

oh sorry, they are both in the app_data folder not in sql server

jeremyh:

You need to make sure that the database has the membership tables in it, to do that that a read of this http://weblogs.asp.net/scottgu/archive/2005/08/25/423703.aspx

regarding with this, is it ok if i just write the name of the database? because the wizard was unable to display the list of databases i have in sql,

try to look at this

Named Pipes Provider, error: 40 - Could not open a connection to SQL Server

Is just a basic connectivity error meaning the client could not connect to the target SQL Server.
Try following these basic connectivity troubleshooting guidelines, see:

SQL Server 2005 Connectivity Issue Troubleshoot - Part I
http://blogs.msdn.com/sql_protocols/archive/2005/10/22/483684.aspx

and

SQL Server 2005 Connectivity Issue Troubleshoot - Part II
http://blogs.msdn.com/sql_protocols/archive/2005/10/29/486861.aspx

And also if you are working on Windows XP with SP2,
Then the Windows Firewall is probably blocking your SQL connection:

http://support.microsoft.com/default.aspx?scid=kb;en-us;839269

Oh and Also if this is a SQL Server at your hosting company then many
do not allow remote connections, So you have to use there tools.

Hope it helps

jeremyh:

Named Pipes Provider, error: 40 - Could not open a connection to SQL Server

Is just a basic connectivity error meaning the client could not connect to the target SQL Server.
Try following these basic connectivity troubleshooting guidelines, see:

SQL Server 2005 Connectivity Issue Troubleshoot - Part I
http://blogs.msdn.com/sql_protocols/archive/2005/10/22/483684.aspx

and

SQL Server 2005 Connectivity Issue Troubleshoot - Part II
http://blogs.msdn.com/sql_protocols/archive/2005/10/29/486861.aspx

And also if you are working on Windows XP with SP2,
Then the Windows Firewall is probably blocking your SQL connection:

http://support.microsoft.com/default.aspx?scid=kb;en-us;839269

Oh and Also if this is a SQL Server at your hosting company then many
do not allow remote connections, So you have to use there tools.

Hope it helps

jeremyh can you help me,

i dont get the instruction on how to make remedy for this,

here is the error i got,

Error Message 3:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Shared Memory Provider, error: 40 - Could not open a connection to SQL Server)

Troubleshoot:
1) You might explicitly use "lpc:"prefix which ask for connect through shared memory. Either server instance was not started successfully or shared memory was not enabled on the server.To resolve this, you remove "lpc:"prefix in your connection string as long as Server is listening on other protocols or enable shared memory and restart server.

2) You explicitly use "lpc:"prefix and connect to a local named instance through form [./(local)/localhost/<machinename>]\<InstanceName>, but Sqlbrowser service was not started. To resolve this, you need to enable sqlbrowser.

3) You might connect through "lpc:" which not includes any server name, to fix this, add correct server name in your connection string.

i'll be looking forward to your reply. thanks

Hello,

Follow the steps on this blog post and you should be able to get it working

http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

Oh I have just been told you get this message as well if sql express is not running
more info and steps to check http://blogs.msdn.com/markberr/archive/2006/03/31/566258.aspx 

Good luck