Question
8.0.1 64-bit SQL Server Connection Problems
We are running an instance of SQL Server 2005 with a new
installation of CF 8.0.1 64-bit on Windows 2008 64-bit VMWare.
We are unable to connect to our SQL Server 2005 database instance via CF admin. After having problems connecting through CF admin, I tried to connect via Windows ODBC Datasources and had the same issue. I was finally able to connect when I turned off “Dynamically determine port” and hard-coded the instance port (SQL instances do not run on port 1433, they are assigned by SQL or the admin). In Windows 2008 32-bit (and Windows 2003 32-bit) I leave “Dynamically determine port” checked on and it works fine. It is only the 64-bit version that does not work with this left on.
So, thinking I figured it all out, I changed the CF datasource TCP port from 1433 to our instance port (1462), but it still didn’t work. The same datasources work in 8.0.1 32-bit (set on port 1433), but not the 64-bit version (either on port 1433 or 1462).
Anyone have ideas on how to connect to SQL via CF admin in this scenario?
We are unable to connect to our SQL Server 2005 database instance via CF admin. After having problems connecting through CF admin, I tried to connect via Windows ODBC Datasources and had the same issue. I was finally able to connect when I turned off “Dynamically determine port” and hard-coded the instance port (SQL instances do not run on port 1433, they are assigned by SQL or the admin). In Windows 2008 32-bit (and Windows 2003 32-bit) I leave “Dynamically determine port” checked on and it works fine. It is only the 64-bit version that does not work with this left on.
So, thinking I figured it all out, I changed the CF datasource TCP port from 1433 to our instance port (1462), but it still didn’t work. The same datasources work in 8.0.1 32-bit (set on port 1433), but not the 64-bit version (either on port 1433 or 1462).
Anyone have ideas on how to connect to SQL via CF admin in this scenario?
