As anyone published this site to a host provider offering the full version of SQL Server? I had this running in development environment using SQL Express. Now I am trying to publish to GoDaddy which uses full SQL Server. I have created my single SQL database,
run the Club tables script, AND added the ASP Schema which I believe to be the equivalent of the ASP membership database that gets auto created. (handles all the membership controls?)
Now I have published, and it doesn't want to connect to the DB. (I am assuming this is the ERROR) that occurs before the page even loads) I have done quite a few edits to the web.config trying to tinker with the connection string, membership parameters, etc.
My ulimate question is this....Should I look within the code as well for possible DB connectivity setup or is it all self-contained in web.config? The original connection string focused on SQL Express's ability to leverage "user instances" which full SQL
Server does not. Anyone know what I am missing?
I wish I could lend an experienced hand here, but I can only report that I am suffering from the exact same problem with the exact same hosting provider. I can run the site fine in my Dev environment (VS2008) I tried running the site after posting using
the databases in the App_Data folder as well as attempting to configure the SQL databases for the site (and running the script) and setting up the ASP Schema.
I can however see the error message, but it hasn't yet provided me with any kind of a clue as to how to fix the problem (this is all very new to me)
When you modified the web.config did you comment out the <customErrors mode="RemoteOnly" defaultRedirect="ErrorPage.htm"/> line and set <compilation debug="true">?
The error message I get is:
Server Error in '/' Application.
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.
Exception Details: System.Data.SqlClient.SqlException: 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)
Source Error:
Line 4: Line 5: void Application_Start(object sender, EventArgs e) { Line 6: if (!Roles.RoleExists("Administrators")) Roles.CreateRole("Administrators"); Line 7: } Line 8:
MichaelDean1...
0 Points
1 Post
Club Site in full MS SQL Server??
Feb 01, 2010 02:20 PM|LINK
As anyone published this site to a host provider offering the full version of SQL Server? I had this running in development environment using SQL Express. Now I am trying to publish to GoDaddy which uses full SQL Server. I have created my single SQL database, run the Club tables script, AND added the ASP Schema which I believe to be the equivalent of the ASP membership database that gets auto created. (handles all the membership controls?)
Now I have published, and it doesn't want to connect to the DB. (I am assuming this is the ERROR) that occurs before the page even loads) I have done quite a few edits to the web.config trying to tinker with the connection string, membership parameters, etc.
My ulimate question is this....Should I look within the code as well for possible DB connectivity setup or is it all self-contained in web.config? The original connection string focused on SQL Express's ability to leverage "user instances" which full SQL Server does not. Anyone know what I am missing?
Club site database SQL Server full
Tagard
Member
4 Points
2 Posts
Re: Club Site in full MS SQL Server??
Feb 26, 2010 05:10 AM|LINK
I wish I could lend an experienced hand here, but I can only report that I am suffering from the exact same problem with the exact same hosting provider. I can run the site fine in my Dev environment (VS2008) I tried running the site after posting using the databases in the App_Data folder as well as attempting to configure the SQL databases for the site (and running the script) and setting up the ASP Schema.
I can however see the error message, but it hasn't yet provided me with any kind of a clue as to how to fix the problem (this is all very new to me)
When you modified the web.config did you comment out the <customErrors mode="RemoteOnly" defaultRedirect="ErrorPage.htm"/> line and set <compilation debug="true">?
The error message I get is:
Server Error in '/' Application.
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.Exception Details: System.Data.SqlClient.SqlException: 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)
Source Error:
Tagard
Member
4 Points
2 Posts
Re: Club Site in full MS SQL Server??
Feb 26, 2010 03:11 PM|LINK
I was able to connect to the GoDaddy SQL server by changing my web.config connection strings as follows...
This was the first time I tried to remove the default LocalSqlServer connection string and use my own, and it worked.