May 20, 2018 at 8:49 pm
Moving Databases from SQL 2008 Enterprise on Windows 2008 R2 Enterprise server To SQL 2014 Enterprise Windows 2012 R2 Cluster environment.
I have three SQL instances installed on the SQL 2008 and the same on the SQL 2014
My databases that is on port 1433 works fine.
I have a database on instance 2 using port 2433 and I can not connect from my web application get this error
I am sure it is a string issue but not sure what is wrong with my string.
My string
<%strConnect ="Provider=SQLOLEDB.1;Persist Security Info=True;User ID=wrestler;Password=xxxxxxx;Initial Catalog=WrestlingHistory;Data Source=SERV014-N1-SQLW\wrestling,2433"%>
<%strConnect ="Provider=SQLOLEDB.1;Persist Security Info=True;User ID=wrestler;Password=harley95;Initial Catalog=WrestlingHistory;Data Source=tcp:10.10.10.97\wrestling,2433"%>
On the sql server I have port 2433 open for TCP and UDP
In SQL Server Configuration Manager
All the Protocols are enabled
The TCP/IP for the IP addresses I have port 2433 added
This is the first time using another instance on SQL 2014 I had this working fine on SQL 2008
any ideas?
Thank you
Tom
May 21, 2018 at 1:41 am
check firewal as it might be getting blocked there.
Moreover, you must not share your actual ip and user details over web.
----------
Ashish
May 21, 2018 at 6:20 am
Hi
First that ip address is just made up it is not my actual ip address
I turned off the Windows Firewall and the same results Not sure if it is the firewall.
Still thinking it is the string
May 21, 2018 at 6:28 am
try these steps for troubleshooting:-
1) try telnet host:port from some remote server from where you can ping this db server (having port 2433)
2) if telnet works, then test odbc connection by running "odbcad32.exe" from "window+run" and test connectivity.
These 2 will help you to determine where the problem is.
----------
Ashish
May 21, 2018 at 7:17 am
Stop guessing what the error might be and add some logging. Then you will capture the actual error message. You can also can change the IIS setting to send error messages to the browser. Then when viewing the site from the web server it will display the error message. It is crazy to get a 500 error and just blindly try to solve it without knowing first what you are trying to solve.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
May 21, 2018 at 9:06 am
You can use netstat /a to look for listening ports on the server.
Double check that config manager has the correct ports for the instance.
Check that the cluster is correctly presenting the virtual socket you want (ip/port).
May 21, 2018 at 10:32 am
Ok guys
port 2433 is not listening
unable to telnet to that port
port 1433 is listening and I can telnet to port 1433 no problem
the Windows 2012 R2 servers firewall has port 2433 TCP and UDP open.
Checked SQL Server Configuration Manager for Protocols for my instance TCP/IP is enabled and all the ip addresses have port 2433 specified and TCP Dynamic Ports is BLANK
But then I figured it out on the ip address that is assigned to the instance was set to Enable NO I changed that to Enable YES
Now able to telnet to that address on port 2433 and the Web site is working again.
Thank you all for the help
Mark this as resolved
May 21, 2018 at 12:42 pm
trgrassijr - Monday, May 21, 2018 10:32 AMOk guysport 2433 is not listening
unable to telnet to that port
port 1433 is listening and I can telnet to port 1433 no problemthe Windows 2012 R2 servers firewall has port 2433 TCP and UDP open.
Checked SQL Server Configuration Manager for Protocols for my instance TCP/IP is enabled and all the ip addresses have port 2433 specified and TCP Dynamic Ports is BLANK
But then I figured it out on the ip address that is assigned to the instance was set to Enable NO I changed that to Enable YESNow able to telnet to that address on port 2433 and the Web site is working again.
Thank you all for the help
Mark this as resolved
The formats for connecting to a named instance are:
ServerName\InstanceName
ServerName,port
IP,port
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
May 21, 2018 at 3:50 pm
Glad it's working.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply