Copy link to clipboard
Copied
Hey guys, this time i need some URGENT help, i swapped from windows to linux platform and using CF9, when i create a DSN in windows using SERVER_NAME\INSTANCE_NAME for the Server field, filling user name and password with a Microsoft SQL Server native DSN works perfectly, but when i do this same thing on Linux i get this nasty error:
java.sql.SQLNonTransientConnectionException: [Macromedia][SQLServer JDBC Driver]The requested instance is either invalid or not running.
The root cause was that: java.sql.SQLNonTransientConnectionException: [Macromedia][SQLServer JDBC Driver]The requested instance is either invalid or not running.
So i tryed to create a connection using the "Other" as DSN type and filled out this info:
CF Data Source Name: Test
JDBC URL: jdbc:sqlserver://SERVER_NAME\INSTANCE_NAME:1433;DatabaseName=MyDatabase
Driver Class: com.microsoft.sqlserver.jdbc.SQLServerDriver
Driver Name: SQL Server JDBC
User name: myuser
Password: mypass
i get this error:
Connection verification failed for data source: test
com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host FULLSQL, port 1433 has failed. Error: "Connection refused. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port.".
This was done after downloading sqljdbc_3.0.1301.101_enu.tar.gz from microsoft's web site and placing the sqljdbc4.jar file inside the /opt/coldfusion9/runtime/lib directory.
So basically the first way to create the connection works on windows but not on linux, and the second way does not work in any place even tho it's supposed to be working...
Please send me some help ASAP, need this thing working BADLY!
Copy link to clipboard
Copied
Come on guys.!! ne1? , still need that life saver tip for this issue....
Copy link to clipboard
Copied
Do you need to connect to it via its name? Can you not just connect via IP & port (still using the SQL Server driver, not the "other" driver).
--
Adam
Copy link to clipboard
Copied
Okay, just solved the mistery... i will NEVER connect since every time you install a new SQL Server instance THAT new instance will listen to a different port, in this case the default 1433 was working but for the first instance and i was trying to connect to a second one listening in some other port i can't remember ATM.
Thanx for that help ne way Adam....!