Re: [plum] SQL Server 2005

[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 Sent: Wednesday, December 28, 2005 9:15 AM To: plum@mail.productivityenhancement.com Subject: SPAM-LOW: Re: [plum] SQL Server 2005   Hi Jeff, Yeah, I tried all that. I found a blog post by Matt Wooward which goes into this.  http://www.mattwoodward.com/blog/index.cfm?catID=2 Seems fairly straight forward, don't know why mine won't work.  I will give it another shot shortly... 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 TCP Port field which was blank.  I set the TCP Port field to the standard 1433.    In CF Administrator for the Datasources I tried both ports and they both work fine.  I figured that Plum might be using the standard 1433 so that is currently what I have set in CF Admin.  I originally used the sa account and password to verify but then added a separate development user and password for my SQLEXPRESS connection in order to get my development username/passwd to work for the actual development database.  (In other words, my development username/password that moved from SQL Server 2000 to the upgraded 2005 did not originally work until I added that same username/password as Login (under Security, then Logins) to the higher level SQLEXPRESS connection).   I didn't initially change any of the DB references in the Plum project but did verify CF DSN, username and password under the Enviroment settings, ColdFusion Data Source.  I also verified server, database and authentication on the Database settings.  These are the same as they were on the previous SQL Server 2000 and I can connect using that same username and password with the Management Studio.  Since then I've tried using the sa account in Plum, tried changing the Database name to SQLEXPRESS and SQLEXPRESS\<db name> with no luck.   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 Plum settings but will try with a new Project and let you know.                           -Jeff Wells   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jeff Fleitz Sent: Saturday, December 24, 2005 7:01 AM To: plum@mail.productivityenhancement.com Subject: Re: [plum] SQL Server 2005   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. I was able to create a sample Plum project against the MS SQL 2005 database, add a table and then re-synch the database no problem. You did change the db reference in the Plum project file, right? Jeff 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 Plum project and attempt to sync the DB, no luck.  The exact error is: [DBNETLIB][ConnectionOpen (InvalidInstance()).] Invalid connection.   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 Plum project I have verified that Environment, ColdFusion Data Source AND Database properties are using the same mapping, username, password as CF (and it worked fine under SQL Server 2000).  Again, my exist site works fine and CF Admin verifies the data source.   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   -- v/r, Jeff Fleitz -- v/r, Jeff Fleitz