|
Well, after creating a new project, I
figured out the issue. The Server needs to be 127.0.0.1\SQLEXPRESS, I was
putting the \SQLEXPRESS in front of the Database (ex. \SQLEXPRESS\pubs), duh! Anyhow, let me know if you need any of my
CF Admin settings to get yours working. -Jeff
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jeff Wells The other thing that comes to mind is any firewall
software you maybe running. With ZoneAlarm, I did have to allow SQL
Server to act as a server. Just another thought.
-Jeff From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jeff Fleitz Hi Jeff, On 12/27/05, Jeff
Wells <
[EMAIL PROTECTED]> wrote: Getting CF to connect – I had to do two steps –
Enable TCP/IP and input the static TCP/IP port number. To enable TCP/IP
(and incidentally Named Pipes if also needed), I got into SQL Server
Configuration Manager (different from the Management Studio) –> then
selected SQL Server 2005 Network Configuration -> Protocols for
SQLEXPRESS. My default install had both Named Pipes and TCP/IP disabled,
once changed I had to restart the SQLServer service. To set the TCP/IP
port number, I right clicked TCP/IP and selected Properties – then
selected the IP Addresses Tab, then at the bottom of that screen there is a TCP
Dynamic Ports field (set to 3482) and a In CF Administrator for the Datasources I tried both ports
and they both work fine. I figured that I didn't initially change any of the DB references in the Hopefully, not too long winded. I believe others
switching to SQL Server 2005 will have to jump through the same hoops with the
TCP/IP settings. Not sure on the
-Jeff Wells From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Jeff Fleitz Just as a follow-up, I was finally able to get CF to
talk to the pubs database in SQL Server 2005 via a ODBC socket
connection. Don't know why the java driver won't work, but that is a
different topic. On
12/22/05, Jeff Wells <
[EMAIL PROTECTED]> wrote: Curious
if anyone has migrated a current plum project (and site) to SQL Server
2005? My current problem is that ColdFusion can connect to the database
just fine but when I go into my already existing I've
Googled this error message and I get a bunch of stuff on TCP/IP ports and Named
Pipes and even stuff on DBNETLIB and worm viruses all under SQL Server 2000 not
2005, none of which makes any sense since my ColdFusion server can connect just
fine. More
details: in my If
anyone has any hints, tips, tricks or .45 caliber bullets it would be greatly
appreciated. (My apologies if this has been covered before on the
reflector, I'm on a new laptop and don't have access to the past issues).
-Jeff
|
- [plum] SQL Server 2005 Jeff Wells
- Re: [plum] SQL Server 2005 Jeff Fleitz
- Re: [plum] SQL Server 2005 Jeff Fleitz
- RE: [plum] SQL Server 2005 Jeff Wells
- Re: [plum] SQL Server 2005 Jeff Fleitz
- Re: [plum] SQL Server 2005 Jeff Wells
- RE: [plum] SQL Server 2005 Jeff Wells
