Ask a Question related to Coldfusion Database Access, Design and Development.
-
ewl2 #1
ODBC Socket ERROR
I have a a sql 6.5 that i connect to using odbc sockets on CF 7. It worked
fine on my dev machine, but when i installed cf 7 on my production box and
created the data source I got the following error:
Connection verification failed for data source: test
java.sql.SQLException: [Macromedia][SequeLink JDBC Driver]TCP/IP error,
connection refused.
The root cause was that: java.sql.SQLException: [Macromedia][SequeLink JDBC
Driver]TCP/IP error, connection refused.
My research on this problem all deals with the mX 7 odbc services not running.
Both services are running....
ANY Ideas??
ewl2 Guest
-
Socket ODBC error
After I submit the ODBC socket, then I got error message saying "Unable to update the ColdFusion MX 7 ODBC Server. Timeout period expired without... -
ODBC socket query error
I have an ODBC socket connection with a database. The DSN says the connection is OK. I created a simple query in the create a recordset window. ... -
MYOB ODBC Socket Error
Problem solved... Once you've got the ODBC v5.whatever driver installed, the DSN setup and tested with the MYOB connection tester, go to... -
Coldfusion ODBC Socket Error and NOVELL
I have an ODBC connection set up on my personal machine which connects to a Novell Directory eDirectory. If I query the database using an invalid... -
MYOB ODBC Socket Error
Woohoo! I've got the same problem also! running CFMX 6.1 and the V5 MYOB ODBC DemonHellSpawn Driver. I have setup and tested the DSN on the... -
Sarge #2
Re: ODBC Socket ERROR
Have you verified the connection using the MS Data Source Administrator? Can
you telnet to port 1433 on the SQL Server box? Is the SQL Server box listening
on port 1433 (or whatever port you have SQL Server bound to)?
Sarge Guest
-
ewl2 #3
Re: ODBC Socket ERROR
Yes, the datasource verifies ok, in the windows odbc admin screen. We actually had cf MX 6 on the machine previously and had no problems connecting using the socket.
ewl2 Guest
-
er1 #4
Re: ODBC Socket ERROR
The ports for the ODBC socket services have been changed in MX 7 from 19997 and
19998 to 19995 and 19996.
However, in my experience, existing ODBC socket datasources and even the
default port for new ODBC socket datasources do NOT get updated when you
upgrade from 6.x to 7.x. You have to do that manually. You can change both of
these in cfusion\lib\neo-query.xml.
Does that help?
[IMHO it would be a great help if MM could include this info in the release
notes and KB tn_18800, etc.]
er1 Guest
-
ewl2 #5
Re: ODBC Socket ERROR
That worked..........
Thank you so much, i was at my wits end trying to figure that out. Since
the releases were so similar, we copied the neo-query.xml so we didn't have to
recreate all our datasources.... oops
Macromedia, please put this in a technote, as it is almost impossible to
diagnose this problem
thanks for your help
ewl2 Guest



Reply With Quote

