Error Creating Connection Pool for Microsoft SQL Server

I am trying to create a connection pool that connects to a MS SQl Server but it keeps giving me an error
Unable to create : com.microsoft.sqlserver.jdbc.SQLServerDriver
Missing class: com.microsoft.sqlserver.jdbc.SQLServerDriver Dependent class: oracle.oc4j.sql.config.DataSourceConfigUtils Loader: oc4j:10.1.3 Code-Source: /D:/jdevstudiobase1013/j2ee/home/lib/oc4j-internal.jar Configuration: in META-INF/boot.xml in D:\jdevstudiobase1013\j2ee\home\oc4j.jar This load was initiated at system.root:0.0.0 using the Class.forName() method. The missing class is not available from any code-source or loader in the system.
I have added the Microsoft Jar to the D:/jdevstudiobase1013/j2ee/home/lib/ and also to D:/jdevstudiobase1013/j2ee/home/. Please any suggestion would be welcome

Similar Messages

Cant create connection Pool for MS SQL Server 2000 with Microsoft Driver

i am using bea weblogic server 6.1, i cant create connection pool while using MS
SQL Server 2000. i have installed JDBC Driver SAP1 from microsoft website. when
i give the following class name for JDBC driver and the connection url and click
apply while selecting the available server, a number of exception appears in default
server (that is the connection pool cannot be created..... cannot load the driver
class).
URL= jdbc:Microsoft:sqlserver://127.0.0.1:1433;DatabaseName=MyDB
Driver= com.microsoft.jdbc.sqlserver.SQLServerDriver
when i use the above setting in a JDBC simple application in Jbuilder
7.0 the application runs successfully and fetches the data deom MS SQL database
but in at Bea connection Pool is not created with these settings. i do give appropriate
username and password in properties field in connection pool. Thankx for any help!

khabbab wrote:
That was the original code part from "startweblogic" :
:runWebLogic
echo on
set PATH=.\bin;%PATH%
set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;
echo off
and i changed it to :
:runWebLogic
echo on
set PATH=.\bin;%PATH%
set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;D:\Program Files\Microsoft
SQL Server 2000 Driver for JDBC\lib\msbase.jar;D:\Program Files\Microsoft SQL
Server 2000 Driver for JDBC\lib\msutil.jar;D:\Program Files\Microsoft SQL Server
2000 Driver for JDBC\lib\mssqlserver.jar;I suggest moving or copying the three ms driver jars to a directory that has no blanks
in it so the classpath doesn't have blanks in it. Ie:
go to the "D:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib"
directory and do this:
mkdir D:\microsoft_jdbc_driver
cp *.jar D:\microsoft_jdbc_driver
Then make the classpath include D:\microsoft_jdbc_driver\msbase.jar etc.
Joe
>
>
echo off
when i save and run the bat file, server appears then disappears.
Joseph Weinstein <[email protected]_this> wrote:
khabbab wrote:
The class path which is echoed at server startup does not include thepaths to
driver jar files. when i edited the "startweblogic.bat" file and includedthe
driver class paths to jar files, now the server doesnot even run. tellme what
to do now???Show me what change you made to the startweblogic file.
Joe
Joseph Weinstein <[email protected]_this> wrote:
khabbab wrote:
kindly tell me how can i check that the class paths for driver jarfiles are included
in that string? thanks. also tell me can not i use the jdriver forsql server
2000?.The startup script will echo what it's doing, including printing out
the classpath
it will use. Yes you can use the jDriver for MS SQL2000. It is sufficient
for
basic JDBC, but the MS drivfer is preferable in some ways.
Joe
Joseph Weinstein <[email protected]_this> wrote:
khabbab wrote:
i am using bea weblogic server 6.1, i cant create connection
pool
while
using MS
SQL Server 2000. i have installed JDBC Driver SAP1 from microsoft
website.
when
i give the following class name for JDBC driver and the connectionurl and click
apply while selecting the available server, a number of exception
appears
in default
server (that is the connection pool cannot be created..... cannot
load
the driver
class).The server startup script creates a string that will become the
classpath
for the server.
This string is part of the java call to start the server with a-classpath
argument. You need to
make sure the MS driver jars are part of that classpath string.
Joe
URL= jdbc:Microsoft:sqlserver://127.0.0.1:1433;DatabaseName=MyDB
Driver= com.microsoft.jdbc.sqlserver.SQLServerDriver
when i use the above setting in a JDBC simple applicationin Jbuilder
7.0 the application runs successfully and fetches the data deom
MS
SQL database
but in at Bea connection Pool is not created with these settings.
i
do give appropriate
username and password in properties field in connection pool.
Thankx
for any help!
khabbab wrote:
The class path which is echoed at server startup does not include thepaths to
driver jar files. when i edited the "startweblogic.bat" file and includedthe
driver class paths to jar files, now the server doesnot even run. tellme what
to do now???
Joseph Weinstein <[email protected]_this> wrote:
khabbab wrote:
kindly tell me how can i check that the class paths for driver jarfiles are included
in that string? thanks. also tell me can not i use the jdriver forsql server
2000?.The startup script will echo what it's doing, including printing out
the classpath
it will use. Yes you can use the jDriver for MS SQL2000. It is sufficient
for
basic JDBC, but the MS drivfer is preferable in some ways.
Joe
Joseph Weinstein <[email protected]_this> wrote:
khabbab wrote:
i am using bea weblogic server 6.1, i cant create connection
pool
while
using MS
SQL Server 2000. i have installed JDBC Driver SAP1 from microsoft
website.
when
i give the following class name for JDBC driver and the connectionurl and click
apply while selecting the available server, a number of exception
appears
in default
server (that is the connection pool cannot be created..... cannot
load
the driver
class).The server startup script creates a string that will become the
classpath
for the server.
This string is part of the java call to start the server with a-classpath
argument. You need to
make sure the MS driver jars are part of that classpath string.
Joe
URL= jdbc:Microsoft:sqlserver://127.0.0.1:1433;DatabaseName=MyDB
Driver= com.microsoft.jdbc.sqlserver.SQLServerDriver
when i use the above setting in a JDBC simple applicationin Jbuilder
7.0 the application runs successfully and fetches the data deom
MS
SQL database
but in at Bea connection Pool is not created with these settings.
i
do give appropriate
username and password in properties field in connection pool.
Thankx
for any help!

