Urgent ****Error in Microsoft JDBC drivers:****

hi Guys,
I am getting the following error when I am trying to execute the query:
'Select getDate()'
getDate is a function which returns the system date. The query works perfectly fine when run from query analyser and most of the times from within the application as well. But some times it throws the following error. I am having multiple threads executing the above query.
It seems to be a bug in the driver. Any idea/workaround ???
I am using jdk 1.3.1 and SQL Server 2000
cheers,
java.lang.NullPointerException
     at com.microsoft.jdbc.base.BaseImplStaticCursorResultSet.setupTempFiles(Unknown Source)
     at com.microsoft.jdbc.base.BaseImplStaticCursorResultSet.<init>(Unknown Source)
     at com.microsoft.jdbc.base.BaseStatement.chainInServiceImplResultSets(Unknown Source)
     at com.microsoft.jdbc.base.BaseStatement.getNextResultSet(Unknown Source)
     at com.microsoft.jdbc.base.BaseStatement.commonGetNextResultSet(Unknown Source)
     at com.microsoft.jdbc.base.BaseStatement.executeQueryInternal(Unknown Source)
     at com.microsoft.jdbc.base.BaseStatement.executeQuery(Unknown Source)
     at com.sanderson.tallyman.util.TallymanDB.executeQuery(Unknown Source)
     at com.sanderson.tallyman.util.TallymanDB.getCurrentDate(Unknown Source)
     at com.sanderson.tallyman.operations.interfaces.RecordUpdateControl.updateRecord(Unknown Source)
     at com.sanderson.tallyman.operations.interfaces.DebtInterfaceControl.processUpdate(Unknown Source)
     at com.sanderson.tallyman.operations.interfaces.DebtInterfaceControl.processInterface(Unknown Source)
     at com.sanderson.tallyman.operations.interfaces.InterfaceHandler$ProcessRecord.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)

>
It seems to be a bug in the driver. Any
idea/workaround ???
My first idea would be that it is very likely that is has nothing to do with the driver and the problem is in your code.
If you have reduced this to a simple test case that clearly demonstrates that it isn't your code, but is the driver, then post it here.

