Link to home
Start Free TrialLog in
Avatar of Jerry Shakal
Jerry ShakalFlag for United States of America

asked on

CFMX v 8 to SQL Server 2008 R2

We are connecting from ColdFusion v 8 to SQL Server 2008R2 where tcp/ip has been enabled.  We cannot create the datasource using the Microsoft SQL Server Driver in CF as we receive this error.

Connection verification failed for data source: dbname
java.sql.SQLException: [Macromedia][SQLServer JDBC Driver]No more data available to read.
The root cause was that: java.sql.SQLException: [Macromedia][SQLServer JDBC Driver]No more data available to read.
Avatar of RickEpnet
RickEpnet
Flag of United States of America image

You need to make sure there are no firewall rules on either server preventing the connection we use SQL 2008 R2 not problem with CF8
Avatar of Jerry Shakal

ASKER

We've been able to work around it with the ODBC Socket, however, some of our applications require the SQL Server driver.  Checking firewall rules now.
Firewall is OFF on both servers
Avatar of Jones911
Jones911

Are you sure your putting in the right IP address of the SQL server?
You should not need OBDC.

Are you running 64bit on the SQL 2008 R2?

Do you have 32Bit Clients like you see in the screen shot?
3-21-2011-2-55-07-PM.jpg
@RickEpnet - Yes 64bit on the SQL Server, and 32bit SQL Native Client just as your graphic indicates.  
When you say you enable TCP/IP have you enabled it on both standard and 32bit?
In the SQL Server Configuration Manager -
SQL Native Client 10.0 Configuration (32bit)
 Client Protocols TCP/IP Enabled
and under
SQL Native Client 10.0 Configuration
 Client Protocols TCP/IP Enabled

Are you sure your putting in the right IP address of the SQL server?

Also after enabling TCP/IP have you rebooted?
Here too? You can go back in and disable any you do not want once you get it working.
3-21-2011-3-18-47-PM.jpg
@jones911 - used the name of the sql server, then recreated the datasource using the IP address and got the same results.  The servers have been rebooted serveral times.  We've been live for months, but are running out of options since sql 2005 is desupported next month.
@RickEpnet - on those properties only IP1 and IP2 show Enabled.  I went and marked them all YES, but have to wait to restart the services.  
@RickEpnet - same error even after changing all IPs to Yes / Enable and restarting the services.
Connection verification failed for data source: nexgen1
java.sql.SQLException: [Macromedia][SQLServer JDBC Driver]No more data available to read.
The root cause was that: java.sql.SQLException: [Macromedia][SQLServer JDBC Driver]No more data available to read.

Can you ping the server?  Does the DB username exists?  Try a SA user/pass?
Have you applied all the patches to the CF machine. I am talking about Coldfusion Patches?
@Jones911 - the server can be pinged - the DB is valid, I used our SA user/pass and same error.  as noted in prior comment, we are using odbc socket, but appears some of our application require the sql server driver.  that's where we are failing at connectivity.
Is it an issue with a names instance of the database?
I am kind of at a loss. Not sure if the updates will help.
the issue is with the default instance - not named instance.  no firewall rules, tcp/ip is enabled, SA accounts can login via odbc, but not w/coldfusion using sql server driver.  very odd.
I too am using the default instance.
Avatar of _agx_
Shot in the dark, but check *all* of your CF logs. There may contain more detail about the error.

Also, have you tried using a different driver instead, such as the MS Driver or jTDS?
MS Driver: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=99b21b65-e98f-4a61-b811-19912601fdc9&displaylang=en
JTDS: http://jtds.sourceforge.net/ 
ASKER CERTIFIED SOLUTION
Avatar of Brijesh Chauhan
Brijesh Chauhan
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
You had encryption turned on in the SQL server?
So .... what was the problem?
No just unusual. Is you SQL server exposed to the internet.
I am so glad someone thought to post that for you. I am just sorry I did not think of it.