Error creating connection pool for WLS6.1 for DB2 connect

Hi,
We have installed licensed copy of Weblogic 6.1 Applciation server on HPUX 11.0.
Our backend system is DB2 on Mainframe (S/390). We have installed DB2Connect
JDBC driver ver 7.1 on HPUX. While creating pool throught weblogic console with
following parameters:
Name: DB2Pool
URL:jdbc:db2:INFOSYSG
Driver Classname: COM.ibm.db2.jdbc.app.DB2Driver
Properties:
user=jargon
password=jargon
Then appropriate Target was selected.
When server was started following error was recevied on console:
"CLI0647E Error allocating DB2 environment handle, rc=db2jdbc"
Any pointers to the solution are welcome.
Regards,
Punam Chordia
Infosys Technologies Ltd, Pune
Phone: 91-20-2932000 Ext. 5650
Fax: 91-20-2932832

Hi,
thank you for your answer, but i already fixed my problem.
i simply put the profile-script of the db2-instance into the start script of the
weblogic server.
i didn´t really figure out so far which variable was missing, but now it works.
unfortunately i found that this driver supports only 2 connections at the same
time when using jdk 1.3.0 :-(.
Regards,
Andreas Koch
Netfidelity Consulting GmbH
tel +49 211 6012330
fax +49 211 6012320
mail [email protected]
Joseph Weinstein <[email protected]> wrote:
If you can connect to DB2 on your own, using their
driver and their JDBC examples, then show me the code
that works, and show me the classpath and OS environment
you're running in, and I'll show you what should be
done for the server.
Andreas Koch wrote:
Hi,
unfortunately i have the same problem and found no solution so far.
you may check my start-script, but in my eyes all db/2 stuff shouldbe
found.
thanks for urgent help
Andreas Koch
NetFidelity Consulting Gmbh
[email protected]
"Slava Imeshev" <[email protected]> schrieb im Newsbeitrag
news:[email protected]...
Hi Punam,
You need to make sure that all driver's native libraries are
available to the Weblogic. Check if SQLLIB\bin is on the path
and let us know if it helps.
Regards,
Slava Imeshev
"Punam" <[email protected]> wrote in message
news:[email protected]...
Hi,
We have installed licensed copy of Weblogic 6.1 Applciation server
on
HPUX
11.0.
Our backend system is DB2 on Mainframe (S/390). We have installedDB2Connect
JDBC driver ver 7.1 on HPUX. While creating pool throught weblogic
console
with
following parameters:
Name: DB2Pool
URL:jdbc:db2:INFOSYSG
Driver Classname: COM.ibm.db2.jdbc.app.DB2Driver
Properties:
user=jargon
password=jargon
Then appropriate Target was selected.
When server was started following error was recevied on console:
"CLI0647E Error allocating DB2 environment handle, rc=db2jdbc"
Any pointers to the solution are welcome.
Regards,
Punam Chordia
Infosys Technologies Ltd, Pune
Phone: 91-20-2932000 Ext. 5650
Fax: 91-20-2932832
Name: startWebLogic.sh
startWebLogic.sh Type: Kornshell Script File (application/x-unknown-content-type-mks_shell)
Encoding: x-uuencode

Code for connecting to a Microsoft SQL server database

Hi
What is the code for connection to a Microsoft SQL server database using JSP? I know the structure of the code but i do not know the driver name. Any importing required besides java.sql?
Thanks

Back up there. JSP's should never contain any
database code. You should write a bean to handle
database transactions and call that from your JSP.I agree wholeheartedly with that.
Why didn't you consult google to help you with your
problem? The answer is on the MS website.
http://support.microsoft.com/default.aspx?scid=kb;en-u
s;313100This is correct, too. Isn't Google installed on your machine?
%

JDriver for microsoft sql server 2000

"Hi, Currently, I am using your JDriver for microsoft SQL server 2000 for evaluation purposes and confront the following problem: (1) using utils.dbping C:\student\work>java utils.dbping mssqlserver4 sa "" ywu**** Success!!! ****You can connect to the database in your app using: java.util.Properties props = new java.util.Properties(); props.put("user", "sa"); props.put("password", ""); java.sql.Driver d = (java.sql.Driver)Class.forName("weblogic.jdbc.mssqlserver.Driver").newInstance(); java.sql.Connection conn = d.connect("jdbc:weblogic:mssqlserver4:ywu", props) // This mode is superior, especially in serverside classes because // it avoids DriverManager calls are class synchronized, and will // bottleneck any other JDBC in the server, even already-running // connections, because all JDBC drivers use DriverManager.println() // to log info and exceptions, and that call is also class synchronized. // For repeated connecting, a single driver instance can be re-used.**** or **** Class.forName("weblogic.jdbc.mssqlserver4.Driver").newInstance(); java.sql.Connection conn = DriverManager.getConnection("jdbc:weblogic:mssqlserver4:ywu", "sa", "");**** or **** java.util.Properties props = new java.util.Properties(); props.put("user", "sa"); props.put("password", ""); props.put("server", "ywu"); Class.forName("weblogic.jdbc.mssqlserver4.Driver").newInstance(); java.sql.Connection conn = DriverManager.getConnection("jdbc:weblogic:mssqlserver4", props);It seems that everything is fine, but(2) set up connection pool to MS SQL server, the weblogic server prints out error messages during the server goes up:<Jun 18, 2001 5:51:22 PM EDT> <Error> <JDBC Connection Pool> <Cannot startup connection pool "newSQLconn" weblogic.common.ResourceException:Could not create pool connection. The DBMS driver exception was:Driver

Hi,
I was having the same problem and to solve it u have to point your classpath to
mssqlserver4v65.jar in the lib directory of your wl installation, in my case i
did:
set classpath=%classpath%;%WL_HOME%\lib\mssqlserver4v65.jar
I hope it helps.
Yuanqing Wu <[email protected]> wrote:
"Hi, Currently, I am using your JDriver for microsoft SQL server 2000
for evaluation purposes and confront the following problem: (1)
using utils.dbping C:\student\work>java utils.dbping
mssqlserver4 sa "" ywu**** Success!!! ****You can connect to the database
in your app using: java.util.Properties props = new java.util.Properties();
props.put("user", "sa"); props.put("password", ""); java.sql.Driver
d = (java.sql.Driver)Class.forName("weblogic.jdbc.mssqlserver.Driver").newInstance();
java.sql.Connection conn = d.connect("jdbc:weblogic:mssqlserver4:ywu",
props) // This mode is superior, especially in serverside classes because
// it avoids DriverManager calls are class synchronized, and will
// bottleneck any other JDBC in the server, even already-running //
connections, because all JDBC drivers use DriverManager.println() //
to log info and exceptions, and that call is also class synchronized.
// For repeated connecting, a single driver instance can be re-used.****
or
**** Class.forName("weblogic.jdbc.mssqlserver4.Driver").newInstance();
java.sql.Connection conn = DriverManager.getConnection("jdbc:weblogic:mssqlserver4:ywu",
"sa", "");**** or **** java.util.Properties props = new java.util.Properties();
props.put("user", "sa"); props.put("password", ""); props.put("server",
"ywu"); Class.forName("weblogic.jdbc.mssqlserver4.Driver").newInstance();
java.sql.Connection conn = DriverManager.getConnection("jdbc:weblogic:mssqlserver4",
props);It
seems that everything is fine, but(2) set up connection pool to MS SQL
server, the weblogic server prints out error messages during the server
goes up:<Jun 18, 2001 5:51:22 PM EDT> <Error> <JDBC Connection Pool>
<Cannot startup connection pool "newSQLconn" weblogic.common.ResourceException:Could
not create pool connection. The DBMS driver exception was:Driver

How to connect musicdb to Microsoft SQL Server

hi..
i have tried musicdb example with mysql, but i need to connect it to SQL Server.
i have created a similar DB in SQL SERVER, however i am not able to create a user, similar to musicdbuser and musicdbpass in SQL SERVER.
Also in the Administrator console i followed these steps.
1. Applications->web Applications->deployed the war file-> OK
2.Resources->JDBC->Connection Pool->New->Name ='musicdb-jdbc-pool-SQLserver'->Resource Type='javax.sql.Datasource'->Database Vendor='Microsoft SQL SERVER'-> Next
added properties Values
databaseName musicdb(this is the database i created in MS SQL SERVER)
databaseSourceName musicdb(this is the DSN name i created in control panel->ODBC connections)
networkProtocol TCP
user sa (this is the username that i use to start SQL SERVER)
password syntel123$ (this is the password that i use with the above user )
portNumber 1443
serverName localhost
then i click finish.
if i say ping to this connection , i get success!!
3. then i goto resources->jdbc->jdbc resources->new->JNDI Name="jdbc/musicdb"->pool name="musicdb-jdbc-pool-SQLserver'"->ok
4. Then i click resources->connectors->connector connection pool->new->Name="mep/musicdb"->resource adapter="ds-jcr-connector-jaxrs"->next->finish
5 Then i click resources->connector resources->new->JNDI name="mep/musicdb"->pool="mep/musicdb"->ok
however when i hit the URL http://localhost:8080/musicdb/resources/albums
i get the following error
type : Exception report
message
description: The server encountered an internal error () that prevented it from fulfilling this request.
exception: javax.servlet.ServletException: com.sun.jersey.api.container.ContainerException: java.lang.NoClassDefFoundError: Could not initialize class com.sun.mep.ws.vtms.util.ConnectionPool
root cause: com.sun.jersey.api.container.ContainerException: java.lang.NoClassDefFoundError: Could not initialize class com.sun.mep.ws.vtms.util.ConnectionPool
root cause: java.lang.NoClassDefFoundError: Could not initialize class com.sun.mep.ws.vtms.util.ConnectionPool

Hi,
I was able to create a JDBC connection pool for SQL Server successfully and will share the key steps, and was able to create a MEP user with an ECBO connection configured for the SQL Server; However, it looks like there is a "false positive" problem. Even though the user was created with the SQL Server connector whose associated JDBC connection pool passed the Ping test, doing a sync as that user changed the MySQL database album table and not the SQL Sever album table. MEP didn't give any error at all. I will bring this up with our engineers.
Here are the steps for at least getting GF JDBC connections with SQL Server working.
1. With MS SQL Sever 2005 Server Management Studio,
created a 'musicdb' database, a 'musicdbuser' user with password 'musicdbpass',
and added the 'album' table with
name (varchar(30) primary key, not null)
artist (varchar(30), not null)
date_published (datetime, not null)
rating (int, not null)
username (varchar(30), not null)
2. With MS SQLServer Configuration Manager, enable TCP/IP on static IP address
and 127.0.0.1 on port 1433 and restarted the SQL Server service
3. Downloaded Microsoft's 2.0 Driver for SQL Server 2005
4. Copied the driver sqljdbc4.jar to GF_HOME/domains/mep/lib/ext
5. Restarted GF
6. Login to GF Admin Console
7. Create Resources -> JDBC -> Connection Pool
name: musicdb_pool_sqlserver
resource type: javax.sql.DataSource
datasource class: com.microsoft.sqlserver.jdbc.SQLServerDataSource
8. Create Resources -> JDBC -> Resource
name jdbc/musicdb_sqlserver
9. Go back to musicdb_pool_sqlserver and click Additional Properties then add
user: musicdbuser
password: musicdbpass
serverName=localhost
portNumber=1433
databaseName=musicdb
10. Click General tab and click Ping. Get Success!

Trouble connecting to the Microsoft SQL Server 2005 using JDBC Connection

Hi,
I am unable to connect to the Microsoft SQL Server 2005 using JDBC Connection. Kindly tell me steps to connect to the SQL Server using JDBC. The error message that I am getting while creating a data source is :
java.rmi.RemoteException: com.sap.engine.services.dbpool.exceptions.BaseRemoteException: Error during start of application "sap.com/JDBCConnector_KedDS.xml". [id = StartupError]
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:608)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
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:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
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:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
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:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.rmi.RemoteException: Error occurred while starting application in whole cluster and wait.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 13169050:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "KedDS".
at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1843)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4761)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
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:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
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:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
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:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance ManagedConnectionFactoryImpl.
at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.<init>(ManagedConnectionFactoryImpl.java:78)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1779)
... 42 more
Caused by: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver
Found in negative cache
------------------------- Loader Info -------------------------
ClassLoader name: [library:KedDriver]
Parent loader name: [Frame ClassLoader]
No references !
Resources:
E:\usr\sap\J2E\JC01\j2ee\cluster\server0\bin\ext\KedDriver\sqljdbc.jar
E:\usr\sap\J2E\JC01\j2ee\cluster\server0\bin\core_lib\opensqlport.jar
Loading model: {parent,local,references}
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:360)
at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.<init>(ManagedConnectionFactoryImpl.java:74)
... 43 more
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:663)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
... 31 more
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 13169050:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "KedDS".
at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1843)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4761)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
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:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
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:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
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:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance ManagedConnectionFactoryImpl.
at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.<init>(ManagedConnectionFactoryImpl.java:78)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1779)
... 42 more
Caused by: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver
Found in negative cache
------------------------- Loader Info -------------------------
ClassLoader name: [library:KedDriver]
Parent loader name: [Frame ClassLoader]
No references !
Resources:
E:\usr\sap\J2E\JC01\j2ee\cluster\server0\bin\ext\KedDriver\sqljdbc.jar
E:\usr\sap\J2E\JC01\j2ee\cluster\server0\bin\core_lib\opensqlport.jar
Loading model: {parent,local,references}
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:360)
at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.<init>(ManagedConnectionFactoryImpl.java:74)
... 43 more
at com.sap.engine.services.deploy.server.application.ParallelAdapter.sleepClientThread(ParallelAdapter.java:270)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:127)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4761)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
... 33 more
at com.sap.engine.services.dbpool.exceptions.BaseRemoteException.writeReplace(BaseRemoteException.java:178)
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 java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:896)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1011)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
at javax.management.MBeanException.writeObject(MBeanException.java:126)
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 java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:964)
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 java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at com.sap.engine.services.jmx.ResponseMessage.writeBody(ResponseMessage.java:177)
at com.sap.engine.services.jmx.Message.writeMsg(Message.java:257)
at com.sap.engine.services.jmx.Message.getMsg(Message.java:453)
at com.sap.engine.services.jmx.Message.writeExternal(Message.java:505)
at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1267)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:66)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

