Deploying JDBC connector for SQL Server 2000

Hi All
We have a new MII 12.0.4 box installed with JDK 1.4_16. While trying to deploy SQL 2000 server JDBC driver after browsing to the (3 nos) *.jar file ,once i try to save it gives an error "DRIVE_NOT_UPLOADED"
Are there any other configs required to deploy a JDBC driver or permissions that we are missing.
Cheers

Does'nt help , any driver i try to upload it throws an error "DRIVER_NOT_UPLOADED" and when i check on the logs in the default trace error is :
com.sap.xmii.Illuminator.gui.handlers.JDBCDriverHandler#sap.com/xappsxmiiear#com.sap.xmii.Illuminator.gui.handlers.JDBCDriverHandler#Administrator#106##n/a#SAPEngine_Application_Thread[impl:3]_29##0#0#Error#1#/Applications/XMII#Plain###No files were uploaded in the multipart request#
I suspect some problem with the backend config...Any suggestions
Regards,
Rajeev

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.

*****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.

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

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

Are there any JDBC Drivers for SQL Server 2000?

Hello Everyone,
Any news on the JDBC drivers for SQL Server 2000? I know it is not
certified yet but is there a date when it will be.
Which versions of WLS will they work with? Any help is appreciated.
Sincerely,
--Luis

Hello Michael,
Any news on the JDBC drivers for SQL Server 2000? I know it is not
certified yet but is there a date when it will be.
Which versions of WLS will they work with? Any help is appreciated.
Sincerely,
--Luis
"Michael Girdley" <[email protected]> wrote in message
news:3a6549bb$[email protected]..
Not yet, but they will appear on the web site in about two weeks.
Thanks,
Michael
Michael Girdley, BEA Systems Inc
Learning WebLogic? Buy the book.
http://www.learnweblogic.com/
"Stefano Picozzi" <[email protected]> wrote in message
news:[email protected]..
Are there any JDBC Drivers for SQL Server 2000 for Weblogic Server.

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

JDBC connection for SQL Server 2000

How to connect SQL Server 2000 from java?
If i can get any sites where i can get examples also fine.
Thanks in advance
Praveen.

Developer's Daily Java Education
front page | java | perl | unix | DevDirectory
Front Page
Java
Education
Pure Java
   Articles
