K
Kumar902402
Guest
Hi Guyz,
I have VB.NET applications on production environment. I am trying to point out the production web.config to the dev sql server DB by updating the connection string. However, I receive below error while doing so
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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server.
I have checked below configurations and everything looks perfect
1. SQL Server on dev is allowing remote connections
2. Firewall on dev sql server is off.
3. I am able to ping successfully the IP address of dev from PROD server. No packets was lossed. DNS are all perfect.
4. Connection string username,password, dbname are all correct.
5. If i use the same connection string from local machine, I don't face this error. Only from PROD server i see this error.
Just puzzled what could cause this error ? Any suggestions would be helpful. Thanks.
Continue reading...
I have VB.NET applications on production environment. I am trying to point out the production web.config to the dev sql server DB by updating the connection string. However, I receive below error while doing so
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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server.
I have checked below configurations and everything looks perfect
1. SQL Server on dev is allowing remote connections
2. Firewall on dev sql server is off.
3. I am able to ping successfully the IP address of dev from PROD server. No packets was lossed. DNS are all perfect.
4. Connection string username,password, dbname are all correct.
5. If i use the same connection string from local machine, I don't face this error. Only from PROD server i see this error.
Just puzzled what could cause this error ? Any suggestions would be helpful. Thanks.
Continue reading...