Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

logon control works on local server but not on remote server 1

Status
Not open for further replies.

jordanking

Programmer
Sep 8, 2005
351
hello,

I have a logon control that does not use the default databse in the app_data folder, but rather it uses a SQL server database where I have created the same table structures required for the asp.net membership functions. The logon works when using the local test server on my own computer but does not work remotely.

The error given is extensive, but summarized, it states that the logon control is looking for the databse in the add_data folder which does not exist and does not have the permission to create. I have created custom connection strings and member, role, and profile providers in the web.config file.

Can anyone help me understand why the remote version of the site is still looking for the default databse in the app_data folder?

the following is the error that appears after an attempted login
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to 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

.....
I'd rather be surfing
 
It looks like it is only trying to create a default db because it cannot find the one you are specifying in connection string. Make sure the connection string is pointing to the correct DB.
 
thanks jbenson, when going over my connection strings I noticed that i did not set a default provider for the profile so i made the following changes and it now works

changed from:
Code:
<profile>
     ...
</profile>
to:
Code:
<profile defaultProvider="EFFUProfileProvider">
     ...
</profile>

.....
I'd rather be surfing
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top