Error deploying JDBC driver for SQL Server 2005

Hi all
I'm trying to deploy a JDBC driver for MS SQL Server 2005 (downloaded [here|http://www.microsoft.com/downloads/details.aspx?familyid=C47053EB-3B64-4794-950D-81E1EC91C1BA&displaylang=en]). When I try to deploy it according to the instructions found [here|http://help.sap.com/saphelp_nwce10/helpdata/en/51/735d4217139041e10000000a1550b0/frameset.htm] it fails.
The error in the logs doesn't give any useful information though. It only says Error occurred while deploying component ".\temp\dbpool\MSSQL2005.sda".
Has anyone else deployed a driver for SQL Server 2005, or perhaps have any suggestions of what else I could try?
Thanks
Stuart

Hi Vladimir
That's excellent news! Thanks for the effort you've put into this. I'm very impressed with how seriously these issues are dealt with, specifically within the Java EE aspects of SAP.
May I make two suggestions on this topic:
1. Given that NWA has such granular security permissions, please could the security error be shown when it is raised? This would help immediately identify that the problem isn't actually a product error, but rather a missing security permission (and thus save us time and reduce your support calls).
2. Please could the role permissions be clearly documented (perhaps they already are, and I just couldn't find the docs?) so we know what is and isn't included in the role. The name is very misleading, as a "superadmin" is generally understood to have no limitation on their rights - so clear documentation on what is in-/excluded would be most helpful.
On a related topic, I came across another issue like this that may warrant your attention (while you're already looking into NWA security issues). I logged a support query about it (ref: 0120025231 0000753421 2008) in case you can retrieve details there (screenshots, logs, etc.). It's basically a similar security constraint when trying to create a Destination. I'm not sure if this is something you would like to include as standard permissions within the NWA_SUPERADMIN role or not, but I think it's worth consideration.
Thanks again for your help!
Cheers
Stuart

Similar Messages

  • Deploy JDBC driver for SQL server 2005 on PI 7.1

    How to deploy JDBC driver for SQL server 2005 on PI 7.1
    We are in SAP NetWeaver 7.1 Oracle 10G
    Third party system is  SQL server 2005
    There are different JDBC versions are available to download for SQL server 2005.
    I am not sure about the applicable version for the PI 7.1 SP level. Again JMS Adapter needs to be deploy along with this.
    Please help

    Hi,
    Hope this How to Guide help you.
    How To Install and Configure External Drivers for the JDBC & JMS Adapters from
    www.sdn.sap.com/irj/sdn/howtoguides
    Regards,
    Karthick.
    Edited by: Karthick Srinivasan on Apr 13, 2009 4:07 PM

  • Deploying JDBC driver for SQL Server 2005 on PI 7.1

    How to Deploy JDBC driver for SQL Server 2005 on PI 7.1 on Windows 2003 server
    We are in NW PI 7.1 and third party db is sql server 05.
    Found How-to Guide SAP NetWeaver u201804 but unable to find for NW PI 7.1
    Can any one help me on this? (looking for guide step by step procedure)
    Regards
    Mahesh

    Hi,
    Check these:
    Re: Installing JDBC Drivers for PI 7.1
    how to deploy MS Sql Server 2005 and 2008 jdbc driver
    Mention of a SAP Note in the first link or refer this note [831162|https://service.sap.com/sap/support/notes/831162]
    Regards,
    Abhishek.

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

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

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

  • JDBC driver for SQL Server Compact Edition

    Hi,
    I'm trying to run pc java application on Pocket Pc (Mobile 5.0) with SQL Server Compact edition.
    The error message is:
    java.lang.UnsatisfiedLinkError: java/sql/DriverManager.getCallerClassLoader()Ljava/lang/ClassLoader;
    at java.sql.DriverManager.getConnection(Unknown Source)...
    Should I use a special jdbc driver for SQL Server Compact Edition? Is there one?
    Mixxo

    Hi,
    I got an answer from msdn forum:
    http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2307542&SiteID=1.
    There is no jdbc driver for SQL Server Compact Edition. OleDB and ADO.net are available. Now I need to know how to use them (in Java)...
    Thanks, Mixxo

  • JDBC Driver for SQL Server 7

    Is there a free JDBC Driver for SQL Server 7 available? If so, where? I created a server program that listens to a port and inserts records based on information it receives. It uses sun's JDBC:ODBC Bridge but it crashes randomly (sometimes weeks, sometimes days, sometimes hours after starting program). Each time it crashes it generates a error log file like this:
    An unexpected exception has been detected in native code outside the VM.
    Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x77f821e1
    Function name=RtlEnterCriticalSection
    Library=C:\WINNT\System32\ntdll.dll
    Current Java thread:
         at sun.jdbc.odbc.JdbcOdbc.driverConnect(Native Method)
         at sun.jdbc.odbc.JdbcOdbc.SQLDriverConnect(Unknown Source)
         at sun.jdbc.odbc.JdbcOdbcConnection.initialize(Unknown Source)
         at sun.jdbc.odbc.JdbcOdbcDriver.connect(Unknown Source)
         at java.sql.DriverManager.getConnection(Unknown Source)
         at java.sql.DriverManager.getConnection(Unknown Source)
         at com.xxxxx.data.DataAccess.connect(DataAccess.java:20)
         at com.xxxxx.xxx.server.Broadcaster.insertOrder(POSServer.java:71)
         at com.xxxxx.xxx.server.ClientListener.run(POSServer.java:298)
    Dynamic libraries:
    0x00400000 - 0x00405000      C:\WINNT\system32\java.exe
    0x77F80000 - 0x77FFB000      C:\WINNT\System32\ntdll.dll
    0x77DB0000 - 0x77E0C000      C:\WINNT\system32\ADVAPI32.dll
    0x77E80000 - 0x77F35000      C:\WINNT\system32\KERNEL32.DLL
    0x77D40000 - 0x77DB0000      C:\WINNT\system32\RPCRT4.DLL
    0x78000000 - 0x78046000      C:\WINNT\system32\MSVCRT.dll
    0x6D420000 - 0x6D4F0000      C:\Program Files\JavaSoft\JRE\1.3.1_02\bin\hotspot\jvm.dll
    Local Time = Mon May 06 10:36:33 2002
    Elapsed Time = 124
    # The exception above was detected in native code outside the VM
    # Java VM: Java HotSpot(TM) Client VM (1.3.1_02-b02 mixed mode)
    Or this:
    An unexpected exception has been detected in native code outside the VM.
    Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x77f821e1
    Function name=RtlEnterCriticalSection
    Library=C:\WINNT\System32\ntdll.dll
    Current Java thread:
         at sun.jdbc.odbc.JdbcOdbc.freeConnect(Native Method)
         at sun.jdbc.odbc.JdbcOdbc.SQLFreeConnect(Unknown Source)
         at sun.jdbc.odbc.JdbcOdbcDriver.closeConnection(Unknown Source)
         at sun.jdbc.odbc.JdbcOdbcConnection.close(Unknown Source)
         at sun.jdbc.odbc.JdbcOdbcConnection.finalize(Unknown Source)
         at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
         at java.lang.ref.Finalizer.runFinalizer(Unknown Source)
         at java.lang.ref.Finalizer.access$100(Unknown Source)
         at java.lang.ref.Finalizer$FinalizerThread.run(Unknown Source)
    Dynamic libraries:
    0x00400000 - 0x00405000      C:\Program Files\JavaSoft\JRE\1.3.1_02\bin\javaw.exe
    0x77F80000 - 0x77FFB000      C:\WINNT\System32\ntdll.dll
    0x77DB0000 - 0x77E0C000      C:\WINNT\system32\ADVAPI32.dll
    0x77E80000 - 0x77F35000      C:\WINNT\system32\KERNEL32.DLL
    0x77D40000 - 0x77DB0000      C:\WINNT\system32\RPCRT4.DLL
    Local Time = Mon May 06 10:13:59 2002
    Elapsed Time = 137
    # The exception above was detected in native code outside the VM
    # Java VM: Java HotSpot(TM) Client VM (1.3.1_02-b02 mixed mode)
    I think this error occurs because I'm using sun's JDBC:ODBC Bridge. I'm hoping that using a different driver will solve the problem.
    Thanks,
    Dan

    I used Sun's jdbc odbc driver for a while, with no problems, with Sql Server 7. But anyways, if you want a free type 4 driver, you can get the freetds driver at
    https://sourceforge.net/projects/jtds/

  • Using JSP & JDBC driver for SQL Server 2000 on Red Hat

    I successfully have a .jsp app running on windows server 2000 using JDBC
    driver for SQL Server 2000. Which I installed in order to the following
    Red Hat:
    http://msdn.microsoft.com/MSDN-FILES/027/001/779/install.htm
    I moved the .jsp app over to the Red Hat 9 server running Tomcat, while
    keeping the MS SQL 2000 on windows. The issue I have is setting up the
    JDBC driver for SQL Server 2000 on the Red Hat server.
    I created a folder called /usr/java/MSSQLdriver and unzipped the tar file with
    the driver for SQL Server 2000. And ran the install.ksh script.
    The /usr/java/MSSQLdriver/lib has the following files within it:
    msbase.jar, msutil.jar, & mssqlserver.jar
    I chmod 0777 each of the *.jar files.
    I then went into /etc/profile.d/tomcat.sh and adding the following:
    CLASSPATH=.;/opt/msSQLjdbc/lib/msbase.jar;/opt/msSQLjdbc/lib/msutil.jar;/opt/msSQLjdbc/lib/mssqlserver.jar
    Each time I login and pull up the termial I get the following error:
    bash: /opt/msSQLjdbc/lib/msbase.jar: cannot execute binary file
    bash: /opt/msSQLjdbc/lib/msutil.jar: cannot execute binary file
    bash: /opt/msSQLjdbc/lib/mssqlserver.jar: cannot execute binary file
    And can't connnect to the database within the .jsp app.
    Is there anyone out there using DBC driver for SQL Server 2000 on the Red Hat server?
    Michael

    Sorry, I needed to correct some information of where the drivers were installed.
    I created a folder called /usr/java/MSSQLdriver/new and untar the Microsoft file with the driver for SQL Server 2000. I ran the install.ksh script "sh install.ksh"
    installed the driver into the default directory "/opt/msSQLjdbc".
    The /opt/msSQLjdbc/lib has the following files within it:
    msbase.jar, msutil.jar, & mssqlserver.jar
    Michael

  • Microsoft Jdbc driver for SQL Server memory leak

    I'm using Microsoft Jdbc driver and see there's some leak after running application for a while. I'm sure that it's from Jdbc driver because I sitch to Jtds and the issue went away. My question is is there anybody knows which web sites talk about memory leak issue in Microsoft Jdbc driver for SQL Server?
    Appreciate your help

    I'm using Microsoft Jdbc driver and see there's some leak after running application for a while. I'm sure that it's from Jdbc driver because I sitch to Jtds and the issue went away. My question is is there anybody knows which web sites talk about memory leak issue in Microsoft Jdbc driver for SQL Server?
    Appreciate your help

  • JDBC driver for SQL Server

    Does anyone know of a JDBC driver for SQL Server 2000 that supports Windows Authentication?
    Meaning a username and password does not need to be supplied when connecting to the database.
    Thanks,
    James.

    Yes.
    JDBC-ODBC.

  • JDBC driver for SQL Server 2000 with windows authentication

    Does anyone know of a JDBC driver for SQL Server 2000 that supports Windows Authentication, that is that a username and password does not need to be supplied when connecting to the database.

    You can use the JDBC-ODBC-Bridge.
    ODBC provides windows-authentication.
    Hope it helps.
    Freddy

  • JDBC Connectivity for SQL Server 2005 Windows Authentication Mode

    Hi Everyone,
    In my Scenario we are using SQL Server 2005 with Mixed Mode Authentication. Now we are planning to move only with Windows Authentication Mode.
    We have configured DB with Window authentication mode & user id have been configured in PI channels however we are getting error. We checked microsoft site, which says Windows Authentication mode DB can not be connected using JDBC drivers.
    http://support.microsoft.com/kb/313100
    In this above link see Basic Connectivity Troubleshooting Section.
    Please let me know if someone confirued JDBC Channel Successfuly with Windows Authentication Mode.
    Thanks In Advance
    Regards,
    Bharathi.

    I think this issue is related to the way that Vista, Windows 7 and Windows 2008 / 2008 R2 treat users who are logged on to the system with an account that is a member of the local administrators group when SQL is running locally.
    If your SQL setup has left you with BUILTIN\Administrators being a member of the sysadmin server role and you start up SQL Management Studio you'd expect to be mapped to the sysadmin role if your user account is in the local administrators group, however
    these OS disable this ability and when you try to connect to the database engine SQL server doesn't know you are a member of the local administrators group.
    To get round this, close all your open SQL management studio windows and then start a new window by right clicking the icon in the start menu and chosing to run as administrator. This time when you try to connect to the SQL database engine, windows doesn't
    "hide" the fact that you are an administrator. If you need to do this a lot you can go to the compatibility tab on the properties of the shortcut and set it to always run as administrator.
    Alternatively you can install the admin tools remotely and you don't get this effect.
    Tim

  • Test JDBC Driver For SQL Server 2000 Failed

    Hi:
    I have trouble setting up the database connection using jdbc driver in the studio, could anyone help me please? I have MS SQL 2000 MSDE installed on my local machine. I downloaded and installed the JDBC Driver for MSSQL 2000 from Microsoft.
    I put the following jar files into the/lib/ext/ directory
    msbase.jar
    mssqlserver.jar
    msutil.jar
    In Studio 4.1 EE, I went to Runtime>Databases>Drivers, Add a new Driver with these information:
    Name: MSSQL Driver
    Driver: com.microsoft.jdbcx.sqlserver.SQLServerDataSource
    URL Prefix: jdbc:microsoft:sqlserver://localhost:<PORT>[;DatabaseName=<DB>]
    Next I run the Test Driver...
    Database URL: jdbc:microsoft:sqlserver://<machineName>\\<instanceName>;DatabaseName=<xxx>
    User: <username>
    Password: <password>
    I receieved the a popup box and message in the output window:
    Internal test driver incomplete. the driver may not support the required DatabaseMetadata methods. take a look at the Output Window for details.
    Warning: No tables were found. Check your database.
    Warning: No views were found. Check your database
    Warning: No procedures were found. Check your database.
    Your replies are greatly appreciated.
    Perry

    com.microsoft.jdbcx.sqlserver.SQLServerDataSource is a very old direct driver. I'd recommend using the DataDirect 3.2 driver. It can be found at:
    http://www.datadirect-technologies.com/products/jdbc/jdbcindex.asp

  • Microsoft jdbc driver for sql server 2000 error

    I try to connect to a sql server database;
    After execution of:
    C:\Sun\Creator\bin\runide.exe -cp:a =.;"C:\Programmi\Microsoft SQL Server 2000 Driver for JDBC\lib\msbase.jar";"C:\Programmi\Microsoft SQL Server 2000 Driver for JDBC\lib\msutil.jar";"C:\Programmi\Microsoft SQL Server 2000 Driver for JDBC\lib\mssqlserver.jar"
    (where "programmi" is "Program Files" in Italian)
    I can make a connection to sql server.
    When I try to see the "tables" in database I have this error:
    [Microsoft][SQLServer 2000 Driver for JDBC]Error setting up static cursor cache
    I have tryed to found some resolution and I found only this:
    http://forum.java.sun.com/thread.jsp?thread=444136&forum=48&message=2007122
    Can you see if it apply on source of IDE and eventually correct?

    I'm using the new version and I can't update a row
    satRowSet.setDataSourceName("java:comp/env/jdbc/Northwind");
    satRowSet.setCommand("SELECT * FROM dbo.Sat");
    satModel.setWrappedData(satRowSet);
    satRowSet.setConcurrency(java.sql.ResultSet.CONCUR_UPDATABLE);
    satRowSet.setHoldability(java.sql.ResultSet.HOLD_CURSORS_OVER_COMMIT);
    satRowSet.setAutoCommit(true);
    satRowSet.setReadOnly(false);
    satRowSet.execute();
    satRowSet.next();
    try{
    this.satRowSet.absolute(1);
    this.satRowSet.updateRow();
    } catch (Exception ex) {
    this.textArea1.setValue(ex.getMessage());
    ex.printStackTrace();
    java.sql.SQLException: [Sun][SQLServer JDBC Driver]Invalid operation for the current cursor position.
         at com.sun.sql.jdbc.base.BaseExceptions.createException(Unknown Source)
         at com.sun.sql.jdbc.base.BaseExceptions.getException(Unknown Source)
         at com.sun.sql.jdbc.base.BaseResultSet.validateCursorPosition(Unknown Source)
         at com.sun.sql.jdbc.base.BaseResultSet.getString(Unknown Source)
         at com.sun.sql.rowset.JdbcRowSetXImpl.getString(JdbcRowSetXImpl.java:842)
         at com.sun.sql.rowset.JdbcRowSetXImpl.getString(JdbcRowSetXImpl.java:941)
         at untitled.Page1.setFields(Page1.java:133)
         at untitled.Page1.beforeRenderResponse(Page1.java:147)
         at com.sun.jsfcl.app.FacesBean.beforePhase(FacesBean.java:227)
         at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:192)
         at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
         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 org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:289)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
         at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:311)
         at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:205)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:283)
         at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:102)
         at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:192)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
         at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:261)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:215)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:191)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:180)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:582)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
         at com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
         at com.sun.enterprise.security.web.SingleSignOn.invoke(SingleSignOn.java:254)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
         at com.sun.enterprise.web.VirtualServerValve.invoke(VirtualServerValve.java:209)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:161)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
         at com.sun.enterprise.web.VirtualServerMappingValve.invoke(VirtualServerMappingValve.java:166)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:979)
         at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:211)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:692)
         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:647)
         at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:589)
         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:691)
         at java.lang.Thread.run(Thread.java:534)

  • Add microsoft's jdbc driver for sql server 2000  to wls6.1 appear error!

    Hi,
    According to wls's guide,I modify wls's start script(startWeblogic.bat),add
    jdbc driver path to CLASSPATH,
    Howere,I create connect pool,Erorr report:
    No suitable driver find!
    This show jdbc driver isn't at System classpath.
    So , how do I??
    regds
    tks

    set WL_HOME=f:\java\bea\weblogic6.1
    set
    CLASSPATH=%WL_HOME%\server\ext\jdbc\sqlserver\msutil.jar;%WL_HOME%\server\ex
    t\jdbc\sqlserver\mssqlserver.jar;%WL_HOME%\server\ext\jdbc\sqlserver\msbase.
    jar;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar;%
    CLASSPATH%
    "Sree Bodapati" <[email protected]> дÈëÏûÏ¢ÐÂÎÅ
    :[email protected]..
    Can you show me the CLASSPATH you are using?
    sree
    "simon" <[email protected]> wrote in message
    news:[email protected]..
    Hi,
    According to wls's guide,I modify wls's startscript(startWeblogic.bat),add
    jdbc driver path to CLASSPATH,
    Howere,I create connect pool,Erorr report:
    No suitable driver find!
    This show jdbc driver isn't at System classpath.
    So , how do I??
    regds
    tks

  • Porblem loading Microsoft JDBC Driver for SQL Server

    Hi all !!
    Well, it seems there is a naming problem for the MS Driver, when Netbeans creates server resources for the Connection Pool and the DataSource, the default name for the connection pool's datasource classname is com.microsoft.jdbc.sqlserver.SQLServerDataSource, but the actual name of the class within the driver's jar is com.microsoft.jdbcx.sqlserver.SQLServerDataSource, note the 'x' after jdbc.
    I changed this and the resource is created correctly (from the admin console, it pings to the DB server), but when I try to deploy the project, I get this error:
    RAR5038:Unexpected exception while creating resource
    RAR5117 : Failed to obtain/create connection. Reason : Class name is wrong or classpath is not set for : com.microsoft.jdbc.sqlserver.SQLServerDataSource
    RAR5114 : Error allocating connection : [Error in allocating a connection. Cause: Class name is wrong or classpath is not set for : com.microsoft.jdbc.sqlserver.SQLServerDataSource]
    WebModule[WebApplication2]java.sql.SQLException: Error in allocating a connection. Cause: Class name is wrong or classpath is not set for : com.microsoft.jdbc.sqlserver.SQLServerDataSource
    java.lang.RuntimeException: java.sql.SQLException: Error in allocating a connection. Cause: Class name is wrong or classpath is not set for : com.microsoft.jdbc.sqlserver.SQLServerDataSource
    I guess I must change the name of the classname in some other place, but I searched the admin colsole and Netbeans and failed to find where it should be.
    I'm using Netbeans 5.5 and SQL Server 200 with the MS JDBC Driver sp 3.
    Thanks in advance,
    Daniel

    Thanks for your answer !!
    Yes, the datasource classname is correct in domains.xml.
    I had the driver files copied into Appserver/lib, now I placed them also where you suggested me and restarted the server.
    Now I get a different error:
    LDR5202:Exception in EJBClassLoader
    java.io.IOException: The filename, directory or volume label are not valid:
    at java.io.WinNTFileSystem.canonicalize0(Native Method)
    at java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:396)
    at java.io.File.getCanonicalPath(File.java:559)
    at com.sun.enterprise.loader.EJBClassLoader$1.run(EJBClassLoader.java:418)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sun.enterprise.loader.EJBClassLoader.findResource0(EJBClassLoader.java:391)
    at com.sun.enterprise.loader.EJBClassLoader.findResource(EJBClassLoader.java:467)
    at java.lang.ClassLoader.getResource(ClassLoader.java:977)
    at java.lang.ClassLoader.getResource(ClassLoader.java:972)
    at java.lang.ClassLoader.getResourceAsStream(ClassLoader.java:1159)
    at com.sun.enterprise.loader.EJBClassLoader.getResourceAsStream(EJBClassLoader.java:782)
    at com.sun.xml.rpc.spi.JaxRpcObjectFactory.newInstance(JaxRpcObjectFactory.java:131)
    at com.sun.enterprise.webservice.codegen.JaxRpcRICodegen.<init>(JaxRpcRICodegen.java:120)
    at com.sun.enterprise.webservice.codegen.JaxRpcCodegenFactory.getAdapter(JaxRpcCodegenFactory.java:50)
    at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:839)
    at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:580)
    at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployModule(EJBCompiler.java:413)
    at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:226)
    at com.sun.enterprise.deployment.backend.ModuleDeployer.runEJBC(ModuleDeployer.java:1189)
    at com.sun.enterprise.deployment.backend.WebModuleDeployer.deploy(WebModuleDeployer.java:179)
    at com.sun.enterprise.deployment.backend.ModuleDeployer.doRequestFinish(ModuleDeployer.java:160)
    at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:169)
    at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:95)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:871)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:266)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:739)
    at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:174)
    at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:210)
    I guess it may have something to do with any of the classpathes, there is a system or environment CP, one for the App server (with prefixes, suffixes, etc, and there is another in the Netbeans IDE tools Options....
    I also tried to debug into java.io.WinNTFileSystem.canonicalize0(Native Method) just to see the name of the file who raised the exception, but I couldn't attach the BPEL debugger, it gives me this error:
    11:57:24 Connecting to localhost:3343
    11:57:24 Unable to start a debug session : Unable to connect to localhost:3343 : Connection refused: connect
    I'm using a proxy but the system settings are set to not use the proxy for localhost addresses and so is netbeans.
    How much I miss the simplicity of the old Turbo Pascal days !!
    Thanks for your help !!
    Daniel

Maybe you are looking for