Simon said it: > 1) Make sure the RDBMS is running SP2.
I ran into this problem during Beta 2, and Raymond Camden pointed this out. If you don't have SP2, you can download it here: http://www.microsoft.com/sql/downloads/2000/sp2.asp Also, there is a Microsoft SQL Server 2000 Driver for JDBC available from MSDN Online. I don't think it is necessary, but if you are still having problems after installing SP2, give it a try. http://msdn.microsoft.com/downloads/default.asp?URL=/downloads/sample.asp?ur l=/MSDN-FILES/027/001/779/msdncompositedoc.xml -- Scott Van Vliet Sempra Energy 555 W. 5th St., 21st Floor Los Angeles, CA 90013 Tel > 213.244.5205 Email > [EMAIL PROTECTED] "Hello Stupid, and welcome to your crappy computer." - Strong Bad, HomestarRunner.com > -----Original Message----- > From: Alexander Sherwood [mailto:[EMAIL PROTECTED]] > Sent: Monday, July 22, 2002 2:56 PM > To: CF-Talk > Subject: RE: CFMX JDBC Drivers > > > At 05:24 PM 7/22/2002 -0400, you wrote: > > > I have CFMX installed on a Win2K box that can make JDBC > > > connections using the supplied drivers to several > > > different SQL Server 2000 boxes. I cannot, however, make > > > a connection to an instance of SQL Server 2000 Enterprise > > > Edition. > > > > > > A thread on the CF Forums had several posts from users > > > with similar problems. Most just reinstalled their OS > > > and CFMX, which I refuse to do at this point. With this > > > being the only apparent fix, it would seem that the problem > > > lies within CFMX, despite the fact that my server can > > > connect to non-Enterprise instances of SQL Server 2000. I > > > could not find anything that would lead me to believe that > > > SQL 2K Enterprise needs special configuration or prep for > > > JDBC connections. > > > > > > I also tried to get the MSFT JDBC Drivers working (with info > > > from this list) and I could not get it to work either. > > > > > > The exact error message: "The root cause was that: > > > java.sql.SQLException: SQLException occurred in JDBCPool > > > while attempting to connect, please check your username, > > > password, URL, and other connectivity info." All of the > > > connection info is correct. > > > >I haven't run into this problem, myself. There's no > difference between SQL > >Server 2000 Enterprise and other editions, from a connection > perspective. > >Are there any other differences? (Named instances vs default > instances, for > >example.) > > No, just the default on 1433. > > >Can you connect via ODBC to your SQL Server 2000 Enterprise server > >using a username and password? > > Yes, works just fine with the stock System ODBC connection > from the Windows > Control panel. The CF Admin "ODBC Socket" connection fails, > though, when > pointing it to the valid DSN setup through the control panel. > > Any other ideas?! > > Thanks, > > > > >Dave Watts, CTO, Fig Leaf Software > >http://www.figleaf.com/ > >voice: (202) 797-5496 > >fax: (202) 797-5444 > > > ______________________________________________________________________ Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
