Could not load jdbc driver

Hello;
I failed to connect with my database, it give me the massage as following;
Cannot load the SQL driver. Include it in your classpath
Could anyone tell me why? Thanks
And i am using the Microsoft SQL server 2000, Java 2 runtime enviroment and Microsoft SQL Server 2005 JDBC Driver now.
In the user varible, i set a path for the java run time as "c:\Program Files\Java\j2re1.4.2\javaws"
and "CLASSPATH =.;C:\Program Files\Microsoft SQL Server 2005 JDBC Driver\sqljdbc_1.1\enu\sqljdbc.jar" for the JDBC Driver.
and my code as following;
public MyTest()
        //information of our connection
        //the url of the database: protocol:subprotocol:subname:computer_name:port:database_name
         String strUrl      = "jdbc:sqlserver://localhost;user=xx;password=xxxx";
        //user name and password
         String strUser      = "xx";
         String strPass      = "xxx";
        //try to load the driver
        try {
            Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
        catch (ClassNotFoundException e) {
            System.out.println( "Cannot load the SQL driver. Include it in your classpath.");
            System.exit( -1);
        //a null reference to a Connection object
        c = null;
        try {
            //open a connection to the database
           c = DriverManager.getConnection( strUrl, strUser, strPass);
        catch (SQLException e) {
            System.out.println("Cannot connect to the database. Here is the error:");
            e.printStackTrace();
            System.exit( -1);
       //create a statement object to execute sql statements
       displayInformation();  
    }

It is so sensitive with small details, i think.Nope. If you giveit the right path, it'll find it.
till has the same problem, even i used the temp folder.
-classpath= . ; "C:\temp\sqljdbc.jar"Why don't you do yourself a favor and just put that JAR right in the directory where your .java and .class files live? No path, just this:
java -classpath = .;sqljdbc.jar YourClass
"CLASSPATH=.;C:\Program Files\Microsoft SQL Server
2005 JDBC Driver\sqljdbc_1.1\enu\sqljdbc.jar"This ain't right, either. You don't put quotes around anything other than the path entry.
and i could not delete it from system variable
section now, do you think it cause problem?I don't know why you can't delete it. I don't think you should have to muck around with environment variables at all.
%

Similar Messages

  • VDS didn't start: Could not load JDBC driver

    Hello,
    I want to start the VDS Tutorial, but I get an error:
    Exception: Data source 'Derby database' failed. Check your CLASSPATH! (in Tools
    -> Options) Could not load JDBC driver 'org.apache.derby.jdbc.EmbeddedDriver'
    Shutting down...
    Data source 'Derby database' failed. Check your CLASSPATH! (in Tools -> Options)
    Could not load JDBC driver 'org.apache.derby.jdbc.EmbeddedDriver'
    But I add the derby.jar file in the VDS under Tools - Options - Classpath
    Have you any ideas...?!

    I try to start the server without the tutorial and that works...

  • 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

  • NTKERN.VXD could not load device driver

    I just installed the MSI 6380LE board with an AMD 2100+ CPU.  I have the nVIDIAGe2 Ti video card.  Two problems.  When I restarted the computer after transfering my WD 20Gb HD, Phillips CD-RW, and SMC lan card to my computer it went thru the New Hardware sequence.  No problems there.  My printer was detected on the USB port in the back.  However, when I went to print, got a cannot communicate with printer error from my Lexmark printer program.   I went to my device manager and noticed that the following occurred:
    VIA VT83C572/VT82C586 PCI to USB Universal Host
    ---> USB Root Hub!
    This is repeated three times in the device manager.
    When I click on properties for the USB Root Hub it tells me that the NTKERN.VXD could not load device driver.  
    Second issue.  I have a new case that has front USB ports, however, the pin connectors are all separated and I am not sure how to hook them up to the MB correctly as I did not notice in the manual the pin assignments for those connectors.  ANY help is greatly appreciated.  And yes, USB is enabled for all in my BIOS setup.
    Thanks in advanc!!!

    well I did the same thing with my KT3 Ultra ARU, but it works fine other than the low system stability and generally slow behavior of the HDD's since they were not optimized for this board.. but generally everything works fine, but I will need to reload windows in order to have everything moving smoothly again, plus when you do reload windows you will notice a definite speed increase, and if is generally a good idea to back up your important files and do a clean install ever so often, Most IT techs reinstall their OS's every 6-8 months.

  • Beginner Has Problem With Loading JDBC Driver Using MySQL

    Hi, I am having problem with loading JDBC driver, and need your diagnotic help.
    1. I have installed MySQL (C:\mysql), created a databse (soup), and created a littel table (VIDEOS). I am able to see the table in the console:
    sql> select * from videos
    2. I have downloaded the latest version of Connector/J (mysql-connector-java-3.1.0-alpha.zip), and unzip the zip file into my C:\ directory.
    3. I copied the mysql-connector-java-3.1.0-alpha-bin.jar to the C:\j2sdk1.4.1_02\jre\lib\ext folder and it is in my CLASSPATH
    4. MySQL server is running
    C:\> C:\mysql\bin\mysqld-nt --standalone
    5. open another DOS window and use the database
    mysql>USE SOUP
    6. succesfully compiled a Java program (javac Test.java):
    import java.sql.* ;
    public class Test
    public static void main( String[] args )
    try
    Class.forName("org.gjt.mm.mysql.Driver").newInstance();
    try
    Connection con = DriverManager.getConnection( "jdbc:mysql://localhost:3306/soup" );
    try
    Statement statement = con.createStatement();
    ResultSet rs = statement.executeQuery("SELECT TITLE FROM VIDEOS");
    while ( rs.next() )
    System.out.println( rs.getString( "TITLE" ) );
    rs.close();
    statement.close();
    catch ( SQLException e )
    System.out.println( "JDBC error: " + e );
    finally
    con.close();
    catch( SQLException e )
    System.out.println( "could not get JDBC connection: " + e );
    catch( Exception e )
    System.out.println( "could not load JDBC driver: " + e );
    7. when I run the Java program (java Test), I got
    the message:
    could not load JDBC driver: java.lang.ClassNotFoundException: org.gjt.mm.mysql.Driver
    What am I missing?

    Hi,
    I missed to specify test in my last post.
    Try running your program by explicitly setting the classspath when
    running your program . java -classpath c:\mysql-connector-java-3.1.0-alpha-bin.jar test
    Make sure your jar file contains org.gjt.mm.mysql.Driver class

  • 845e max could not load driver .. 2 pci.vxd

    I am getting an error , Windows could not load the driver for this device because the computer is reporting two PCI.VXD bus types, in the device manager.  I have Windows 98SE as my OS.  Any ideas on how I correct this?
     

    That did work eventually.....
    When I did that I had problems with multimedia devices and ended up having to pull sound cards and reinstall the drivers.  
    I did download the Intel drivers that were mentioned in another posting.
    Everything looks good now.  Thanks for the help.

  • Help - Could not load 'oracle.jdbc.driver.OracleDriver ...

    I'm using oci8 to connect to the Oracle database.
    URL: jdbc:oracle:oci8:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(PORT=1527)(HOST=testhost)))(CONNECT_DATA=(SID=fnoe2pa)))
    When I tried to start the weblogic server, I got the following errors:
    Can you suggest what I should do next (step-wise)??? Thanks, Bobby
    <Sleeping in createResource()>
    ####<15/08/2002 14:09:43> <Error> <JDBC> <qawebmethods> <myserver>
    <main> <system> <> <001060> <Cannot startup connection pool
    "pool/test_myapp" weblogic.common.ResourceException:
    Could not load 'oracle.jdbc.driver.OracleDriver
    If this is a type-4 JDBC driver, it could occur if the JDBC
    driver is not in the system CLASSPATH.
    If this is a type-2 JDBC driver, it may also indicate that
    the Driver native layers(DBMS client lib or driver DLL)
    have not been installed properly on your system
    or in your PATH environment variable.
    This is most likely caused by one of the following:
    1. The native layer SO, SL, or DLL could not be found.
    2. The file permissions on the native layer SO, SL, or DLL
    have not been set properly.
    3. The native layer SO, SL, or DLL exists, but is either
    invalid or corrupted.
    For more information, read the installation documentation
    for your JDBC Driver, available from:
    http://e-docs.bea.com
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:212)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
         at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:705)
         at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
         at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:650)
         at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
         at $Proxy31.updateDeployments(Unknown Source)
         at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
         at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
         at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
         at $Proxy42.start(Unknown Source)
         at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
         at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
         at weblogic.management.Admin.finish(Admin.java:644)
         at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
         at weblogic.Server.main(Server.java:35)
    >
    ####<15/08/2002 14:09:43> <Info> <JDBC> <qawebmethods> <myserver>
    <main> <system> <> <001082> <Creating Data Source named
    jdbc/test_myapp for pool pool/test_myapp>
    ####<15/08/2002 14:09:43> <Info> <JDBC> <qawebmethods> <myserver>
    <main> <system> <> <001070> <Checking existence of connection pool
    pool/test_myapp requested by user system>
    ####<15/08/2002 14:09:43> <Error> <JDBC> <qawebmethods> <myserver>
    <main> <system> <> <001059> <Error during Data Source creation:
    weblogic.common.ResourceException: DataSource(jdbc/test_myapp) can't
    be created with non-existent Pool (connection or multi)
    (pool/test_myapp)>
    ####<15/08/2002 14:09:50> <Info> <EJB> <qawebmethods> <myserver>
    <main> <system> <> <010008> <EJB Deploying file: myapp-ejb.jar>
    ####<15/08/2002 14:09:50> <Warning> <J2EE> <qawebmethods> <myserver>
    <main> <system> <> <160007> <You are running WebLogic Server with J2EE
    1.3 features enabled. The implementation of specific J2EE 1.3 features
    (EJB 2.0, JSP 1.2, Servlet 2.3, and J2EE Connector Architecture 1.0)
    in BEA WebLogic Server 6.1 is of a non-final version of the
    appropriate specification. It is subject to change in future releases
    once the specification becomes finalized. This may cause application
    code developed for BEA WebLogic Server 6.1 that uses the new features
    of J2EE 1.3 to be incompatible with the J2EE 1.3 platform supported in
    future releases of BEA WebLogic Server.>
    ####<15/08/2002 14:09:59> <Error> <J2EE> <qawebmethods> <myserver>
    <main> <system> <> <160001> <Error deploying application myapp-ejb:
    Unable to deploy EJB: Counter from myapp-ejb.jar:
    The DataSource with the JNDI name: jdbc/test_myapp could not be
    located. Please ensure that the DataSource has been deployed
    successfully and that the JNDI name in your EJB Deployment descriptor
    is correct.
    >
    ####<15/08/2002 14:09:59> <Info> <HTTP> <qawebmethods> <myserver>
    <main> <system> <> <101053> <[HTTP myserver] Loading web app: myapp>
    ####<15/08/2002 14:09:59> <Info> <HTTP> <qawebmethods> <myserver>
    <main> <system> <> <101059> <[myserver] Loading myapp from WAR file:
    C:\bea\wlserver6.1\.\config\mydomain\applications\.wlnotdelete\wlap31483\myapp.war>
    ####<15/08/2002 14:09:59> <Warning> <J2EE> <qawebmethods> <myserver>
    <main> <system> <> <160007> <You are running WebLogic Server with J2EE
    1.3 features enabled. The implementation of specific J2EE 1.3 features
    (EJB 2.0, JSP 1.2, Servlet 2.3, and J2EE Connector Architecture 1.0)
    in BEA WebLogic Server 6.1 is of a non-final version of the
    appropriate specification. It is subject to change in future releases
    once the specification becomes finalized. This may cause application
    code developed for BEA WebLogic Server 6.1 that uses the new features
    of J2EE 1.3 to be incompatible with the J2EE 1.3 platform supported in
    future releases of BEA WebLogic Server.>
    ####<15/08/2002 14:09:59> <Info> <HTTP> <qawebmethods> <myserver>
    <main> <system> <> <101031>
    <[WebAppServletContext(1412030,myapp,/myapp)] extracting classfiles to
    C:\bea\wlserver6.1\config\mydomain\applications\.wlnotdelete\wlap31483\WEB-INF\_tmp_war_myapp:>
    ####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
    <main> <system> <> <101032>
    <[WebAppServletContext(1412030,myapp,/myapp)] extracted classfiles
    successfully...>
    ####<15/08/2002 14:10:04> <Info> <HTTP Session> <qawebmethods>
    <myserver> <main> <system> <> <100037> <Creating SessionContext of
    type: memory for webapp: /myapp>
    ####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
    <main> <system> <> <101047>
    <[WebAppServletContext(1412030,myapp,/myapp)] registering classpath
    servlet with initArgs 'null'>
    ####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
    <main> <system> <> <101047>
    <[WebAppServletContext(1412030,myapp,/myapp)] registering getior
    servlet with initArgs 'null'>
    ####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
    <main> <system> <> <101047>
    <[WebAppServletContext(1412030,myapp,/myapp)] registering tunneling
    servlets with initArgs 'wl-dispatch-policy=direct'>
    ####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
    <main> <system> <> <101047>
    <[WebAppServletContext(1412030,myapp,/myapp)] registering JSPServlet
    with initArgs '[JspConfig:
    verbose=true,packagePrefix=jsp_servlet,-compiler=javac,compileFlags=,workingDir=C:\bea\wlserver6.1\config\mydomain\applications\.wlnotdelete\wlap31483\WEB-INF\_tmp_war_myapp,pageCheckSeconds=1,superclass=null,keepgenerated=false,precompileContinue=false,compilerSupportsEncoding=true,encoding=null,defaultfilename=index.jsp,compilerclass=null,noTryBlocks=false]'>
    ####<15/08/2002 14:10:04> <Debug> <HTTP> <qawebmethods> <myserver>
    <main> <system> <> <101097> <Registering ServletContext:
    "myapp:/myapp">
    ####<15/08/2002 14:10:04> <Info> <J2EE> <qawebmethods> <myserver>
    <main> <system> <> <160003> <Deployed : myapp>
    ####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
    <main> <system> <> <101133> <Initializing WEB server myserver>
    ####<15/08/2002 14:10:04> <Notice> <Management> <qawebmethods>
    <myserver> <main> <system> <> <141052> <Application Poller started for
    development server.>
    ####<15/08/2002 14:10:04> <Notice> <WebLogicServer> <qawebmethods>
    <myserver> <ListenThread> <system> <> <000202> <ListenThread listening
    on port 7001>
    ####<15/08/2002 14:10:04> <Info> <NT Performance Pack> <qawebmethods>
    <myserver> <ListenThread> <system> <> <000000> <NATIVE: NTSocketMuxer
    was built on Nov 1 2001 16:39:28
    >
    ####<15/08/2002 14:10:04> <Notice> <WebLogicServer> <qawebmethods>
    <myserver> <SSLListenThread> <system> <> <000202> <SSLListenThread
    listening on port 7002>
    ####<15/08/2002 14:10:05> <Notice> <Management> <qawebmethods>
    <myserver> <main> <system> <> <141030> <Starting discovery of Managed
    Server... This feature is on by default, you may turn this off by
    passing -Dweblogic.management.discover=false>
    ####<15/08/2002 14:10:05> <Notice> <WebLogicServer> <qawebmethods>
    <myserver> <main> <system> <> <000331> <Started WebLogic Admin Server
    "myserver" for domain "mydomain" running in Development Mode>
    ####<15/08/2002 14:10:11> <Info> <NT Performance Pack> <qawebmethods>
    <myserver> <ExecuteThread: '14' for queue: 'default'> <> <> <000000>
    <Allocating: '2' NT reader threads>
    ####<15/08/2002 14:10:13> <Info> <HTTP> <qawebmethods> <myserver>
    <ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'> <system>
    <> <101047> <[WebAppServletContext(5367844,console,/console)] actions:
    init>
    ####<15/08/2002 14:10:18> <Info> <HTTP> <qawebmethods> <myserver>
    <ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'> <system>
    <> <101047> <[WebAppServletContext(5367844,console,/console)]
    FileServlet: init>
    ####<15/08/2002 14:10:18> <Info> <HTTP> <qawebmethods> <myserver>
    <ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'> <system>
    <> <101047> <[WebAppServletContext(5367844,console,/console)]
    FileServlet: Using standard I/O>

    "thorick" <[email protected]> wrote in message news:<[email protected]>...
    Most likely, the OCI libraries could not be loaded.
    Before continuing down this path, is there any reason
    why you want to use an OCI based Driver as opposed to the
    all Java Oracle thin driver ?There is indeed a valid reason for my choice.
    I am currently connecting to the Oracle "Rdb" 7.0 database (located on
    VMS) - not Oracle Oracle.
    The SQL Service software we're currently using is version 7.1. This
    version works well with the OCI8 driver (when connecting to the
    database from Windows NT). This version of SQL Service however does
    NOT work for the THIN driver (unless we upgrade the SQL Service to
    version 7.1.5.5 - which we're not prepared to do so because it is not
    stable enough from our previous test/trials). SQLSRV Version 7.1.5.5
    works for THIN driver but it will result in uncommitted
    transactions/unresolved connection/stopping of listener issues and
    there is a need to restart the service from time to time. Oracle has
    since confirmed that this is a bug that they have yet to resolve...
    So we have to stick to OCI8 (THICK) for the time being. I would really
    appreciate it very much if you can tell me the various OCI libraries
    that I need to load (in terms of WebLogic Server config file settings
    etc..).
    By the way I have already installed the Oracle 8 client software on
    the NT server (where WebLogic Server is) and I have also set up the
    relevant SID (using the Net8 Assistant) that points to the Oracle Rdb
    database on the VMS. I have also tried using SQL*Plus to connect to
    the database and I can connect properly to the database. But WebLogic
    simply doesn't seem to load the software.
    Help...
    Regards,
    Bobby Brown, writing from Australia.

  • Win2000+weblogic510+oracle8i,Could not load 'oracle.jdbc.driver.OracleDriver'

    &#26143;&#26399;&#22235; &#19977;&#26376; 23 20:30:17 GMT+08:00 2000:<E> <JDBC Pool>
    Failed to create connection pool "ejavaPool"
    weblogic.common.ResourceException: Could not load 'oracle.jdbc.driver.OracleDriver'
    because
    System.loadLibrary threw java.lang.UnsatisfiedLinkError
    with the message 'oracle.jdbc.driver.OracleDriver'.
    This could occur if the JDBC driver is not in the weblogic.class.path.
    If this is a type-2 JDBC driver, it may also indicate that
    the Driver native layers(DBMS client lib or driver DLL)
    have not been installed properly on your system or in your environment.
    This is most likely caused by one of the following:
    1. The native layer SO, SL, or DLL could not be found.
    2. The file permissions on the native layer SO, SL, or DLL
    have not been set properly.
    3. The native layer SO, SL, or DLL exists, but is either
    invalid or corrupted.
    For more information, read the installation documentation
    for your JDBC Driver, available from:
    http://www.weblogic.com/docs/install/install_jdbc.html
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.loadDriver(ConnectionEnvFactory.java:82)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.<init>(ConnectionEnvFactory.java:97)
         at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:328)
         at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java, Compiled Code)
         at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:220)
         at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
         at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java, Compiled Code)
         at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
    any idea?

    If you are trying to use the thin driver you need to make sure you have the
    classes12.zip file in the weblogic server classpath. You can download this
    driver from Oracle website.
    hth
    sree
    "meijunyong" <[email protected]> wrote in message
    news:[email protected]...
    >
    &#26143;&#26399;&#22235; &#19977;&#26376; 23 20:30:17 GMT+08:00 2000:<E><JDBC Pool>
    Failed to create connection pool "ejavaPool"
    weblogic.common.ResourceException: Could not load'oracle.jdbc.driver.OracleDriver'
    because
    System.loadLibrary threw java.lang.UnsatisfiedLinkError
    with the message 'oracle.jdbc.driver.OracleDriver'.
    This could occur if the JDBC driver is not in the weblogic.class.path.
    If this is a type-2 JDBC driver, it may also indicate that
    the Driver native layers(DBMS client lib or driver DLL)
    have not been installed properly on your system or in your environment.
    This is most likely caused by one of the following:
    1. The native layer SO, SL, or DLL could not be found.
    2. The file permissions on the native layer SO, SL, or DLL
    have not been set properly.
    3. The native layer SO, SL, or DLL exists, but is either
    invalid or corrupted.
    For more information, read the installation documentation
    for your JDBC Driver, available from:
    http://www.weblogic.com/docs/install/install_jdbc.html
    atweblogic.jdbc.common.internal.ConnectionEnvFactory.loadDriver(ConnectionEnvF
    actory.java:82)
    atweblogic.jdbc.common.internal.ConnectionEnvFactory.<init>(ConnectionEnvFacto
    ry.java:97)
    atweblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:328
    at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java,Compiled Code)
    at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:220)
    at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
    at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java, CompiledCode)
    atweblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
    any idea?

  • Class Not Found: JDBC driver org.postgresql.Driver could not be loaded

    Hi
    I got the below message when i ran TORQUE
    Class Not Found: JDBC driver org.postgresql.Driver could not be loadedPlease let me know why this error arise.i have added the necessary postgresql.jar file in the classpath but still the error persist.
    Reply at the earliest.
    Thanks and Regards
    Gokul

    # The name of the project Torque will generate code for.
      torque.project = bookstore
      # The target database platform.
      torque.database = postgresql
      # The target package to put the generated classes in.
      torque.targetPackage = com.jp.bookstore
      # The JDBC URL that Torque can use to create and
      # drop databases if instructed to do so.
      torque.database.createUrl = jdbc:postgresql://192.168.0.10:5432/postgresql
      # The JDBC URL that will be used to create tables in your database.
      torque.database.buildUrl = jdbc:postgresql://192.168.0.10:5432/bookstore
      # The JDBC URL that will be used to access your database.
      torque.database.url = jdbc:postgresql://192.168.0.10:5432/bookstore
      # The JDBC database driver to use when connecting to your database.
      torque.database.driver = org.postgresql.Driver
      # The administrative username that has sufficient privileges to create
      # and drop databases and tables that Torque executes at generation time.
      torque.database.user = bjuser
      # The administrative password for the supplied username.
      torque.database.password = bjpass
      # The hostname or IP address of your database server.
      torque.database.host = 192.168.0.10

  • Admin tool could not load the essbase driver.Please check the configuration

    Hi All,
    I have obiee11g installed machine and want to connect that machine with essbase.
    For that I have installed Essbase Client [11.1.2.1] by downloading the following files,
    *1>Oracle Hyperion Enterprise Performance Management System Installer Fusion Edition Release 11.1.2.0.0 for Microsoft Windows (32-bit)*
    *2>Hyperion Enterprise Performance Management System Foundation Services Release 11.1.2.0 for Microsoft Windows (32-bit) Part 1 of 4*
    *3>Oracle Essbase Clients Release 11.1.2.0.0 for Microsoft Windows (32-bit)*
    After that I manually added the ESSBASEPATH and ARBORPATH as Environment Variables (USER).
    And also I manually added the essbasepath in bi-init.cmd file.
    Finally I tried to connect essbase with BI through BI Admin Tool, I get the following Error
    "*Admin tool could not load the essbase driver.Please check the configuration*."
    kindly guide me to overcome this issue.
    Thanks and Regards
    sai
    Edited by: 923924 on Apr 24, 2012 5:20 AM

    Until you perform the configuration on the AD server, the following message will appear:
    Error: Could not start the SSO service. Please check the configuration.
    So configure the AD server so that the error message will not appear again.

  • The tech that helped me download CC said he could not load it to my D drive, it had to go on C

    The tech that helped me download CC said he could not load it to my D drive, it had to go on the C drive.  I just bought a new computer with a separate drive for Photoshop.  Why can't you load it on a separate drive or did the techie just not understand me or me him?

    You can customize the installation location within your preferences for the Adobe Creative Cloud application.
    Please be aware if you are installing on a separate drive because your SSD is not large enough you will negate most of the performance gains from the SSD by installing the application on a standard hard drive.

  • Error loading JDBC driver

    Hi,
    I have an rpt file developed in crystal report 2008. it connects to SQL Server using ODBC(RDO) connection. I have a jsp file that needs to change the datasource to use JDBC (JNDI). The scriptlet for changing datasource is given below. I have my sqljdbc.jar in the web-inf\lib folder of my application as well as in \server\{server_name}\lib folder. when I try to run the jsp it gives me error as follows :
    ERROR [com.businessobjects.reports.sdk.JRCCommunicationAdapter]  detected an exception: Error loading JDBC driver.  The class 'com.microsoft.jdbc.sqlserver.SQLServerDriver' could not be found.
         at com.crystaldecisions.reports.queryengine.Connection.t1(Unknown Source)
         at com.crystaldecisions.reports.dataengine.dfadapter.DFAdapter.a(Unknown Source)
         at com.crystaldecisions.reports.dataengine.dfadapter.DFAdapter.for(Unknown Source)
         at com.crystaldecisions.reports.reportdefinition.ReportHelper.a(Unknown Source)
         at com.businessobjects.reports.sdk.requesthandler.ReportViewingRequestHandler.long(Unknown Source)
         at com.businessobjects.reports.sdk.requesthandler.ReportViewingRequestHandler.a(Unknown Source)
         at com.businessobjects.reports.sdk.requesthandler.ReportViewingRequestHandler.byte(Unknown Source)
         at com.businessobjects.reports.sdk.JRCCommunicationAdapter.do(Unknown Source)
         at com.businessobjects.reports.sdk.JRCCommunicationAdapter.if(Unknown Source)
         at com.businessobjects.reports.sdk.JRCCommunicationAdapter.a(Unknown Source)
         at com.businessobjects.reports.sdk.JRCCommunicationAdapter$2.a(Unknown Source)
         at com.businessobjects.reports.sdk.JRCCommunicationAdapter$2.call(Unknown Source)
         at com.crystaldecisions.reports.common.ThreadGuard.syncExecute(Unknown Source)
         at com.businessobjects.reports.sdk.JRCCommunicationAdapter.for(Unknown Source)
         at com.businessobjects.reports.sdk.JRCCommunicationAdapter.int(Unknown Source)
         at com.businessobjects.reports.sdk.JRCCommunicationAdapter.request(Unknown Source)
         at com.businessobjects.sdk.erom.jrc.a.a(Unknown Source)
         at com.businessobjects.sdk.erom.jrc.a.execute(Unknown Source)
         at com.crystaldecisions.proxy.remoteagent.RemoteAgent$a.execute(Unknown Source)
         at com.crystaldecisions.proxy.remoteagent.CommunicationChannel.a(Unknown Source)
         at com.crystaldecisions.proxy.remoteagent.RemoteAgent.a(Unknown Source)
         at com.crystaldecisions.sdk.occa.report.application.ds.a(Unknown Source)
         at com.crystaldecisions.sdk.occa.report.application.ReportSource.a(Unknown Source)
         at ....
    <br>
    <br>
    Scriptlet :
    <%
    //Report can be opened from the relative location specified in the CRConfig.xml, or the report location
    //tag can be removed to open the reports as Java resources or using an absolute path (absolute path not recommended
    //for Web applications).
    final String DBUSERNAME = "sa";
    final String DBPASSWORD = "password";
    final String CONNECTION_STRING = "!com.microsoft.jdbc.sqlserver.SQLServerDriver!jdbc:microsoft:sqlserver://localhost:1433;DatabaseName=;user=;password=";
    final String TRUSTEDCON = "false";
    final String PREQESERVERNAME = "jdbc:microsoft:sqlserver://localhost:1433";
    final String SERVERTYPE = "JDBC (JNDI)";
    final String DATABASE_DLL = "crdb_jdbc.dll";
    final String DATABASE = "bssc";
    final String DBCLASSNAME = "com.microsoft.jdbc.sqlserver.SQLServerDriver";
    final String USEJDBC = "true";
    final String DATABASE_NAME = "bssc";
    final String SERVERNAME = "jdbc:microsoft:sqlserver://localhost:1433";
    final String CONNECTIONURL = "jdbc:microsoft:sqlserver://localhost:1433";
    final String SERVER = "localhost";
    %>
    <%          
              final Logger logger = Logger.getLogger(ReportAction.class.getName());
              final String REPORT_NAME = "../reports/Krt.rpt";
    try {
              ReportClientDocument oReportClientDocument = new ReportClientDocument();
              oReportClientDocument.open(REPORT_NAME, 0);
         // Create the two connectioninfo objects to use
         IConnectionInfo oldConnectionInfo =  new ConnectionInfo();
         IConnectionInfo newConnectionInfo = new ConnectionInfo();
         // Assign the old Connection info to the reports current info
         DatabaseController dbController = oReportClientDocument.getDatabaseController();
         oldConnectionInfo = dbController.getConnectionInfos(null).getConnectionInfo(0);                                       
         // If this connection needed parameters, we would use this field.      
         Fields pFields = null;
         // Create a new propertybag for the new location
         PropertyBag boPropertyBag1 = new PropertyBag();
         // Set new table logon properties
         boPropertyBag1.put("JDBC Connection String", CONNECTION_STRING);
         boPropertyBag1.put("Trusted_Connection", TRUSTEDCON);
         boPropertyBag1.put("PreQEServerName", PREQESERVERNAME);
         boPropertyBag1.put("Server Type", SERVERTYPE);
         boPropertyBag1.put("Database DLL", DATABASE_DLL);
         boPropertyBag1.put("Database", DATABASE);
         boPropertyBag1.put("Database Class Name", DBCLASSNAME);
         boPropertyBag1.put("Use JDBC", USEJDBC);
         boPropertyBag1.put("Database Name", DATABASE_NAME);
         boPropertyBag1.put("Server Name", SERVERNAME);
         boPropertyBag1.put("Connection URL", CONNECTIONURL);
         boPropertyBag1.put("Server", SERVER);
         // Assign the properties to the connection info
         newConnectionInfo.setAttributes(boPropertyBag1);
         // Set the DB Username and Pwd
         newConnectionInfo.setUserName(DBUSERNAME);
         newConnectionInfo.setPassword(DBPASSWORD);
         // The Kind of connectionInfos is SQL
         newConnectionInfo.setKind(ConnectionInfoKind.SQL);
         // set the parameters to replace.
         // The 4 options are:
         // _doNotVerifyDB
         // _ignoreCurrentTableQualifiers
         // _mapFieldByRowsetPosition
         // _useDefault 
         int replaceParams = DBOptions._ignoreCurrentTableQualifiers + DBOptions._doNotVerifyDB;
         // Now replace the connections      
         dbController.replaceConnection(oldConnectionInfo, newConnectionInfo, pFields, replaceParams);
    %>
    <%
    //Report can be opened from the relative location specified in the CRConfig.xml, or the report location
    //tag can be removed to open the reports as Java resources or using an absolute path (absolute path not recommended
    //for Web applications).
    final String DBUSERNAME = "sa";
    final String DBPASSWORD = "password";
    final String CONNECTION_STRING = "!com.microsoft.jdbc.sqlserver.SQLServerDriver!jdbc:microsoft:sqlserver://localhost:1433;DatabaseName=;user=;password=";
    final String TRUSTEDCON = "false";
    final String PREQESERVERNAME = "jdbc:microsoft:sqlserver://localhost:1433";
    final String SERVERTYPE = "JDBC (JNDI)";
    final String DATABASE_DLL = "crdb_jdbc.dll";
    final String DATABASE = "bssc";
    final String DBCLASSNAME = "com.microsoft.jdbc.sqlserver.SQLServerDriver";
    final String USEJDBC = "true";
    final String DATABASE_NAME = "bssc";
    final String SERVERNAME = "jdbc:microsoft:sqlserver://localhost:1433";
    final String CONNECTIONURL = "jdbc:microsoft:sqlserver://localhost:1433";
    final String SERVER = "localhost";
    %>
    <%          
              final Logger logger = Logger.getLogger(ReportAction.class.getName());
              final String REPORT_NAME = "../reports/Krt.rpt";
    try {
              ReportClientDocument oReportClientDocument = new ReportClientDocument();
              oReportClientDocument.open(REPORT_NAME, 0);
         // Create the two connectioninfo objects to use
         IConnectionInfo oldConnectionInfo =  new ConnectionInfo();
         IConnectionInfo newConnectionInfo = new ConnectionInfo();
         // Assign the old Connection info to the reports current info
         DatabaseController dbController = oReportClientDocument.getDatabaseController();
         oldConnectionInfo = dbController.getConnectionInfos(null).getConnectionInfo(0);                                       
         // If this connection needed parameters, we would use this field.      
         Fields pFields = null;
         // Create a new propertybag for the new location
         PropertyBag boPropertyBag1 = new PropertyBag();
         // Set new table logon properties
         boPropertyBag1.put("JDBC Connection String", CONNECTION_STRING);
         boPropertyBag1.put("Trusted_Connection", TRUSTEDCON);
         boPropertyBag1.put("PreQEServerName", PREQESERVERNAME);
         boPropertyBag1.put("Server Type", SERVERTYPE);
         boPropertyBag1.put("Database DLL", DATABASE_DLL);
         boPropertyBag1.put("Database", DATABASE);
         boPropertyBag1.put("Database Class Name", DBCLASSNAME);
         boPropertyBag1.put("Use JDBC", USEJDBC);
         boPropertyBag1.put("Database Name", DATABASE_NAME);
         boPropertyBag1.put("Server Name", SERVERNAME);
         boPropertyBag1.put("Connection URL", CONNECTIONURL);
         boPropertyBag1.put("Server", SERVER);
         // Assign the properties to the connection info
         newConnectionInfo.setAttributes(boPropertyBag1);
         // Set the DB Username and Pwd
         newConnectionInfo.setUserName(DBUSERNAME);
         newConnectionInfo.setPassword(DBPASSWORD);
         // The Kind of connectionInfos is SQL
         newConnectionInfo.setKind(ConnectionInfoKind.SQL);
         // set the parameters to replace.
         // The 4 options are:
         // _doNotVerifyDB
         // _ignoreCurrentTableQualifiers
         // _mapFieldByRowsetPosition
         // _useDefault 
         int replaceParams = DBOptions._ignoreCurrentTableQualifiers + DBOptions._doNotVerifyDB;
         // Now replace the connections      
         dbController.replaceConnection(oldConnectionInfo, newConnectionInfo, pFields, replaceParams);
    %>
    I am not sure why it is not able to get the Driver since the required jar is there in lib folder? Am I missing something ?
    Edited by: sb-onward on Jul 30, 2009 6:01 PM

    Hi,
    Make sure you have set the Classpath in CRConfig.xml for the jdbc jar.
    Place the CrConfig.xml  in the classes directory of your application.
    Please let me know the results.
    Regards,
    Neeraj

  • Class Not Found: JDBC driver oracle.jdbc.driver.OracleDriver

    Does anyone can help?
    When I install the OpenBravo, I get the error shown below:
    Class Not Found: JDBC driver oracle.jdbc.driver.OracleDriver could not be loaded.
    I am using the Oracle XE, jdk1.5.0_06, Apache Tomcat 5.5.17.

    include the jar file classes111.jar in your classpath, it will work
    The location would be like
    C:\Applns\oracle9204\jdbc\lib\classes111.jar;
    set the classpath with this jar in command prompt
    set CLASSPATH=%CLASSPATH%;C:\Applns\oracle9204\jdbc\lib\classes111.jar;

  • Load JDBC driver in runtime

    Hi all,
    I'm trying to load mysql jdbc driver in runtime i've tried the following links
    [http://dev-loki.blogspot.com/2008/01/loading-jdbc-driver-at-runtime.html]
    [http://www.kfu.com/~nsayer/Java/dyn-jdbc.html]
    [http://www.devdaily.com/java/edu/JDBC-SQLProcessor/Simple_JDBC_Example.shtml]
    [http://tech.puredanger.com/2006/11/09/classloader/]
    [http://fdt.powerflasher.com/blog/?p=35]
    I'm not being able to get this to work it always given the classnotfoundexception
    can anyone help please?
    Thanks in advance

    There is no server. I'm doing a normal java aplication, i wanted to have a folder where would be the jdbc drivers in runtime the user will choose what driver to load to access a some db.
    I'm using eclipse and this is what i have now
    import java.sql.Connection;
    import java.sql.Driver;
    import java.sql.DriverPropertyInfo;
    import java.sql.SQLException;
    import java.util.Properties;
    public class DriverShim implements Driver{
         private Driver driver;
         public DriverShim(Driver d) {
              this.driver = d;
         public boolean acceptsURL(String u) throws SQLException {
              return this.driver.acceptsURL(u);
         public Connection connect(String u, Properties p) throws SQLException {
              return this.driver.connect(u, p);
         public int getMajorVersion() {
              return this.driver.getMajorVersion();
         public int getMinorVersion() {
              return this.driver.getMinorVersion();
         public DriverPropertyInfo[] getPropertyInfo(String u, Properties p) throws SQLException {
              return this.driver.getPropertyInfo(u, p);
         public boolean jdbcCompliant() {
              return this.driver.jdbcCompliant();
                   String libraryPath = System.getProperty("java.library.path");
              String sep = System.getProperty("path.separator");
              libraryPath = "." + sep + "C:/Users/Luis/Documents/eclipse/workspace/DBDIGGER/lib/connectors" + sep + "native" + sep + libraryPath;
              //libraryPath ="C:/Users/Luis/Documents/eclipse/workspace/DBDIGGER/lib/connectors";
              System.setProperty("java.library.path", libraryPath);
              System.out.println(libraryPath);
    URL u;
              try {
                   u = new URL("jar:file://C:/Users/Luis/Documents/eclipse/workspace/DB/lib/connectors/mysql-connector-java-5.1.7-bin.jar!/");
                   String classname = Settings.MYSQL;
                   URLClassLoader ucl = new URLClassLoader(new URL[] { u });
                   URL[] ee =ucl.getURLs();
                   Driver d = (Driver)Class.forName(classname, true, ucl).newInstance();
                   DriverManager.registerDriver(new DriverShim(d));
                   DriverManager.getConnection("jdbc:mysql://localhost:3306/mysql", "user", "pw");
              } catch (MalformedURLException e) {
                   // TODO Auto-generated catch block
                   e.printStackTrace();
              } catch (ClassNotFoundException e) {
                   // TODO Auto-generated catch block
                   e.printStackTrace();
              } catch (SQLException e) {
                   // TODO Auto-generated catch block
                   e.printStackTrace();
              } catch (InstantiationException e) {
                   // TODO Auto-generated catch block
                   e.printStackTrace();
              } catch (IllegalAccessException e) {
                   // TODO Auto-generated catch block
                   e.printStackTrace();
              } Project Folder Structure
    DB
    bin
    lib
    connectors
    mysql-connector-java-5.1.7-bin.jar
    src
    result of classpath
    .;C:/Users/Luis/Documents/eclipse/workspace/DBDIGGER/lib/connectors;native;C:\Program Files\Java\jre6\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:/Program Files/Java/jre6/bin/client;C:/Program Files/Java/jre6/bin;C:\Program Files\JavaFX\javafx-sdk1.1\bin;C:\Program Files\JavaFX\javafx-sdk1.1\emulator\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\Intel\DMIX;C:\Program Files\Softex\OmniPass;C:\Program Files\MySQL\MySQL Server 5.1\bin
    Maybe what i'm doing wrong is the classpath, this is not a web app is a standard java aplication...
    Could someone explain to me how to set a classpath ?? correctly...

  • Could not load load from location:/test_subreport.jasper

    Hi All:
    Any help or hint is greatly appreciated it!!
    I am currently using IceFaces 1.8.2, Jsf 1.1, and JasperReport 3.5.2.
    I get the following error:
    net.sf.jasperreports.engine.JRException: Could not load object from location : /test_subreport.jasper
    The report test_report.jasper has a subreport called test_subreport.jasper. I placed both test_report.jasper and test_subreport.jasper in the directory "WEB-INF/reports/"
    public String testSearch() throws Exception
              try
                   Connection connection;
                   FacesContext context = FacesContext.getCurrentInstance();
                   HttpServletResponse response = (HttpServletResponse)context.getExternalContext().getResponse();
                   InputStream reportStream = context.getExternalContext().getResourceAsStream("WEB-INF/reports/test_report.jasper");
                   ServletOutputStream servletOutputStream = response.getOutputStream();
                   ServletContext ctx = (ServletContext) FacesContext.getCurrentInstance().getExternalContext().getContext();
                   String filepath = ctx.getRealPath("/WEB-INF/reports/");
                   filepath = filepath = "/";
                   String imagepath = ctx.getRealPath("/WEB-INF/images/test_logo.gif");
              HashMap parameterMap = new HashMap();
              parameterMap.put("SUBREPORT_DIR", filepath);
              parameterMap.put("Test Number", testNumber);
              parameterMap.put("Image Path", imagepath);
              Properties properties = new Properties();
              properties.load(context.getExternalContext().getResourceAsStream("WEB-INF/config.properties"));
              String driver = properties.getProperty("jdbc.driver");
              String jdbc_url = properties.getProperty("jdbc.url");
              String username = properties.getProperty("jdbc.username");
              String password = properties.getProperty("jdbc.password");
              Class.forName(driver);
              connection = DriverManager.getConnection(jdbc_url, username, password);
              JasperRunManager.runReportToPdfStream(reportStream, servletOutputStream, parameterMap, connection);
              //byte[] reports = JasperRunManager.runReportToPdf(reportStream, parameterMap, connection);
              connection.close();
              response.setContentType("application/pdf");
              servletOutputStream.flush();
              servletOutputStream.close();
              catch(Exception e)
                   log.error("exception message:"+e.getMessage());
              return "success";
         }

    There is a forum dedicated to JasperReports and you might find help there..
    http://jasperforge.org/plugins/espforum/browse.php?group_id=102&forumid=103
    Also don't forget to use tags because they make it easier for others to read your posts.
    Finally, I suggest moving all of your database access code into a separate class.  It will help you write code that is easier to maintain.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

Maybe you are looking for