i'm using jcreator pro
jdk i.6
mssql server 2005
and downloaded the jdbc driver( i noticed that the msutil.jar and msbase.jar are not in the folder avalable on microsoft site Microsoft SQL Server 2005 JDBC Driver so i installed
Microsoft SQL Server 2000 Driver for JDBC 1st and just changed the jqljdb.jar file with the one available in Microsoft SQL Server 2005 JDBC Driver )
and set the path of the CLASSPATH to a folder which name has no spaces
and tried Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
and Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
and tried compiling and running with command prompt
and still have the same exception which occurs at runtime
"An exception has occured: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver"
i really need help

JDBC for microsoft Sql server giving erro

hello,
I am getting an class not found exception when i am trying to load the JDBC Driver for microsoft SQL Server.
//Driver d = (Driver)Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver").newInstance();
// Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver"); // 2005 version
Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver"); // 2000 version
I have tried all these 3 methods still i am getting this error
C:\Documents and Settings\rshekdar>java -jar D:\NetBeansProjects\HelloWorldApp\dist\HelloWorldApp.jar
Hello World!
exception caught in class for namecom.microsoft.jdbc.sqlserver.SQLServerDriver
java.lang.ClassNotFoundException: com.microsoft.jdbc.sqlserver.SQLServerDriver
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at helloworldapp.Main.main(Main.java:28)
here is my classpath
C:\Documents and Settings\rshekdar>set classpath
CLASSPATH=.;C:\Program Files\Sybase\Jaguar CTS 3.5\html\classes;C:\Program Files\Sybase\Jaguar CTS 3.5\java\classes;C:\Program Files
\Sybase\Shared\PowerBuilder\classes.zip;C:\Program Files\Java\jdk1.6.0_10\lib;C:\Program Files\Java\jre1.6.0_06\lib\ext\QTJava.zip;C
:\Program Files\Java\jdk1.6.0_10;C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\mssqlserver.jar;C:\Program Files\Mic
rosoft SQL Server 2000 Driver for JDBC\lib\msbase.jar;C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msutil.jar;
can anyone tell me whats wrong here please i have tried all that i could possibly do. I cannot see anything wrong here, maybe a fresh set of eyes could. Any help given would be highly appreciated.

