Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
bubberz
Constraint Violating Yak Guru
289 Posts |
 Posted - 2007-07-18 : 09:07:08
|
| I'm trying to start using the login controls for v 2.0, and get the following error: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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. SQLExpress database file auto-creation error: The connection string specifies a local Sql Server Express instance using a database location within the applications App_Data directory. The provider attempted to automatically create the application services database because the provider determined that the database does not exist. The following configuration requirements are necessary to successfully check for existence of the application services database and automatically create the application services database:If the applications App_Data directory does not already exist, the web server account must have read and write access to the applications directory. This is necessary because the web server account will automatically create the App_Data directory if it does not already exist. If the applications App_Data directory already exists, the web server account only requires read and write access to the applications App_Data directory. This is necessary because the web server account will attempt to verify that the Sql Server Express database already exists within the applications App_Data directory. Revoking read access on the App_Data directory from the web server account will prevent the provider from correctly determining if the Sql Server Express database already exists. This will cause an error when the provider attempts to create a duplicate of an already existing database. Write access is required because the web server accounts credentials are used when creating the new database. Sql Server Express must be installed on the machine. The process identity for the web server account must have a local user profile. See the readme document for details on how to create a local user profile for both machine and domain accounts. We have SQL Server 2005 on the machine, but do you have to have Express too?Thanks! |
|
|
SalmonTraining
Starting Member
1 Post |
Posted - 2007-07-18 : 18:26:05
|
| You can run with SQL Server instead of SQL Express but you need to do some extra configuring.You need to install the membership structures (tables, procedures etc) on SQL Server - you use the aspnet_regsql.exe utility to do this.On your PC, you'll probably find it here:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50215\aspnet_regsql.exeJust run it and follow the steps to "Configure SQL Server for Application Services".Then you need to point your database connection against SQL Server (if you're using e.g. VWD Express, by default it's pointed at SQL Express). Have a look at the connectionstring in your web.config - you don't want to see "Data Source=.\SQLEXPRESS", instead on your development environment it will be "Server=localhost", or an explicit server name if you're using one. |
 |
|
|
|
|
|
|
|
login controls...need SQL Express too???