asked on
How do I deploy my Visual Studio Web Site to a production and maintain SQL connectivity
I am trying to deploy a Visual Studio 2013 website with a database to a machine running Windows 7 Enterprise, SQL Server without Management Studio, and IIS 6.1. The data connection works fine in the development environment but is breaking as soon as I move the site to the production environment. I don't know if there is something wrong with my connection string or if SQL Server is not installed/configured properly. How do I determine where the problem is and how would I go about fixing it?
The error I get is:
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)
The connection string is:
Data Source=.\SQL;AttachDbFilen
Thanks for the help.
The error I get is:
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)
The connection string is:
Data Source=.\SQL;AttachDbFilen
Thanks for the help.
Microsoft IIS Web ServerMicrosoft SQL Server.NET Programming
Last Comment
Vitor Montalvão
ASKER
Thanks Boyd,
IIS 6.1 and ASP 4.0 are installed and I'm told SQL Server is installed but I can not find the SQL Server Management Studio. I think what I'm trying to find is the connection string for the installed SQL Server. The person who set the server up doesn't seem to know and I'm at a bit of a loss as to next steps.
Thanks,
Doug
IIS 6.1 and ASP 4.0 are installed and I'm told SQL Server is installed but I can not find the SQL Server Management Studio. I think what I'm trying to find is the connection string for the installed SQL Server. The person who set the server up doesn't seem to know and I'm at a bit of a loss as to next steps.
Thanks,
Doug
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
The deployment target will require IIS and SQL Server installed. Web sites that use scriptiung or ASP code will require a web server to execute the server sire scripts/code.
You will need to update the connection string to match the SQL server on the target site
One way to test the SQL Server is to set up an DSN (ODBC Concection) to the server to test the server. I used DSNs in the past to make deployment of my ASP sites and Apps easier. Not sure if that is considered Best Practice with .NET.