Sorry, I didn't see your first first post of your CLASSPATH... I lost in the stack-trace (silly me ;-)
C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\mssqlserver.jar;
C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msbase.jar;
C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msutil.jar;Yep, They look like they might be Sequel JDBC drivers to me... So open each of those jars in your zip-utility (winzip or whatever) and see if any of them contain the missing class: com.microsoft.jdbc.sqlserver.SQLServerDriver OR anything which looks similar... Are you certain the 2K and 05 class names are the same?
And If the required class does exist then Q: Does java -jar use the CLASSPATH environment variable at all? ... If I was implementing it wouldn't... too "tacky"... I'd respect the classpath in the manifest, and an explicit -cp switch, but I wouldn't trust the system environment variable to point me to the "correct" required classes... not in a pink fit.
I hope that helps some... these problems can be just sooooo frustrating!
Cheers. Keith.

Best driver available for MicroSoft SQL server?

Hi,
I am using MS-SQL server for my application server.
Which driver should i use for it?
Right now I am using ODBC driver.
Please suggest me a few links where i could get the best driver(thin driver) for SQL server.
regards
suri

Hi,
best driver available for MicroSoft SQL server?i-net software has written a solid JDBC driver based on TDS. The trial version is limited to a single connection. http://www.inetsoftware.de/English/Produkte/JDBC_Overview/ms.htm
jTurbo provides jdbc driver for MS SQL Server (www.jTurbo.com).
Merant technologies also provides jdbc driver for MS SQL Server. Find more details at http://www.microsoft.com/sql/downloads/2000/jdbc.asp.Microsoft licenses MERANT's JDBC driver for SQL Server 2000.
I cannot comment which one is the best driver. It depends on your project requirements and the buget alloted.
Hope this helps.
Good Luck.
Gayam.Srinivasa Reddy
Developer Technical Support
Sun Micro Sysytems
http://www.sun.com/developers/support/