Similar Messages

  • *****Error in Microsoft JDBC drivers for SQL Server 2000****

    hi guys,
    I am getting the following error in my application. The error seems to have thrown by Microsoft JDBC drivers for SQL Server 2000
    The application tries to execute the the following query when the error is thorwn:
    SELECT getDate(); // getDate is a function which returns currebt date time. The error is thrown occassionally. Other times the same query is executed correctly by the application.
    Can any one help with this one.
    The error is:
    java.lang.NullPointerException
         at com.microsoft.jdbc.base.BaseImplStaticCursorResultSet.setupTempFiles(Unknown Source)
         at com.microsoft.jdbc.base.BaseImplStaticCursorResultSet.<init>(Unknown Source)
         at com.microsoft.jdbc.base.BaseStatement.chainInServiceImplResultSets(Unknown Source)
         at com.microsoft.jdbc.base.BaseStatement.getNextResultSet(Unknown Source)
         at com.microsoft.jdbc.base.BaseStatement.commonGetNextResultSet(Unknown Source)
         at com.microsoft.jdbc.base.BaseStatement.executeQueryInternal(Unknown Source)
         at com.microsoft.jdbc.base.BaseStatement.executeQuery(Unknown Source)
         at com.sanderson.tallyman.util.TallymanDB.executeQuery(Unknown Source)
         at com.sanderson.tallyman.util.TallymanDB.getCurrentDate(Unknown Source)
         at com.sanderson.tallyman.operations.interfaces.RecordUpdateControl.updateRecord(Unknown Source)
         at com.sanderson.tallyman.operations.interfaces.DebtInterfaceControl.processUpdate(Unknown Source)
         at com.sanderson.tallyman.operations.interfaces.DebtInterfaceControl.processInterface(Unknown Source)
         at com.sanderson.tallyman.operations.interfaces.InterfaceHandler$ProcessRecord.run(Unknown Source)
         at java.lang.Thread.run(Unknown Source)
    rgds,

    Hi,
    Did you ever get an answer to this? I am also having this problem.

  • Error with Download JDBC Drivers page

    There appears to be an error with the JDBC Drivers download page. When navigating from the top-level download page, all I'm seeing is '<SCRIPT LANGUAGE="javascri'. Is there another page from which I can download the driver?
    Guy Heathcote
    Ordnance Survey
    UK

    The 10g and later drivers trade memory for performance. They use much more memory than the 9i drivers, but are much faster. If you look at the JDBC FAQ here on OTN there is some more info on where the memory is going. The stack trace you posted is what I would expect to see from buffer allocation described in the FAQ.
    Douglas

  • Error when using JDBC drivers

    Hi ..
    We have successfully deployed the JDBC drivers but in RWB(Communication channel monitoring) ,when executing we are getting an error
    Received XI System Error. ErrorCode: EXCHANGE_PROFILE_ACCESS ErrorText:   ErrorStack: Error while reading exchange profile for system PI7 and client 001
    2006-12-05 12:33:25 Error Transmitting the message to endpoint http://sap1:8001/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: EXCHANGE_PROFILE_ACCESS:.
    <b></b><i></i>
    Any suggestions
    Thanks
    Gopal
    Message was edited by:
            Gopal krishnan
    Message was edited by:
            Gopal krishnan

    Hi..
    I did it but here i am wondering becoz my RFC connection SAPSLDAPI works fine
    But at transaction SLDCHECK..it throws an error like
    Calling function LCR_LIST_BUSINESS_SYSTEMS
    Retrieving data from the SLD server...
    Function call returned exception code     4
    => Check whether the SLD is running!
    Summary: Connection to SLD does not work
    => Check SLD function and configurations
    But the SLD URL pops up and opens wih put any error.in a same fashion,it happens in SXMB_ADM--> integration engine config.it says connections to SLD doesnot work
    any idea to verify
    Thanks
    Gopal

  • Two Microsoft JDBC Drivers - WL is picking its own

    We want to use Microsoft's own version of JDBC, not WL's version.
    Currently WL is choosing it's own (mssqlserver4v65.jar) that's in ...bea\weblogic700\server\lib over the MS SQL Server one I thought I'd installed properly.
    Guess the question is: how do you install an additional MS SQL Server JDBC driver so when you call it in your Java code (jsp, bean, etc.) it uses the NEWLY installed one & not WL's own mssqlserver4v65.jar?
    1. How do you change the classpath? Do you change the system classpath as well as the WL classpath?
    2. Which folder does the NEW MS JDBC driver go in?
    3. Do you have to make a special reference to the NEW JDBC driver so WL doesn't use its own?
    Thanks!

    steve garrison wrote:
    We want to use Microsoft's own version of JDBC, not WL's version.
    Currently WL is choosing it's own (mssqlserver4v65.jar) that's in ...bea\weblogic700\server\libover the MS SQL Server one I thought I'd installed properly.
    That's very odd. That could only happen if the two drivers accpeted the same
    URL, but I don't think that's true. If you show me the pool definition I can
    help.
    Guess the question is: how do you install an additional MS SQL Server JDBC driverso when you call it in your Java code (jsp, bean, etc.) it uses the NEWLY installed
    one & not WL's own mssqlserver4v65.jar?
    If two drivers have the same Driver class name and accept the same URL, the one
    that comes first in the classpath will be the one used.
    1. How do you change the classpath? Do you change the system classpath as well as the WL classpath?
    Open the startWeblogic script and you will see how the classpath is formed for the
    execution line that starts weblogic.
    2. Which folder does the NEW MS JDBC driver go in?It doesn't matter as long as it's listed in the classpath the server uses.
    3. Do you have to make a special reference to the NEW JDBC driver so WL doesn't use its own?Typically the pool just needs the driver's class name (which is different for all different
    vendor's drivers), and the URL that driver takes (which except for very rare cases is
    also different for different drivers).
    As a last resort you can always move/remove drivers that you don't want to use. However,
    do show your pool definition and we'll solve this.
    Joe
    Thanks!

  • Could not find Microsoft JDBC Driver ???

    Hi all,
    My program could not find the JDBC driver. Why?????
    Here is my environment:
    Platform: Win2000
    Database: Sql2000
    Tool: JBuilder enterprise (trial version)
    JDBC Driver: Microsoft JDBC driver for SQL Server 2000
    I set the CLASSPATH=.;D:\Sql200JDBCDriver\lib\msbase.jar;D:\Sql200JDBCDriver\lib\msutil.jar;D:\Sql200JDBCDriver\lib\mssqlserver.jar
    Here is my javabean:
    package test;
    import java.sql.*;
    import java.io.*;
    public class LoginBean{
    public static boolean login(String strUser, String strPass)     {
    ResultSet rs;
    try{
    System.out.println("before class.forName");//Print trapped error.
    Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
    System.out.println("After class.forName");//Print trapped error.
    java.sql.Connection theConnection = DriverManager.getConnection("jdbc:microsoft:sqlserver://localhost:8080;DataBaseName ='MyDataBase;User=sa;passowrd="); //Connect to db
    System.out.println("After get connection");//Print trapped error.
    Statement theStatement=theConnection.createStatement();
    rs=theStatement.executeQuery("SELECT username, password FROM login WHERE username= '" + strUser + "' AND password= '" + strPass + "'");
    if(rs.next()) //Fetch username of record
    return true;
    }catch(Exception e){
    System.out.println("before e.getMessage error");//Print trapped error.
    System.out.println(e.getMessage());//Print trapped error.
    System.out.println("after e.getMessage error");//Print trapped error.
    } return false;
    Here are the messages I got:
    before class.forName
    before e.getMessage error
    com.microsoft.jdbc.sqlserver.SQLServerDriver
    after e.getMessage error.
    The program never got throught the statement: Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
    What's wrong?????
    thanks in advanced.

    I guess you have a good idea what the problem is. Either the class name you have specified is wrong or the required library is not on the classpath.
    How are you setting the classpath? Are you running your application through JBuilder or through the command line?
    If it's through JBuilder then make sure that you've configured one of their tiresome "Libraries" and that your project has it in its "Required Libraries".
    Never rely on environment variables to supply the classpath - it takes very little effort to set up a classpath for each application you're developing and will ensure you're using the versions of each library that you want to. Personally I make sure I delete the classpath environment variable so there's nothing implicit hiding away.
    Hope this helps.

  • Microsoft JDBC SQL Server Drivers

    I want to use the Microsoft JDBC SQL Server Drivers. I know they are not supported.
    What do I need to do to my 9iAS install so that my reports can use this JDBC connection.
    I have 5 simple reports I want to run from a very simnple menu. I want to hide the JDBC connection in the URL. But I want the report to use the URL to connect to a MS SQL Server 200 database and generate a report that was created using Reports Builder.
    Obviosly I am new to all of this. And someone else is doing the 9iAS install.
    What do I need to do to get this going?
    Thanks for any help.
    Jeanne

    I am now using mth Merant SQL Server JDBC Driver.
    But I still get the following error when running from the URL from my local OC4J.
    I have added classpath of YM*.jar files to rwEng and rwUrlEng in rep_<myserver>.conf.
    Why can't it find the drivers?
    Thanks.
    Reports Error Page
    Wed May 28 10:08:52 PDT 2003
    javax.servlet.jsp.JspException: rwlib-1: REP-4100: Failed to execute data source. JDBCPDS-62008:com.oracle.ias.jdbc.sqlserver.SQLServerDriver
    javax.servlet.jsp.JspException: rwlib-1: REP-4100: Failed to execute data source.
    JDBCPDS-62008:com.oracle.ias.jdbc.sqlserver.SQLServerDriver
    at oracle.reports.jsp.ObjectsTag.doEndTag(ObjectsTag.java:180)
    at test.WLBNTemp._jspService(_WLBNTemp.java:85)
    at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
    at oracle.jsp.runtimev2.JspPageTable.compileAndServe(JspPageTable.java:508)
    at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:255)
    at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:407)
    at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:330)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:336)
    at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:59)
    at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:283)
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:523)
    at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:269)
    at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:735)
    at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:243)
    at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:64)

  • Microsoft jdbc driver class not found error

    hello,
    i have installed jdbc driver for 2005 from microsoft. i have put sqljdbc.jar in the classpath as well as in jbuilder 2006 library. still i get the following error.
    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:306)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:164)
    at dbinfo.dbinfo.getConnection(dbinfo.java:27)
    at dbinfo.dbinfo.displayDbProperties(dbinfo.java:64)
    at dbinfo.dbinfo.main(dbinfo.java:150)
    Error Trace in getConnection() : com.microsoft.jdbc.sqlserver.SQLServerDriver
    Error: No active Connection
    what am i missing?

    i have the same problem can anyone help me in setting the classpath to the drivers. i am new to java plz help me
    thanks in advance

  • Microsoft SQL Server JDBC Drivers 4.0.2206 timeout on first connection to SQL Server Express after it sleeps

    Our builds kick off and run integration tests. They are configured to hit a SQL Server Express server.
    If the builds have been quiet for a while, the first test to connect fails after stalling for 20 minutes.
    Subsequent tests are fine.
    Reversing test order does the same thing, with a different test.
    We noticed in the SQL Server express log the server saying it is waking up after being idle.
    Microsoft SQL Server Express with Microsoft SQL Server JDBC Drivers 4.0.2206.
    Connection times out after 20 minutes.Occurs with the first connection made after the SQL Server Express server wakes up from going to sleep.Connections after the first are just fine, until SQL Server Express sleeps.SSL enabled. Timeout duration for the connection failure is unaffected by setting timeout options for the connection.  Work around:
    cron-like job that runs every minute that makes a simple query on the server keeps the server from going to sleep.
    Has anyone else run into this?

    Hello,
    SQL Server Express will go to sleep if idle, this behavior is not configurable.
    When SQL Express transitions from idle to active some of the memory that was released needs to be reclaimed; this results is a slight lag during "startup time" when you're first connecting to SQL Express.
    The other sort of sleep occurs when a database with AUTO_CLOSE unloading itself after a period of inactivity. This can be resolved by setting AUTO_CLOSE to false.
    You can refer to the following blog about more details about this:
    http://blogs.msdn.com/b/sqlexpress/archive/2008/02/22/sql-express-behaviors-idle-time-resources-usage-auto-close-and-user-instances.aspx
    You can try to upgrade the SQL Server Express to a non-free version to get rid of this.
    Regards,
    Fanny Liu
    Fanny Liu
    TechNet Community Support

  • Error in Sender JDBC communication channel

    Dear All,
    We have an interface in which we are fetching data from SQL database through sender JDBC communication channel.
    Last week SQL server was upgraded from 2000 to 2008 and the communication channel has stopped working and is giving the following error:
    Database-level error reported by JDBC driver while executing statement 'SELECT * FROM mstemp_tbl WHERE Active='0''. The JDBC driver returned the following error message: 'java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter 1 (""): Data type 0x38 is unknown.'. For details, contact your database server vendor.
    Please let me know if any JDBC drivers are to be installed for SQL 2008 or how can we resolve this.
    Thanks,
    NJ

    Hi,
    You may need to update your JDBC driver to 1.2 or 2.0. Kindly see supportability matrix on this link (question #2):
    http://msdn.microsoft.com/en-us/sqlserver/cc325721
    Regards,
    Jenny

  • Error in configuring JDBC Adapter

    Hi All,
    I have configured a sender JDBC Adapter with the following parameters.
    JDBC Drivers: com.microsoft.jdbc.sqlserver.SQLServerDriver
    Connection: jdbc:microsoft:sqlserver://MIS-SERVER\MIS_DEV_SVR;DatabaseName=SEPG_NEWDB
    But in Runtime, I am getting error as follows...
    Error during database connection to the database URL 'jdbc:microsoft:sqlserver://MIS-SERVER\MIS_DEV_SVR;DatabaseName=SEPG_NEWDB' using the JDBC driver 'com.microsoft.jdbc.sqlserver.SQLServerDriver': 'com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:microsoft:sqlserver://MIS-SERVER\MIS_DEV_SVR;DatabaseName=SEPG_NEWDB': SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]The requested instance is either invalid or not running.'
    It has been confirmed that JDBC Drivers are properly deployed.
    Any suggestions to resolve this issue?
    Regards
    Pavan

    Hi Pavan,
    I think Port is missing and also it should be look like this. (microsoft not required for SQL SERVER 2000).
    Make sure msbase.jar, msutil.jar, mssqlserver.jar are the driver files and deployment.
    Connection: jdbc:sqlserver://MIS-SERVER\MIS_DEV_SVR<b>:PORT</b>;DatabaseName=SEPG_NEWDB
    Regards,
    Sarvesh

  • Error at sender JDBC communication channel

    Dear All,
    While executing JDBC(MS-Access)-PI-RFC interface, we are getting error in sender JDBC communication channel. The error is as following:
    Error during database connection to the database URL 'jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=
    sappidev\Datatran\Database.mdb' using the JDBC driver 'jdbc.odbc.JdbcOdbcDriver': 'com.sap.aii.adapter.jdbc.sql.DriverManagerException: Can not establish connection:: SQLException: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified'.
    I have checked various posts on forums and as per those no drivers installation is required to access MS-Access database and I am not able to find any post which could solve my problem.
    Kindly guide me on what might be the problem and how this can be resolved.
    Regards,
    NJ

    Hi Nishu,
      That error ALWAYS means your DSN name is incorrect or can't be accessed for some reason (permission). The ODBC part says that the bridge is working.
      But that DSN is 100% wrong or cannot be seen by the user account that the server is running as. Make sure you have a system DSN and not a user one.
    You can refer these....
    http://bytes.com/topic/java/answers/625400-java-sql-sqlexception-microsoft-odbc-driver-manager-data-source-name-not-found
    http://www.daniweb.com/forums/thread13092.html#
    Hope this will help you....
    Regds,
    Pinangshuk.

  • Problem using production version of SQL Server 2005 JDBC drivers

    A production version of the Microsoft SQL Server 2005 JDBC driver became available on 1/20/06, and we are having some issues getting it to work with WLS 9.1. The non-XA driver works fine, but when we attempt to use the XA version, we see the error below in our logs. (Note that in the text "status:0 msg:null", the "null" is actually an unprintable character that I was not able to copy/paste.)
    We have successfully tested WLS 9.1 with the beta JDBC drivers that were released by Microsoft a number of months ago, so this appears to be a problem with the prod version only (although we had no trouble using the prod drivers with JBoss). We have actually opened a support case for this, but the response we have received thus far has been negligible at best and we really need to get this issue resolved, so I am posting the problem here as well to see if anyone else has encountered it.
    Regards,
    Sabrina
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
    Caused by: ourpackage.OurDBUtil.openConnection(OurDBUtil.java:130)     
         ... 11 more
    Caused by: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XA_OK start() failed on resource 'OurXADataSource': XA_OK
    javax.transaction.xa.XAException: java.sql.SQLException: Failed to create the XA control connection. Error: xp_sqljdbc_xa_init failure, status:0 msg:null.
         at com.microsoft.sqlserver.jdbc.SQLServerXAResource.start(Ljavax.transaction.xa.Xid;I)V(Unknown Source)
         at weblogic.jdbc.jta.DataSource.start(DataSource.java:679)
         at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1160)
         at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1093)
         at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:496)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:428)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1390)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1395)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1327)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
         ... 12 more

    SabrinaL wrote:
    A production version of the Microsoft SQL Server 2005 JDBC driver became available on 1/20/06, and we are having some issues getting it to work with WLS 9.1. The non-XA driver works fine, but when we attempt to use the XA version, we see the error below in our logs. (Note that in the text "status:0 msg:null", the "null" is actually an unprintable character that I was not able to copy/paste.)
    We have successfully tested WLS 9.1 with the beta JDBC drivers that were released by Microsoft a number of months ago, so this appears to be a problem with the prod version only (although we had no trouble using the prod drivers with JBoss). We have actually opened a support case for this, but the response we have received thus far has been negligible at best and we really need to get this issue resolved, so I am posting the problem here as well to see if anyone else has encountered it.
    Regards,
    SabrinaHi. Have you done all the XA-related install for the new MS driver? (put the XA
    dll in the DBMS environment etc)? Is your DBMS on a 32-bit machine or 64-bit machine?
    Does the driver present a dll for each of those? You can also get good JDBC help
    from MS via their microsoft.public.sqlserver.jdbcdriver newsgroup.
    Joe Weinstein at BEA
    >
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
    Caused by: ourpackage.OurDBUtil.openConnection(OurDBUtil.java:130)     
         ... 11 more
    Caused by: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XA_OK start() failed on resource 'OurXADataSource': XA_OK
    javax.transaction.xa.XAException: java.sql.SQLException: Failed to create the XA control connection. Error: xp_sqljdbc_xa_init failure, status:0 msg:null.
         at com.microsoft.sqlserver.jdbc.SQLServerXAResource.start(Ljavax.transaction.xa.Xid;I)V(Unknown Source)
         at weblogic.jdbc.jta.DataSource.start(DataSource.java:679)
         at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1160)
         at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1093)
         at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:496)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:428)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1390)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1395)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1327)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
         ... 12 more

  • SAPClassNotFoundException: com.microsoft.jdbc.sqlserver.SQLServerDriver

    Hi...Experts....
    Requirement:
    From our PI 7.1 System we have to connect to MS-SQL Server 2000 using JDBC.
    Execution :
    We have downloaded
    Microsoft SQL Server JDBC Driver 3.0 ...and...Microsoft SQL Server JDBC Driver 2.0 ( We mean we tried both drivers)and deployed using JSPM in PI system
    To deploy this ..We used & reviewed the following notes
    Note 0000831162 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 JDBC Adapter
    Note 0001138877 - PI 7.1 : How to Deploy External Drivers JDBC/JMS Adapters
    Note 0000850116 - XI 3.0 / PI 7.0 JDBC Adapter: Type 2 JDBC Driver Deployment
    Note 0001123333 - Redeploying same component with JSPM
    Issue Observation Path :
    in JSPM ...The deployment is successfull
    But in
    >Runtime Workbench NetWeaver Administrator
    >>Component Monitoring
    >>>Compnenet with status ..ALL...[DISPLAY]
    >>>Adapter Engine
    >>>>Communication Channel 
    We continuioulsy see the following error
    ERROR :
    Error during database connection to the database URL 'jdbc:microsoft:sqlserver://101.197.135.118:1433;databaseName=LWV' using the JDBC driver 'com.microsoft.jdbc.sqlserver.SQLServerDriver': 'com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:microsoft:sqlserver://101.197.135.118:1433;databaseName=LWV': SAPClassNotFoundException: com.microsoft.jdbc.sqlserver.SQLServerDriver'
    ERROR:
    In this Juncture...We have 2 queires.
    01. How to make the Deployed JDBC Driver avaialbiliy in the system.
    02. Any other alternate way to make sure our self deployed JDBC well installed in system and can be used from PI Console.
    Regards
    PR

    Imran ...Thank U Very much...
    We could able to move forward.
    as in Java Instance :
    In directory : DRIVE:\usr\sap\<SID>\DVEBMGS<NN>j2ee\cluster
    We can see : instance.properties
    We copied the  3 files  (01) sqljdbc4.jar, (02) msutil.jar, (03) msbase.jar  into a directory like
    DRIVE:\usr\sap\<SID>\DVEBMGS<NN>j2ee\cluster\bin\ext\com.sap.aii.adapter.lib\lib\
    In the "configtool"  we configured these 3 jar files in class path like :
    DRIVE:\usr\sap\<SID>\DVEBMGS<NN>j2ee\cluster\bin\ext\com.sap.aii.adapter.lib\lib\sqljdbc4.jar;
    DRIVE:\usr\sap\<SID>\DVEBMGS<NN>j2ee\cluster\bin\ext\com.sap.aii.adapter.lib\lib\msutil.jar;
    DRIVE:\usr\sap\<SID>\DVEBMGS<NN>j2ee\cluster\bin\ext\com.sap.aii.adapter.lib\lib\msbase.jar
    and restarted the Instance, which in turn updated the instance.properties
    and we could see the errors stopped coming in the "XI Runtime WorkBench - Component Monitoring"
    We could see as
    >>>Processing started
    >>>Processing finished successfully
    >>>Polling interval started. Length: 60.0 seconds
    So we understood, the connection could db server and we conformed we moved a head on the issue
    Summarized Notes List :
    Note 0000831162 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 JDBC Adapter
    Note 0001138877 - PI 7.1 : How to Deploy External Drivers JDBC/JMS Adapters
    Note 0000850116 - XI 3.0 / PI 7.0 JDBC Adapter: Type 2 JDBC Driver Deployment
    Note 0001123333 - Redeploying same component with JSPM
    Note 0000639702 - JDBC Driver for Microsoft SQL Server
    Rgds
    PR

  • JDBC drivers for SQL Server 2008 and PI7.0

    HI,
    I have deployed the JDBC drivers (sqljdbc.jar and sqljdbc4.jar) available for the SQL Server 2008 from the microsoft website as described in the how to document for deploying and configuring JDBC and JMS adapters.
    I am running a JDBC to FIle(XML) scenario. When I go and see on the RWB CC monitoring, I get this error
    Error during database connection to the database URL 'jdbc:sqlserver://hostname:1433;databaseName=123_Nagasatya' using the JDBC driver 'com.microsoft.sqlserver.jdbc.SQLServerDriver': 'com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:sqlserver://hostname:1433;databaseName=123_Nagasatya': UnsupportedClassVersionError: com/microsoft/sqlserver/jdbc/SQLServerDriver (Unsupported major.minor version 50.0)'
    WRT to the SQL server the port 1433  is open on the host and there is no firewall on the PI server as well as the SQL Server. Both are on different machines.Any help would be greatly appreciated.
    Regards.

    Hi Sujan,
    This is the link.
    [JDBC|http://www.microsoft.com/downloads/details.aspx?familyid=c47053eb-3b64-4794-950d-81e1ec91c1ba&displaylang=en]
                                          or
    You can also use the one on the market place.
    Go to http://service.sap.com/msplatforms -> SQL Server
    get zip-file sqljdbc_12_hotfix.zip contains the sqljdbc.jar file.
    It should work.
    Please let me know if you have any questions.
    Regards.

Maybe you are looking for