Using MS SQL Server 2000 for WLCS 3.50 DB

I'm using WebLogic 6.0sp1 with Commerce Server 3.5 and I've successfully
installed the demo. I would like to create another commerce server
installation, this time using Microsoft SQL Server 2000 as the database
instead of Cloudscape. I've downloaded and installed the BEA jDriver
for MS SQL 7/2000 and tested it using dbping. My question is: where are
the db scripts for creating and populating the commerce database? I've
found the WLCS_320_DB_DDL_1.1.zip file on the BEA downloads site, but
I'm concerned that this schema is for Version 3.20 of Commerce Server.
Is there a similar file for WLCS 3.50? If not, is it safe to use this
one?
If this is posted in the wrong place, please let me know and I'll repost
to the appropriate newsgroup as required.
Sincerely,
Michael Schulz

Hi Michael,
At this time SQL Server 2000 is not certified for WLCS 3.5. Since the
schema has changed between 3.2 and 3.5, running the 3.2 scripts is not a
good idea.
I can tell you that certification is in progress for SQL Server 2000. Your
best bet is to contact your Sales Representative to get an idea of when
certification might be coming.
I hope this helps.
- Ginny
"Michael Schulz" <[email protected]> wrote in message
news:[email protected]..
I'm using WebLogic 6.0sp1 with Commerce Server 3.5 and I've successfully
installed the demo. I would like to create another commerce server
installation, this time using Microsoft SQL Server 2000 as the database
instead of Cloudscape. I've downloaded and installed the BEA jDriver
for MS SQL 7/2000 and tested it using dbping. My question is: where are
the db scripts for creating and populating the commerce database? I've
found the WLCS_320_DB_DDL_1.1.zip file on the BEA downloads site, but
I'm concerned that this schema is for Version 3.20 of Commerce Server.
Is there a similar file for WLCS 3.50? If not, is it safe to use this
one?
If this is posted in the wrong place, please let me know and I'll repost
to the appropriate newsgroup as required.
Sincerely,
Michael Schulz

Similar Messages

Error Using the SQL Server 2000 Driver for JDBC Service Pack 3

Hi,
I�m using the SQL Server 2000 Driver for JDBC Service Pack 3. The connection is succesfully, but when I use de statement.executequery() method, there is the follow exception:
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Invalid object name 'PEC_COUNTRY'.
This is my code:
ResultSet resultSet;
Statement statement;
Connection connection;
Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver").newInstance();
connection = DriverManager.getConnection("jdbc:microsoft:sqlserver://S0MALMUERTA:1433;user=sa;password=");
statement = connection.createStatement();
resultSet = statement.executeQuery("SELECT COY_INX, COY_NAME, COY_ICO FROM PEC_COUNTRY
");When I make the last instruction, occurs the above exception
Thanks in advance
Luija

The way you are connecting, the default database used will be 'master' and i guess that the table PEC_COUNTRY was defined in another database.
If it is the case you need to specify the database name.
connection = DriverManager.getConnection("jdbc:microsoft:sqlserver://S0MALMUERTA:1433;DatabaseName=yourdb;user=sa;password=");

Using MS Sql Server 2000 with Flex 2

help! - I'm trying to understand how I could use Flex 2 (with
the Flex Data Services) using MS SQL Server 2000 as my RDMS.
Currently using SS with ASP. Basically, what do I need in
terms of server set up (e.g. do I need to install the J2EE Server
for instance?). How about using transaction based storedprocedures
with flex.
I'm having difficulty finding a clear answer (for me anyway!)
to my question. I have even phoned Adobe last Thursday to ask them
- and their expert was not around and they said would call me
back... hmm.

Hi Michael,
At this time SQL Server 2000 is not certified for WLCS 3.5. Since the
schema has changed between 3.2 and 3.5, running the 3.2 scripts is not a
good idea.
I can tell you that certification is in progress for SQL Server 2000. Your
best bet is to contact your Sales Representative to get an idea of when
certification might be coming.
I hope this helps.
- Ginny
"Michael Schulz" <[email protected]> wrote in message
news:[email protected]..
I'm using WebLogic 6.0sp1 with Commerce Server 3.5 and I've successfully
installed the demo. I would like to create another commerce server
installation, this time using Microsoft SQL Server 2000 as the database
instead of Cloudscape. I've downloaded and installed the BEA jDriver
for MS SQL 7/2000 and tested it using dbping. My question is: where are
the db scripts for creating and populating the commerce database? I've
found the WLCS_320_DB_DDL_1.1.zip file on the BEA downloads site, but
I'm concerned that this schema is for Version 3.20 of Commerce Server.
Is there a similar file for WLCS 3.50? If not, is it safe to use this
one?
If this is posted in the wrong place, please let me know and I'll repost
to the appropriate newsgroup as required.
Sincerely,
Michael Schulz