JDBC 101: How to connect to an SQL database with JDBC
Introduction
If you're interested in connecting your Java applets and applications to standard SQL databases like Oracle, Informix, Sybase, and others, JDBC is your ticket to paradise. The combination of Java's JDBC and standard SQL makes a simple and powerful database solution. JDBC makes the simple things easy -- without making the complex tasks too difficult either.
In this first article in our series, we'll show you step-by-step how to establish a connection from your Java programs to an SQL database using JDBC. In the process we'll show you how to connect to two different databases -- Mini SQL (mSQL), and Interbase -- just so you can see how the code changes when you switch from one database to another.
Obtaining the JDBC driver
Before you start working with JDBC, you'll need a copy of the Java JDK. If you don't have it already, you can get the JDK for free at Sun's Java web site, or it will also be included with many IDE's that you can purchase, such as JBuilder or Visual Cafe.
Once you have the JDK, the next thing you need to do is to get the correct JDBC driver for your database. In most cases the JDBC driver will be provided by your database vendor. For instance, if you purchase the Interbase database, the driver will be provided with the software, or you can obtain the most recent version at http://www.interbase.com/.
(An exception to this rule is Mini SQL, or mSQL. Because it's a very low-cost database, the JDBC driver has actually been developed by a separate group of people, led by George Reese at imaginary.com. You can download the mSQL JDBC driver from the imaginary.com web site.)
Once you have the correct JDBC driver for your database, install it according to the instructions that came with it. Installation instructions will vary somewhat for each vendor.
Establishing a connection is a two-step process
Once you have the correct JDBC driver installed, establishing a connection from your Java programs to your SQL database is pretty easy.
Regardless of whether you're trying to connect to Oracle, Sybase, Informix, mSQL, or Interbase (or any other JDBC data source), establishing a connection to an SQL database with Java JDBC is a simple two-step process:
Load the JDBC driver.
Establish the connection.
We'll show you two examples just so you can see how easy it is, and how little the code changes when you migrate from one database server to another.
A Mini SQL Example
Listing 1 provides the full source code required to establish a connection to a mSQL database on a server named "www.myserver.com".
// Establish a connection to a mSQL database using JDBC.
import java.sql.*;
class JdbcTest1 {
    public static void main (String[] args) {
        try {
            // Step 1: Load the JDBC driver.
            Class.forName("com.imaginary.sql.msql.MsqlDriver");
            // Step 2: Establish the connection to the database.
            String url = "jdbc:msql://www.myserver.com:1114/contact_mgr";
            Connection conn = DriverManager.getConnection(url,"user1","password");
        } catch (Exception e) {
            System.err.println("Got an exception! ");
            System.err.println(e.getMessage());
Listing 1: This source code example shows the two steps required to establish a connection to a Mini SQL (mSQL) database using JDBC.
An Interbase Example
Listing 2 provides the full source code required to establish a connection to an Interbase database. In this example, we're connecting to a local Interbase server (i.e., the server is running on the same PC that we're running the Java code on).
// Establish a connection to an Interbase database using JDBC.
import java.sql.*;
class JdbcTest1 {
    public static void main (String[] args) {
        try {
            // Step 1: Load the JDBC driver.
            Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
            // Step 2: Establish the connection to the database.
            String url = "jdbc:odbc:contact_mgr";
            Connection conn = DriverManager.getConnection(url,"user1","password");
        } catch (Exception e) {
            System.err.println("Got an exception! ");
            System.err.println(e.getMessage());
Listing 2: This source code example shows the two steps required to establish a connection to an Interbase database using JDBC.
What's the difference?
The difference between the two source code listings is very small, so we highlighted them in a dark blue color. The only difference between connecting to the two databases is:
The name of the JDBC driver.
The URL used to connect to the database.
Everything else in the two source code listings -- except for the comment at the top -- is identical. Here's a slightly more detailed discussion of the two differences:
1. The JDBC Driver
The name of the JDBC driver will be supplied to you by your database vendor. As you can see in the class.forName() statements, these names will vary. In the first case we're using the mSQL-JDBC driver. In the second case we're using the JDBC-ODBC Bridge driver supplied with the Interbase server.
2. The URL
The syntax of the DriverManager.getConnection() method is:
DriverManager.getConnection(String url, String username, String password);
The username and password are the normal names you use to log into your database. The URL you use will again vary with the database you use. In both examples shown, we're establishing a connection to a database named contact_mgr. (We'll use this database for all of our examples in this series of JDBC articles.)
If you stick with standard SQL commands, it can be very easy to switch from one database server to another. In fact, I've heard from several developers who are using mSQL to prototype their software (because it's so inexpensive), and then switching to another commercial vendor when it's time to take their product "live".
Conclusion
Establishing a connection to an SQL database with Java JDBC is a simple, two-step process. The process is nearly identical for all SQL databases, and the only real differences are (a) the driver name, and (b) the URL used to connect to the database. Your database vendor will provide this information in their documentation.
Resources mentioned in this article
Here are a few links to resources we mentioned in this article:
Interbase
The Mini SQL (mSQL) database
The mSQL-JDBC driver at imaginary.com
[an error occurred while processing this directive]

JDBC Drivers for SQL server 2000

Hi friends,
while trying to connect SAP xMII with SQL server 2000, i am facing difiiculties Driver classname ,URL and the correct driver(jar file)
can you please help to solve this problem.
Thanks
Srikanth

Hi Srikanth,
Download the Driver from
http://www.microsoft.com/downloads/details.aspx?familyid=07287b11-0502-461a-b138-2aa54bfdc03a&displaylang=en,
This will give u setup.exe, Once you Install the the exe , you can find 3 jar files at
C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib.
Copy the Jar files and Paste them in <xMIIServer>\ServletExec AS\se-xMII\webapps\default\Lighthammer\WEB-INF\lib
Now in the DataSource Tab in xMII main menu, copy the IDBC data source and create a new one, in that Put the server URL as
jdbc:microsoft:sqlserver://yourServerName:1433;user=yourUser;password=yourPwd
and Driver name as com.microsoft.jdbc.sqlserver.SQLServerDriver
Hope this will help
Thanks and Regards
Rupesh

Question about load Microsoft JDBC driver for Sql server 2000

Hello,
I have some problem while trying load the sqlserver2000 jdbc driver
My program is a third party application and it works with the other type 4 JDBC driver well. So I tried to use Microsoft SQL server 2000 JDBC driver instead.
I installed JDBC driver and set up the classpath.
My error message is:
"Driver class 'com.microsoft.jdbc.sqlserver.SQLServerDriver' could not be loaded"
Is above message means that my classpath setup correctly but the application could not load the class or the application could not find the jar file which containes the driver class?
By the way, the third party application I was using to load this JDBC driver does not certified to use microsoft JDBC driver. But I don't think it matter?
Thanks for your help
Hui Lu

Hello,
I have some problem while trying load the
sqlserver2000 jdbc driver
My program is a third party application and it works
with the other type 4 JDBC driver well. So I tried to
use Microsoft SQL server 2000 JDBC driver instead.
I installed JDBC driver and set up the classpath.
My error message is:
"Driver class
'com.microsoft.jdbc.sqlserver.SQLServerDriver' could
not be loaded"
That is an unusual message. Presumably you did not see "NoClassDefFoundError". If you see that it means the class could not be found.
Is above message means that my classpath setup
correctly but the application could not load the class
or the application could not find the jar file which
containes the driver class?
By the way, the third party application I was using to
load this JDBC driver does not certified to use
microsoft JDBC driver. But I don't think it matter?
It could. Perhaps the app expects a certain functional level and the driver doesn't support that. And so it bails with the message that you see.
Or it could mean that you have do something special because it has its own class path, and the driver is not in that.

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)

Is this a bug in JDBC driver for SQL Server 2000?

Hi, all:
I encountered a strange problem today.
My struts/jsp application throws an error while executing the following SQL:
SELECT id,moduleName,pageLevel,ent_name,style_name,type,hits,startDate,expireDate,expireAction,active,dealtime FROM v_ad WHERE style_id=1 ORDER BY id DESC
The error message is:
[Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Invalid column name 'style_id'.
However, the column "style_id" does exist in view "v_ad", and if I execute this query in SQL Server Query Analyzer, it runs rightly with my expected result.
I wonder if this is a bug of JDBC, and if this is really a bug, how should I deal with this problem?
Any help would be thankful!

Sounds like you may not have connected to the right database on the server.
Check the default database for the username/passwd combo you are logging in with.

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

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

Deploying JDBC connector for SQL Server 2000

Similar Messages

Maybe you are looking for