JTDS driver

I want to connect Netweaver DataBase Server (sqlserver 2000 in my case)using jTDS driver. can anybody help me in creating a datasource in visual administrator for sql server using jTDS driver. I tried to create a datasource using jTDS in visual admin for sql server, I got the following error:
java.rmi.RemoteException: Error occurred while starting application in whole cluster and wait.; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide execption: server ID 3584050:Cannot create DataSource "testdb".
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:679)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:562)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:261)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:317)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:400)
     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:157)
     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:291)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide execption: server ID 3584050:Cannot create DataSource "testdb".
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.sleepClientThread(ParallelAdapter.java:232)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:113)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:214)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4601)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:677)
Thanks in advance,
Saikrishna.

Here's the problem I'm having. Every time I try to use DriverManager.getConnection, I get the message "No suitable driver". This is some basic code I wrote just to check the driver...
Class.forName("com.internetcds.jdbc.tds.Driver");
String url = "jdbc:freetds:sqlserver://scartin:1433";
Connection conn = DriverManager.getConnection(url,"admin","admin"); I have the .jar file in my classpath, and i'm pretty sure the URL is right, but like i said previously, I can't find any documentation on it at all.
Thanks
Simon

Similar Messages

NoSuitableDriver exception running against a jtds driver.

I developed my BC using SQL Flavour and now I try to run against SqlServer using Jtds Driver.
I created my connection and tested it : it works fine.
I create a configuration using that connection but when I try to run the tester against the DB I get a NoSuitableDriver error. (No suitable driver found for jdbc:jtds:sqlserver://faac/MSSQLSERVER;domain=faac;)
Shoud register the driver somewhere in my classes ?
What I Missed ?
Tks
Tullio

I'm guessing that the embedded WLS server can't find the JDBC library you are using - you can try adding it to the lib directory of the embedded WLS
Somewhere like: C:\Users\youruser\AppData\Roaming\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\lib
or directly to the classpath in the startup script:
C:\Users\sshmeltz\AppData\Roaming\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\bin
or try and mark the library with the JDBC jar to be deployed by default in JDeveloper.

Anybody use jtds driver with creator?

Hello,
I have a creator app that talks to our SQLServer via the jtds driver.
I cannot update any records, I get a "result set is read only" message.
I tried changing the concurrency to CONCUR_UPDATABLE and TYPE_SCROLL_SENSITIVE.
Is there a better Driver to use?
Thanks
Frank

I'm not completely sure I understand what you are saying, especially the part with the updateable and read-only tables (ResultSets are updateable/read-only, not tables). Could you provide an example (Java code or at least the SQL) illustrating your point?
The problem with "this driver" is that in its last public release (1.0.2) it did not implement client side cursors (in fact it did, but only for Sybase). This support has now been extended to SQL Server in cases when the server isn't able to create a server side cursor, so jTDS will cache the whole result on the client and create a client side one. This behavior will be available in the next release (or you can get it from the CVS tree before that).
The problem with transparently creating client side cursors is that this introduces a huge (memory and performance) overhead of which the user is unaware. This may lead to OutOfMemoryErrors simply because the table didn't have a primary key or the SELECT didn't include it.
And now that we're here, let me point out that the DataDirect driver is not the most efficient, by far. There's even a test in their performance test suite (which they use only to point out that their driver is and will be the only one that doesn't fail that particular test), which creates a forward only ResultSet and then calls last() and beforeFirst() on it. This test only works because they cache the entire ResultSet, which may seem like a good thing, but it's totally unnecessary and if you compare the time it takes for that test to run with the time to do a simple next() through the exact same ResultSet it's orders of magnitude larger.
And one final thing: the JDBC spec rightfully states that a JDBC driver implementation does not have to implement features that the underlying DBMS does not support. Creating a scrollable and/or updateable ResultSet from God knows what falls under this category in my oppinion. The SQL Server spec clearly states what conditions must be met by a SELECT query for a server side cursor to be created on it. You can't reasonably expect not to meet those conditions and still get what you want.
Alin,
The jTDS Project.

Jtds driver creating deadlocks

hi
I have a strange problem i am using jtds driver and have SPs in database i am using SQL server.
i.e.
storeprocedureOne[ select the rows from database]
storeprocedureTne[ delete the rows from database]
both SPs are called using different connection object and different statement object i mean to say both are called by different function but sometimes they are creating deadlocks and i don't understand why.
if anyone have an idea plz let me know
thanks in advance

Here's the problem I'm having. Every time I try to use DriverManager.getConnection, I get the message "No suitable driver". This is some basic code I wrote just to check the driver...
Class.forName("com.internetcds.jdbc.tds.Driver");
String url = "jdbc:freetds:sqlserver://scartin:1433";
Connection conn = DriverManager.getConnection(url,"admin","admin"); I have the .jar file in my classpath, and i'm pretty sure the URL is right, but like i said previously, I can't find any documentation on it at all.
Thanks
Simon

Jtds driver and NT

Hi,
I have been doing some testing of the jtds driver on XP and NT and it seems that the driver runs great on XP but is very slow on an NT 4.0 machine.
Does anybody know of any know problems with this driver and OS?
Is there a better driver I could try out for windows NT 4.0?
Regards.
Alan

I'd guess some would say there is no "better" driver for most definitions of the word...
Perhaps not better but different: http://www.microsoft.com/sql/downloads/2005/jdbc.mspx
Or googling should find several commercial drivers, some come with no-cost trial versions. E.g. http://www.datadirect.com/downloads/registration/connect_jdbc/index.ssp
My first guess is that it isn't a driver issue. I'd start by checking network configuration, seeing how much packet loss "ping" reports, how fast "ftp" can move data from db server to client, ... And checking if the NT machine is low on memory and simply swapping itself to death.
How slow is "very slow"? A simple select takes 10ms, 1sec, 1min, 1h, ...? Compared to what on the faster machine?

SQL Exception while connecting to Jtds driver

hi...can somebody help me with my error
iam using "net.sourceforge.jtds.jdbc.Driver" with SQL Server 2000 on XP with tomcat version 4.0
it gives me the following exception
java.sql.SQLException: "Network error IOException: Connection refused: connect"
can somebody help me urgent

ya i tried telnet localhost 1433..still
Connecting To localhost...Could not open connection to the host, on port 1433: Connect failed
and when i use netstat -an the foll appears
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:25 0.0.0.0:0 LISTENING
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1027 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5101 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1033 0.0.0.0:0 LISTENING
TCP 192.168.1.2:139 0.0.0.0:0 LISTENING
TCP 192.168.1.2:1138 216.155.193.140:5050 ESTABLISHED
TCP 192.168.1.2:1151 68.142.233.167:443 ESTABLISHED
TCP 192.168.1.2:1422 61.2.36.53:5101 ESTABLISHED
TCP 192.168.1.2:1593 59.92.38.133:5101 ESTABLISHED
TCP 192.168.1.2:1874 216.109.118.146:5001 ESTABLISHED
TCP 192.168.1.2:2054 64.94.235.124:80 ESTABLISHED

Websphere 5.1 Jtds jdbc driver issue

Can some one suggest the possible solution to this issue.
I am trying to use Jtds 1.2 jdbc driver to connect to Sqlserver 2000 from the websphere 5.1 app server ( actually test server environment from WSAD 5.1.2) and I am getting the SQLException as follows "The requested size is greater than the maximum number of rows" . We have the same Jtds driver running fine on JBoss app server for the same application. So I am guessing it must be some configuration that I am missing in websphere that I could nt able to figure out. Appreciate if some one can direct me.
The run time error....
[7/3/06 11:34:47:297 CDT] 7c2fe6bb WebGroup I SRVE0181I: [Form Action Servlet] [ARJ] [Servlet.LOG]: java.sql.SQLException: java.sql.SQLException: The requested fetch size is greater than the maximum number of rows.
     at net.sourceforge.jtds.jdbc.JtdsStatement.setFetchSize(JtdsStatement.java:956)
     at net.sourceforge.jtds.jdbcx.proxy.StatementProxy.setFetchSize(StatementProxy.java:393)
     at com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.enforceStatementProperties(WSJdbcStatement.java:290)
     at com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.executeQuery(WSJdbcStatement.java:443)
     at com.actek.j2ee.common.sessionbean.QuerySessionBean.processQueryParm(QuerySessionBean.java:140)
and the concised SQL query, app error are as follows...
SELECT TOP 101 P.CreditTrnNo, P.CreditType, P.CustomerNo, P.Reviewed, P.NextReviewDate, P.DateComp .......... FROM CreditTrn P LEFT OUTER JOIN Customer Customer_CreditTrn ON P.CustomerNo = Customer_CreditTrn.CustomerNo LEFT OUTER JOIN Dealer Dealer_CreditTrn ON P.DealerNo = Dealer_CreditTrn.DealerNo LEFT OUTER JOIN UsrSet UsrSet_CreditTrn ON P.ChkUserNo = UsrSet_CreditTrn.UserNo WHERE Customer_CreditTrn.CustomerId = '013108' ORDER BY P.SalePend DESC, P.CompReq DESC, P.TrnType, P.FstDate, P.FstTime
java.sql.SQLException: The requested fetch size is greater than the maximum number of rows.
     at net.sourceforge.jtds.jdbc.JtdsStatement.setFetchSize(JtdsStatement.java:956)
     at net.sourceforge.jtds.jdbcx.proxy.StatementProxy.setFetchSize(StatementProxy.java:393)
     at com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.enforceStatementProperties(WSJdbcStatement.java:290)
     at com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.executeQuery(WSJdbcStatement.java:443)

It passes the J2EE 1.3 certification ...So it is JDBC 2.0 compliant.
How does it rate with JDBC 3.0? Like mostly
complete? Or all complete but just not certified
(presuming such a certification exists.)It's both JDBC 2.0 and 3.0 compliant. The problem with the J2EE 1.4 compliance test suite is that it's not publicly available (1.3 is) so we simply can't test against it. We are trying to get jTDS certified, but it costs $2000 and we don't have that kind of money (not unless we pay from our pockets). We intend to do it, from donations and commercial support, but we're currently quite far from the $2k target. Even without an official certification jTDS is the driver of choice for a number of applications that need JDBC 3.0 features (e.g. Hibernate).
The only missing JDBC 3.0 features are connection pooling and row sets. The reason we did not implement these features is that there are good, free third party implementations out there, which are probably better implemented and tested than anything we could come up with (namely DBCP and c3p0 for connection pooling and the Sun reference implementation for row sets). Regarding connection pooling, jTDS does implement the PooledConnection interface, it just doesn't implement the pooling DataSource.
And it does windows auth as well as database auth
right (not a new feature but I want to make sure I
remember?)Yes, it does both SQL Server and Windows authentication. Windows authentication can be done using the credentials of the currently logged user (i.e. without the need to specify a user name and password) or by providing a Windows user name and password (this is useful when logging in from a non-Windows machine or a machine outside of the domain to an SQL Server that is only configured to accept Windows authentication). As far as I know the second Windows authentication mode is only supported by jTDS.
Alin.

How to install jTDS jdbc driver

I've heard so much about this jTDS driver, and had it with the current jdbc driver i'm using. I'm using slserver 7. i would like to install the jtds driver. I just downloaded the .jar file. how do i install the driver. which directory do i put it in? pls help asap. thanks a million.

"Install" it?
The directory you put it in depends greatly on the application that's using it.
If it's a desktop app, put in in the CLASSPATH for the app.
If it's a Web app, put it in the WEB-INF/lib directory for your app.
It's not a cut & dried answer. I don't think one JAR file will necessarily serve all apps. Expect to have duplicates as needed. I do.
%

'other driver and xa connection properties

A connection pool is configured through the admin server with a third party driver (specify other for database type). The driver is only on the classpath

This submitted without me finishing...
We have configured a connection pool with 'other' type and the jtds driver for sql server 6.5 (net.sourceforge.jtds.jdbcx.JtdsDataSource). The driver is only on the classpath of the managed servers, not the admin server.
In this case, we do not see the XA properties in the advanced options (eg Enable XA Transaction Timeout). I am assuming this is because the admin server does not know if the driver is XA or not.
Is there a way to have weblogic show the XA properties, without placing the driver on the admin server classpath?

Failure when connecting MS SQL SERVER from ODI ! could not load JDBS driver

i have some trouble with connecting MS SQL SERVER from ODI.
I have already downland jdbs driver 3.0 (and 2.0 ) and copy the sqljdbc4.jar to D:\oracle\product\11.1.1\Oracle_ODI_1\oracledi\agent\drivers( where the oracle jdbs driver is already exitst )....but i have this error :
could not load JDBS driver class..
thanks

After more investigation and even more chocolate, we've identified the problem and it's now working. For anyone else who strikes this problem in future, here's something to check/consider/try:
Even though Squirrel SQL Client was connecting and working ok using the MS JDBC driver (v 3.0), it recorded this in its logs:
Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the INTERSECT operation.
We've found that the open source jTDS driver does not have the same issue as the Microsoft one.
We've installed the current jTDS driver, recorded the driver name (net.sourceforge.jtds.jdbc.Driver) and the JDBC URL (jdbc:jtds:sqlserver://<hostname>:1433/<database>) and the connection is now working fine.
Hope this helps other people...
Thanks to those of you who offered suggestions and things to check...much appreciated.
Robyn

Jtds and SQL server 2000(Personal Edition) problem

My application need to work in standalone mode without being connected to the network.
I've installed SQL Server 2000(Personal Edition) on Windows XP platform. I've Tomat 4.1 installed on the same machine. My applciation based on jsps and servlets runs on the same machine.
I'm using the jtds driver and I use the following code to connect to SQL Server.
Class.forName("net.sourceforge.jtds.jdbc.Driver");
String str="jdbc:jtds:sqlserver://127.0.0.1/GH;tds=8.0;namedpipe=true;lastupdatecount=true";
It works fine as long as the machine is connected to the network. Once it is unplugged, it gives me the error "ArrayIndexOutofBounds Exception-1".
But my application needs to be run on a machine where there is no network at all. In the above string I tried to change 127.0.0.1 by computer name and removed namedpipe parameter.
str="jdbc:jtds:sqlserver://mypctds=8.0;lastupdatecount=true";
But it gives the same error. Any idea on this?

Infact SQl server is not listening to 1433 port. When I telnet localhost 1433, it is not connecting. I checked up Server N/w utility and Client N/w utility, both TCP and Named Pipe are enabled. Only if I include namedPipe=true, it works and it requires network connection to be present.
Under Server network utility, if I choose named pipe, the default value shows \\.\pipe\sql\query. I tried to remove \\ so that it doesn't take the network path. But it doesnot work. ANy help?

How do I install the jdbc driver for sql server 2005, in sql developer 4.0 ?

Hallo together
I need access to tables in a MS SQL Server 2005 database.
One possibility is the JDBC driver.
How do i install this driver ?
Thank you very much for your postings.

Hi,
This is from the documentation -
Database: Third Party JDBC Drivers
The Third Party JDBC Drivers pane specifies drivers to be used for connections to third-party (non-Oracle) databases, such as IBM DB2, MySQL, Microsoft SQL Server, or Sybase Adaptive Server. (You do not need to add a driver for connections to Microsoft Access databases.) To add a driver, click Add Entry and select the path for the driver:
For Microsoft SQL Server or Sybase Adaptive Server: jtds-1.2.jar, which is included in the jtds-1.2-dist.zip download
To find a specific third-party JDBC driver, see the appropriate website (for example, http://www.mysql.com for the MySQL Connector/J JDBC driver for MySQL, http://jtds.sourceforge.net/ for the jTDS driver for Microsoft SQL Server and Sybase Adaptive Server, or search at http://www.teradata.com/ for the JDBC driver for Teradata). For MySQL, use the MySQL 5.0 driver, not 5.1 or later, with SQL Developer release 1.5.
You must specify a third-party JDBC driver or install a driver using the Check for Updates feature before you can create a database connection to a third-party database of that associated type. (See the tabs for creating connections to third-party databases in the Create/Edit/Select Database Connection dialog box.)
Alternative:
As an alternative to using this preference, you can click Help, then Check for Updates to install the JTDS JDBC Driver for Microsoft SQL Server and the MySQL JDBE Driver as extensions.
Regards,
Mike

SQL Server 2000 Driver for JDBC SP3 and J2SE 5.0?

Hi.
On http://www.microsoft.com/downloads/details.aspx?FamilyID=07287b11-0502-461a-b138-2aa54bfdc03a&DisplayLang=en
it says JDK versions up to 1.4 are supported (I guess that probably means NO), but I'm wondering if anyone knows if it's possible to use 1.5?
Thanks!

Hi.
On
http://www.microsoft.com/downloads/details.aspx?Family
ID=07287b11-0502-461a-b138-2aa54bfdc03a&DisplayLang=en
it says JDK versions up to 1.4 are supported (I guess
that probably means NO), but I'm wondering if anyone
knows if it's possible to use 1.5?
Thanks!I can't imagine why not. They most likely have that list so that they can say we don't support 1.1.4 or something.
But I gotta be perfectly honest with you. That driver (from the messages posted here) seems to be a real piece of rubbish. Gee I wonder why that would be? I recommend (based on my personal usage experience) the jtds driver http://jtds.sourceforge.net/ Which is free, open source and also a type 4 driver.

Error in Connecting to MS SQL 2005 via JDBC Driver

Here's the setup
CF MX7 resides on a centOS wid Apache 2.0 webserver box.
I need to established a datasource connection between the
Coldfusion server and a MSSQL 2005 Express+SP1 database sitting on
a remote XP wid SP2 setup.
I've also downloaded and installed on the /lib folder of the
CFMX7 server the corresponding JDBC drivers (versions 1.1 and 1.0)
for the MS SQL server.
The thing is, this problem always occurs:
Connection verification failed for data source:
datasourcename
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for
JDBC]Error establishing socket.
The root cause was that: java.sql.SQLException:
[Microsoft][SQLServer 2000 Driver for JDBC]Error establishing
socket.
The datasource connection info is as follows:
CF Datasource Name: datasourcename_JDBCdriver
JDBC URL:
jdbc:microsoft:sqlserver://192.168.0.47:1433;DatabaseName=nameofdatabase
Driver Class: com.microsoft.sqlserver.jdbc.SQLServerDriver
Driver Name: mssql2005
Username: sa
Password: userdefinedpassword
I've already tried these settings:
* Enabled mix mode of authentication under the SQL server
* Affix a /MSSQLSERVER instance name on the jdbc url setting
"jdbc:microsoft:sqlserver://192.168.0.47\MSSQLSERVER:1433;DatabaseName=nameofdatabase"
but a different error had occured:
The root cause was that: java.sql.SQLException:
[Microsoft][SQLServer 2000 Driver for JDBC]The requested instance
is either invalid or not running.
so i remove it since its only an optional setting
* Configured the SQL 2005 Express, under the SQL Server
Configuration Manager, to listen to protocol TCP/IP under port 1433
(this is the ONLY ENABLE protocol)
I've checked using Telnet and netstat and the SQL service is
normally listening to the said port.
* Disabled windows firewall under XP (came with SP2)
and even tried using other JDBC drivers such as:
* macromedia drivers
* jtds driver
but to no avail.
Is the problem still within the MS SQL 2005 Express wid
XP+SP2 box or a connecting issue on the Cf server under the
centOS/Apache machine?
A little help would do wonders just about now.

I had the same problem, but do not have express version. In
the configuration manger, I viewed the properties of the enabled
tcp/ip protocol. On the IP addresses tab, I found that though the
IPs were enabled, the drop down beside active was no. I changed all
to yes, applied it and restarted my instance. Then in the cf
datasource I left the port blank and everything worked.

JTDS JDBC CONNECTON ERROR

ha ii
I try to connect my database using jtds driver.Error indicate **java.sql.SQLException: Network error IOException: Connection refused: connect* , then i check jtds Faq then i fallow these steps
Why do I get java.sql.SQLException: "Network error IOException: Connection refused: connect" when trying to get a connection?
The "Connection refused" exception is thrown by jTDS when it is unable to connect to the server. There may be a number of reasons why this could happen:
1. The server name is misspelled or the port number is incorrect.
2. SQL Server is not configured to use TCP/IP. Either enable TCP/IP from SQL Server's Network Utility app or have jTDS connect via named pipes (see the URL format for information on how to do this).
3. There is a firewall blocking port 1433 on the server.
Error is still
I disable firewall also
my jdbc url is
*("jdbc:jtds:sqlserver://220.247.224.219:1433/sms;username;password");*
I install jtds driver on the c: drive program folder and configure it.
can any one help me to solve this problem.
So i wont to check my jtds installation correct , plese tel me how to install the jtds driver.
can any one help me
thank you

The "Connection refused" exception is thrown by jTDS when it is unable to connect to the server. There may be a number of reasons why this could happen:
1. The server name is misspelled or the port number is incorrect.
2. SQL Server is not configured to use TCP/IP. Either enable TCP/IP from SQL Server's Network Utility app or have jTDS connect via named pipes (see the URL format for information on how to do this).
3. There is a firewall blocking port 1433 on the server.
Error is still
I disable firewall also On both the client and the server?
Your problem is then either 1 or 2.

JTDS driver

Similar Messages

Maybe you are looking for