Error in installing SQL SErver 2000 for SAp

When i try to install Ms SQL server 2000 for SAP it is giving me a message , "unable to validate product key"
Pls let me know how to solve it

Dear,
When u install original sql server, might be it should not ask for product key. In sql source there is one vbs script, just click on that vbs script and ur installation of sql server is going to start. This is upto my knowledge.
Thanking You.
Charanjit

When a database is last used in SQL Server 2000.

Hi,
Need to create one script by which I can get my any of the database lastly used, which is running on SQL Server 2000 lastly used.
Lets say if I have 100 databases running on SQL Server 2000, then using one query I can get all the databases last access date.
I dont want to implement audits because that will give only the result after audit setup.
Thanks In Advance
Regards, Ashish Tripathi

Agree with Erland.
There is no "column" in sys.databases till now. I would suggest you to vote for this feature.
https://connect.microsoft.com/SQLServer/feedback/details/659846/database-last-accessed-time
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

WL 6.0 using MS SQL Server 2000 - Transaction timeout when invoking stored procedure

Hi,
Facing a problem on WL6.0. We are connecting to MS SQL server 2000 using a stateless
session bean
using container managed transaction. The bean method does a few updates to the
database and also
calls a stored procedure that generates primary keys many times. This stored procedure
(SP) is running
in a transaction of its own since it has to increment a counter, update the database
and then return the
primary key.The primary key generator SP is working fine and does not lock the
database in many bean
methods.
In some methods we find that the primary key generator SP has locked the database.
We
then see a lock on the database created due to this SP in the MS SQL client. The
execution goes
into the SP and gets stuck there till the bean's transaction times out. The error
message given is
...... .. Exception Message - The transaction is no longer active
(status = Rolling Back. [Reason = weblogic.transaction.internal.TimedOutExcepti
on: Transaction timed out after 31seconds
tx = transaction=(IdHash=1746718,Name = [EJB StructMgrBeanImpl.addStructure()],X
id=10908:51e67e9d7185816a,Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=
0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '7'
for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[web
logic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[myserver]=(state
=active),properties=({weblogic.transaction.name=[EJB StructMgrBeanImpl.addStruct
ure()], weblogic.jdbc=t3://10.200.15.136:7001}))]). No further JDBC access is
al
lowed within this transaction.
What could be the potential problems in the method's code/SP that could be causing
the timeout?
Anyone faced similar problems?
Thanks in advance,
Sreeja

Hi,
Facing a problem on WL6.0. We are connecting to MS SQL server 2000 using a stateless
session bean
using container managed transaction. The bean method does a few updates to the
database and also
calls a stored procedure that generates primary keys many times. This stored procedure
(SP) is running
in a transaction of its own since it has to increment a counter, update the database
and then return the
primary key.The primary key generator SP is working fine and does not lock the
database in many bean
methods.
In some methods we find that the primary key generator SP has locked the database.
We
then see a lock on the database created due to this SP in the MS SQL client. The
execution goes
into the SP and gets stuck there till the bean's transaction times out. The error
message given is
...... .. Exception Message - The transaction is no longer active
(status = Rolling Back. [Reason = weblogic.transaction.internal.TimedOutExcepti
on: Transaction timed out after 31seconds
tx = transaction=(IdHash=1746718,Name = [EJB StructMgrBeanImpl.addStructure()],X
id=10908:51e67e9d7185816a,Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=
0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '7'
for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[web
logic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[myserver]=(state
=active),properties=({weblogic.transaction.name=[EJB StructMgrBeanImpl.addStruct
ure()], weblogic.jdbc=t3://10.200.15.136:7001}))]). No further JDBC access is
al
lowed within this transaction.
What could be the potential problems in the method's code/SP that could be causing
the timeout?
Anyone faced similar problems?
Thanks in advance,
Sreeja

Using the SQL Server Agent for the first time

I have set up several jobs to run automatically throughout the day. Each job just does one thing: executes an SSIS package.
The packages themselves run perfect when I test them in Visual Studio 2005, but when the SQL Server Agent tries to run the job I am getting failed jobs.
Is there any tutorials or walkthroughs that can teach my about using the SQL Server Agent? If I wanted extensive help troubleshooting my SQL Server Agent problems which part of the message boards would I post that too?
Thanks for the info!

Anyone?
I really need some resources for SQL Server Agent 2005.
Refer these links,
http://technet.microsoft.com/en-us/library/ms141701(v=sql.90).aspx
http://stackoverflow.com/questions/10489392/permissions-issue-running-ssis-package-from-sql-job
Regards, RSingh

ERROR using SQL Server 2000, FOR UPDATE clause problem

Hi All,
Because our main target for RDBMS mostly SqlServer2000, I try to use ADF BC with one. I successfully run the BC with Tester, scrolling up and down, BUT when i try to make changes and do commit, I receive ERROR, I have tried both JDBC Driver from Microsoft and jTDS, both FAILS.
I have set the 'Default Locking Mode ..' to 'optimistic'
(default is 'pessimistic'), it doesn't help.
Here is the error :
With Microsoft JDBC Driver :
(oracle.jbo.DMLException) JBO-26080: Error while selecting entity for Departments
----- LEVEL 1: DETAIL 0 -----
(java.sql.SQLException) [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer] FOR UPDATE cannot be specified on a READ ONLY cursor.
With jTDS JDBC Driver :
(oracle.jbo.DMLException) JBO-26080: Error while selecting entity for Departments
----- LEVEL 1: DETAIL 0 -----
(java.sql.SQLException) Line 1: FOR UPDATE clause allowed only for DECLARE CURSOR.
Pls any body help...
Thank you,
Krist

Krist,
we added a new SQL Flavor 'SQLServer' in JDeveloper 10.1.2
This was implemented to handle special SQL syntax of SQLServer, different from SQL92 (among others the FOR UPDATE problem you're facing).
For new projects, you can select this flavor during their creation. For projects that were defined with Flavor SQL92, you can switch to SQLServer at runtime by setting the parameter jbo.SQLBuilder=SQLServer (in your Application Module configuration or as a java option -Djbo.SQLBuilder=...)
Regards,
Didier.

PreparedStatement for SQL using IN (SQL Server 2000)

Hi, guys
How can I create a preparedStatement for a query using IN operator, which allow me to insert any number of parameters?
eg: SELECT * FROM Students WHERE lastname IN (?, ?, ?, ....)
Thanks
jacklty

Hi, I have found a simpler way of doing this.
private static final String QUERYSTRING = "SELECT * from junk_table "+
" WHERE status in (:x) " ;
<..somewhere later in the code...>
StringBuffer tempBuffer=new StringBuffer(QUERYSTRING);
//Find :1 and replace with a comma separeted list of stauts
tempBuffer.replace(tempBuffer.indexOf(":x"),tempBuffer.indexOf(":x") + ":x".length(),
new String(System.getProperty("status")));
In short, here I am creating my own bind parameters named as :x,:y (lack of imagination on my part...) and then replacing the values of those values with the comma-separated value before actually creating the PreparedStatement.
Hope this works
--Ved

Problem of loading the MS SQL Server 2000 driver for JDBC

Thanks for your reply.
I have already tried to give the full class path of .jar files to the System and User Variables but received the same error. I am doing BCA and developing my very first Project on Java.
Please, tell me one thing. When I had installed MS SQL Server 2000 at my system first time then the 3 JAR files were present in the lib folder and all my codings of connectivity were working properly. Then due to some reasons, I had to format C drive and installed the MS SQL Server 2000 again then in the lib folder the 3 JAR files were not there. How it has happened? Then, I installed the downloaded driver of MS SQL Server 2000 for JDBC 1.4 then the JAR files were installed in the related downloaded driver folder. I manually copied them to the lib folder of MS SQL Server and gave that path to the Classpath of System and User Variables, but it didn't work.
I am not understanding the reason that The Software which worked previously is not working correctly in second time of installing.
I am using command line to develop my stand-alone project. Please help me.

Don't bother with the System CLASSPATH, more often than not, it is not even used.
When running from an IDE, set the project's library preferences.
When running from a web container/application server configure the applications libraries in the server/container, see it's documentation.
When running an applet, configure the [ codebase and/or archive |http://java.sun.com/docs/books/tutorial/deployment/applet/html.html] tags properly.
When running from the command line with the [ "-cp" |http://java.sun.com/javase/6/docs/technotes/tools/solaris/java.html] option, the System CLASSPATH is ignored.
When running from the command line with the "-jar" option, both the System CLASSPATH path and the "-cp" option are ignored, configure the [manifest file|http://java.sun.com/docs/books/tutorial/deployment/jar/downman.html] properly.
When running any other way, the System CLASSPATH might be used.

Problem of loading the MS SQL Server 2000 Driver for JDBC 1.4.1

Thanks for your reply.
I have already tried to give the full class path of .jar files to the System and User Variables but received the same error. I am doing BCA and developing my very first Project on Java.
Please, tell me one thing. When I had installed MS SQL Server 2000 at my system first time then the 3 JAR files were present in the lib folder and all my codings of connectivity were working properly. Then due to some reasons, I had to format C drive and installed the MS SQL Server 2000 again then in the lib folder the 3 JAR files were not there. How it has happened? Then, I installed the downloaded driver of MS SQL Server 2000 for JDBC 1.4 then the JAR files were installed in the related downloaded driver folder. I manually copied them to the lib folder of MS SQL Server and gave that path to the Classpath of System and User Variables, but it didn't work.
I am not understanding the reason that The Software which worked previously is not working correctly in second time of installing.
I am using command line to develop my stand-alone project. Please help me.

Don't bother with the System CLASSPATH, more often than not, it is not even used.
When running from an IDE, set the project's library preferences.
When running from a web container/application server configure the applications libraries in the server/container, see it's documentation.
When running an applet, configure the [ codebase and/or archive |http://java.sun.com/docs/books/tutorial/deployment/applet/html.html] tags properly.
When running from the command line with the [ "-cp" |http://java.sun.com/javase/6/docs/technotes/tools/solaris/java.html] option, the System CLASSPATH is ignored.
When running from the command line with the "-jar" option, both the System CLASSPATH path and the "-cp" option are ignored, configure the [manifest file|http://java.sun.com/docs/books/tutorial/deployment/jar/downman.html] properly.
When running any other way, the System CLASSPATH might be used.

SQL Server 2000 Driver for JDBC - Error establishing sockets

Hi there
I am using Microsoft SQL Server 2000 Driver for JDBC to connect to SQL Sever 2000. It is just a test application to see if it would connect to the datacase successfully. But I got the following errors. I already set up the classpath and installed all SQL Server 2000 Driver for JDBC sp 3. Dont know why it still failed...can anyone help me out of this? Thanks.
When i am using simple JDBC-ODBC bridge Driver it's working fine.
For this Server Pack3 , i have checked every thing like--
TCP / IP Poart is Enable.
I am working in client machine, my MSSQLServer 2000 Placed in server Machine.
when i am giving Telnet ServerIP 1433 it's giving following response.
connecting to ServerIP ....... could not open connection to the host , on port 1433:connection Failed
My Sample Code is :--
String user="sa";
String password="imcindia";
Connection con1 = null;
CallableStatement cstmt = null;
Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver").newInstance();
con1=DriverManager.getConnection("jdbc:microsoft:sqlserver://ServerName:1433;DatabaseName=dmo1o2d",user,password);
Statement st=con1.createStatement();
st.execute("use dm0102d");
st.execute("setuser 'dm01012'");
cstmt = con1.prepareCall("{?=Call dms_ex_create_folder('ABC','18753','NB21','u')}");
cstmt.execute();
Here are Error Code :
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
     at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
     at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
     at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
     at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
     at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
     at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source)
     at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)
     at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
     at java.sql.DriverManager.getConnection(Unknown Source)
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Connection refused: connect
     at java.sql.DriverManager.getConnection(Unknown Source)
     at TestConnection1.main(TestConnection1.java:24)
one can help me to over come this problm,
Thanks in advance.
venkat

hey i also have this problem i have been looking for solution for this problem for along time i tried every possible solution i tried every service pack for the SQL but it didn't connect to the port!!!
it's a network problem ur java code is correct dont worry about it.
finally i had to install MySQL and it's work fine now but if u insist on usning SQL u have to use the JDBC-ODBC Bridge it will work by :
first add data source database , follow these steps
1- go to Administrative tools
2-Data Sources(ODBC)
3-System DNS tab and add then choose SQL SERVER the last option then finish
4-write the name; Note: this name is the one that u will write in ur URL for example if u write Hello the URL will be "jdbc:odbc:Hello"
5- choose the server, its recommended to write "." or (local)
6-change the database to its an important step to choose the database that u want to use, choose northwind if u want to use it
finish
second
adding this code:
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:Hello";
Connection conn = DriverManager.getConnection(url,"user1","password");
} catch (Exception e) {
System.err.println("Got an exception! ");
System.err.println(e.getMessage());
it will work without any problems

JDriver for microsoft sql server 2000

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

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

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

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

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

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.

Using MS SQL Server 2000 for WLCS 3.50 DB

Similar Messages

Maybe you are looking for