Reporting Services for Microsoft SQL Server 2008 R2 (RTM) - 10.50.1617.0

Hello,
We are currently running:
Microsoft SQL Server 2008 R2 (RTM) - 10.50.1617.0 (Intel X86) Apr 22 2011 11:57:00 Copyright (c) Microsoft Corporation Standard Edition on Windows NT 5.2 <X86> (Build 3790: Service Pack 2) (Hypervisor)
We would like to know what is required to configure Reporting Services for Microsoft SQL Server 2008 R2 Standard. Is their a cost associated? I need to inform our IT people what is needed.
Looking forward to your reply, Linda

Double post:
http://social.msdn.microsoft.com/Forums/en-US/3e6c5d4e-228e-4a95-b017-4c20ec61cae4/reporting-services-sql-server-express-2008-r2?forum=sqlreportingservices
Olaf Helper
[ Blog] [ Xing] [ MVP]

Steps to create Connection pool for Oracle apps Adapter.

Hi All,
Could please tel me the steps to create connection pool for Oracle Apps Adapter.
Thanks,
Parker

Steps are given in section "Configuring Connection Information" in Apps Adapter User guide at below link -
http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10537/T430238T430340.htm#T464886
Regards,
Anuj

Metric for Microsoft SQL Server

I'm looking for the Metrics Reference Manual for Microsoft SQL Server. Can't find it on the documentation site

Please check at http://download-west.oracle.com/docs/cd/B16240_01/doc/em.102/b28748/toc.htm

BEA WebLogic jDriver for Microsoft SQL Server

Will BEA continue to support current and future installations of WebLogic jDriver for Microsoft SQL Server 2000 even though BEA recommends to use the JDBC driver available from Microsoft? A written response is necessary in order to determine our future product development direction.
Thank you for your attention regarding this matter.

Actually, this driver is already documented as deprecated. We intended to remove it from a future
release (most likely, the release after WLS 8.1).
The plan is to ship another driver out-of-the-box. We have been evaluating various drivers
for features, quality, and performance. We are pushing very hard to have this replacement
driver available in 8.1SP01, which will also ship with the WLI/Portal/WLW GA (announced to
ship in July). The most likely candidate is already in testing both at the WLS level and
with the layered products. It also did quite well in an internal performance comparison.
"Joseph Weinstein" <[email protected]_this> wrote in message news:[email protected]_this...
>
>
Peter Foskaris wrote:
Will BEA continue to support current and future installations of WebLogic jDriver for Microsoft SQL Server 2000 even though
BEA recommends to use the JDBC driver available from Microsoft? A written response is necessary in order to determine our future
product development direction.
>>
Thank you for your attention regarding this matter.Hi. We intend to deprecate it. We may or may not fix bugs that are found in it in future, and will likely
not do any more development on it, such as implementing any JDBC 2.0 methods. It will be in
our next major release (8), but may not be in future ones.
Joe Weinstein at BEA

SYSTEM MONITORING PLUG-IN FOR MICROSOFT SQL SERVER - Licencing Cost

Hi,
We have license for Oracle 10g OEM. We are planning to implement SYSTEM MONITORING PLUG-IN FOR
MICROSOFT SQL SERVER. Do we need to Buy separate license for this Plugin.
Ritesh

On <http://www.oracle.com/us/corporate/pricing/price-lists/index.html> in the technology pricelist
check for "System Monitoring Plug-in for Non Oracle Databases"

Free JDBC 4.0 driver for Microsoft Sql Server database

Is there any free JDBC 4.0 driver for Microsoft Sql Server database? The jTDS driver is JDBC 3.0 driver. http://jtds.sourceforge.net/

Sooooooo...
what's wrong with the driver provided by Microsoft themselves? Which is JDBC 4. And free.

Error Creating Connection Pool for Microsoft SQL Server

Similar Messages

Maybe you are looking for