SQL Server JDBC Driver Not Found!!!!!!!!!
Guys,
I really need help with this one coz it seems I've done everything and still things aren't working.I'm running a Win2k Server with Sql Server 2000,now I know that I need the sql server 2000 Jdbc drivers inorder for me to connect to the sql server on my machine I've downloaded and installed the drivers successfully at least I think it's successfull coz when I go to the administrative tools option I see that the drivers have been installed.
When I try to connect to the server I get an error:
Class loading errorjava.lang.ClassNotFoundException: com.microsoft.jdbc.sqlserver.SQLServerDriver
despite the fact I have installed the drivers.
If you've got any idea on how to solve this problem,I would appreciate it if you filled me in.
Notice that you aren't using the MSSQL JDBC driver anymore but the Sun JDBC-OBDC-Bridge now which is far less powerfull than the MSSQL driver.
If you want to switch back to the MSSQL driver:
Regarding the setup of the driver. Not setup required - only for extracting the driver JAR files. Put the 3 JAR files into the classpath of your app server where web-apps can see them. At least you can always put them into the WEB-INF\lib directory of your web-app, where the driver is visible only to your web-app.
If you would like to configure the driver parameter in your web.xml use context init-parameters for web-app wide scope or servlet/JSP init-parameters for servlet/JSP only scope.
Michael
Similar Messages
-
Update of MySQL and SQL Server JDBC Driver does not work in 1.2.1
Hi,
always after the update process is started i got the MySQL and SQL Server JDBC driver
update notification.
But all the time after i install the update i got the notification again but no errormessage
that the update was maybe not successful ???
FrankOk
then my subject was false
i always try to update the extensions and now i can see that they are updated on the filesystem but the IDE does not recognize them as updated
....\sqldeveloper\sqldeveloper\extensions\oracle.sqldeveloper.thirdparty.drivers.mysql
is available and new after the update process
and under
...\sqldeveloper\sqldeveloper\tmp\update\oracle.sqldeveloper.thirdparty.drivers.mysql.5239.zip
the downloaded zip file is also available.
In the update window the message is that the extension with version 5206 is available
Maybe that is the problem cause the downloaded files are version 11.1.1.5239
if you look at the bundle.xml file inside the META-INF directory
Frank -
Sql Exception on Testing Configuration with SQL Server JDBC driver for XA
I have a requirement of analyzing the behavior of SQL Server JDBC data sources for XA transactions in our application.We have been using Non-XA drivers for both Oracle and SQL Server as we had no requirement for transactions spanning across multiple databases in past.I have setup and tested the XA driver for Oracle (Oracle Driver (Thin XA) for Instance Connections 9.0.1,9.2.0,10,11) in Weblogic 11g and its working perfectly for transactions spanning across two databases.No when I am trying to configure weblogic 11g R1 for Sql server JDBC driver to support XA transactions with driver details as follows,
Server:Weblogic 11g R1
Driver Type: MS Sql Server
Database Driver :Oracle's MS SQL Server Driver(Type 4 XA) Version:7.0,2000,2005)
Database:SQL Server 2005(Single Instance)
and try to create a new data source and select "Test Configuration" and following error is thrown ,
<Mar 17, 2011 4:49:49 PM GMT+05:30> <Error> <Console> <BEA-240003> <Console encountered the following error java.sql.SQLException: [OWLS][SQLServer JDBC Driver][SQLServer]xa_open (0) returns -3
at weblogic.jdbc.sqlserverbase.BaseExceptions40.createAppropriateSQLExceptionInstance(Unknown Source)
at weblogic.jdbc.sqlserverbase.BaseExceptions40.createSQLException(Unknown Source)
at weblogic.jdbc.sqlserverbase.BaseExceptions.createException(Unknown Source)
at weblogic.jdbc.sqlserverbase.BaseExceptions.getException(Unknown Source)
at weblogic.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
at weblogic.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
at weblogic.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown Source)
at weblogic.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
at weblogic.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unknown Source)
at weblogic.jdbc.sqlserverbase.BaseStatement.commonTransitionToState(Unknown Source)
at weblogic.jdbc.sqlserverbase.BaseStatement.postImplExecute(Unknown Source)
at weblogic.jdbc.sqlserverbase.BasePreparedStatement.postImplExecute(Unknown Source)
at weblogic.jdbc.sqlserverbase.BaseStatement.commonExecute(Unknown Source)
at weblogic.jdbc.sqlserverbase.BaseStatement.executeUpdateInternal(Unknown Source)
at weblogic.jdbc.sqlserverbase.BasePreparedStatement.executeUpdate(Unknown Source)
at weblogic.jdbcx.sqlserver.SQLServerImplXAResource.executeXaRpc(Unknown Source)
at weblogic.jdbcx.sqlserver.SQLServerImplXAResource.executeXaRpc(Unknown Source)
at weblogic.jdbcx.sqlserver.SQLServerImplXAResource.open(Unknown Source)
at weblogic.jdbcx.sqlserverbase.BaseXAConnection.init(Unknown Source)
at weblogic.jdbcx.sqlserverbase.BaseXAConnection40.init(Unknown Source)
at weblogic.jdbc.sqlserverbase.BaseClassCreatorForJDBC40.createXaConnection(Unknown Source)
at weblogic.jdbcx.sqlserverbase.BaseXADataSource.getXAConnection(Unknown Source)
at com.bea.console.utils.jdbc.JDBCUtils.testConnection(JDBCUtils.java:550)
at com.bea.console.actions.jdbc.datasources.createjdbcdatasource.CreateJDBCDataSource.testConnectionConfiguration(CreateJDBCDataSource.java:450)
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:597)
at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:870)
at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:809)
at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:478)
at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:306)
at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:336)
at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:52)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:97)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2044)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:64)
at org.apache.beehive.netui.pageflow.interceptor.action.ActionInterceptor.wrapAction(ActionInterceptor.java:184)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.invoke(ActionInterceptors.java:50)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:58)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:87)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2116)
at com.bea.console.internal.ConsolePageFlowRequestProcessor.processActionPerform(ConsolePageFlowRequestProcessor.java:261)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:556)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:853)
at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:631)
at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:158)
at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:256)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServlet.java:133)
at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1199)
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:686)
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:142)
at com.bea.portlet.adapter.scopedcontent.PageFlowStubImpl.processAction(PageFlowStubImpl.java:106)
at com.bea.portlet.adapter.NetuiActionHandler.raiseScopedAction(NetuiActionHandler.java:111)
at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:181)
at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:167)
at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:225)
at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:180)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:324)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:130)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:184)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:159)
at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388)
at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:199)
at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.service(MBeanUtilsInitSingleFileServlet.java:47)
at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:130)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
I followed the instruction in weblogic jdbc drivers guide to configure the JTA Transactions to support XA on SQL Server machine and weblogic server which included,
1.Copying sqljdbc.dll copied to SQL_Server_Root/bin directory from WL_HOME\server\lib.
2.Copied instjdbc.sql to sql server machine and executed the script with following output,
Changed database context to 'master'.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_open', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_open2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_close', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_close2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_start', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_start2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_end', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_end2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_prepare', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_prepare2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_commit', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_commit2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_rollback', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_rollback2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_forget', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_forget2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_recover', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_recover2', because it does not exist or you do not have permission.
creating JDBC XA procedures
instxa.sql completed successfully.
3.Verified that MSDTC service is running on both SQL Server and weblogic machines with XA Transaction enabled and DTC option enabled for both inbound and outbound connections.
4.Copied sqljdbc.jar (version 3.0 downloaded from msdn portal) to "C:\Oracle\Middleware\wlserver_10.3\server\ext\jdbc\sqlserver" directory and updated weblogic_classpth variable in commEnv.cmd file.
set WEBLOGIC_CLASSPATH=%JAVA_HOME%\lib\tools.jar;%BEA_HOME%\utils\config\10.3\config-launch.jar;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar;%FEATURES_DIR%\weblogic.server.modules_10.3.2.0.jar;%WL_HOME%\server\lib\webservices.jar;%ANT_HOME%/lib/ant-all.jar;%ANT_CONTRIB%/lib/ant-contrib.jar;C:\Oracle\Middleware\wlserver_10.3\server\ext\jdbc\sqlserver\server\ext\jdbc\sqlserver\sqljdbc.jar
Can some one please provide some input on whats causing this and any other steps needs to be followed to implement XA support using SQL Server JDBC driver.You seem to have done everything correctly and diligently. I would ask that you open
an official support case. -
JDBC Driver not found when connecting to Data Federator XI 3.0 SP3
Hello,
I am trying to connect Crystal 2008 to Data Federator however I am getting the Error
Failed to open connection.
Details: JDBC Driver not found.
The JDBC Drivers are installed and working for the Universe Designer, however I am unable to get it working for Crystal. I am using the following connection parameters on Crystal:
Connection URL: jdbc:datafederator://<<servername>>:3055/<<catalog>>
Database Classname: com.businessobjects.datafederator.jdbc.DataFederatorDriver
Any Advice on what I may have missed?The issue was solved, thanks to Patric Wan:
u201CFailed to open the connection. Details: JDBC driver not found.u201D
This means Data Federator JDBC driver was not added to:
C:\Program Files\Business Objects\common\<version>\java\CRConfig.xml
How to connect the Data Federator Server using JDBC?
1. Retrieve the following files from the machine where Data Federator is installed, from the directory [data-federator-installation-dir]/JdbcDriver/lib.
- thindriver.jar
- avalon-framework-4.1.5.jar
- jacorb.jar
- log4j-1.2.8.jar
- logkit-1.2.jar
2. Copy these files to a directory of your choice ([your-jdbc-driverdirectory]).
3. Add [your-jdbc-driver-directory]/thindriver.jar to CRConfig.xml <Add to Classpath tag, you can refer to original sample.CRConfig.xml should be at: C:\Program Files\Business Objects\Common\4.0\java\CRConfig.xml, or search your BOBJ products install to find this file>
4. URL: jdbc:leselect://<host>[:<port>][/[<catalog>]][[;param-name=value]*]
Class Name : LeSelect.ThinDriver.ThinDriver
Edited by: Craig Sander on Feb 12, 2011 8:22 PM -
Need help with MS SQL server JDBC driver
Anyone has experience getting ACS working with SQL2005? We keep getting ‘com.adobe.adept.persist.DatabaseException: java.sql.SQLException: No suitable driver’
We’re using sqljdbc.jar and sqljdbc4.jar that downloaded from Microsoft website. We added this to every library folder under tomcat, JRE and SDK but it did not help. Any suggestion will be helpful.
Thanks-Hi,
We have ACS with SQL Server 2005 Std correctly working.
We have this settings:
############ SQL Server Connection ############
com.adobe.adept.persist.sql.driverClass=com.microsoft.sqlserver.jdbc.SQLServerDriver
com.adobe.adept.persist.sql.connection=jdbc:sqlserver://ip-addressSQL:PortSQL;databaseName =Adept
com.adobe.adept.persist.sql.dialect=microsoft
com.adobe.adept.persist.sql.user=userSQL
com.adobe.adept.persist.sql.password=passSQL
Wi use Microsoft SQL Server JDBC Driver 3.0 downloaded from Microsoft website (http://www.microsoft.com/download/en/details.aspx?id=21599)
Good luck, -
Microsoft SQL Server JDBC driver and WLS JMS problem?
Greetings,
I'm using the Microsoft SQL Server JDBC driver with WLS with JMS
persisted to SQL Server, during WLS startup the JMS attempts to
read the JMSStore and JMSState tables in the db, if they are
already present (say, from a previous run) the driver kicks out:
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can
not re-read row data for column 1.
If the tables are not present, then WLS creates them and
everything proceeds fine. Now, its not a good thing to attempt
to reread row data for a ResultSet, especially for portability. Why is WLS JMS
doing this? is there some config I can use to adjust JMS startup behavior for
persisted JMS stores?
Jay Houghton
Centiv
[email protected]
long exception trace follows:
<Oct 1, 2002 8:29:11 AM EDT> <Info> <JMS> <User connection factory "BroadcastTopicFactory"
is started.>
<Oct 1, 2002 8:29:18 AM EDT> <Info> <JMS> <JMSServer "EnergizerJMSServer", Opening
JDBC store tables "JMSStore
" and "JMSState" using connection pool "JMSConnectionPool".>
<Oct 1, 2002 8:29:20 AM EDT> <Alert> <JMS> <JMSServer "EnergizerJMSServer", store
failed to open, java.io.IOEx
ception: JMS JDBC store, connection pool = <JMSConnectionPool>, prefix = <null>:
recover
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can
not re-read row data for colum
n 1.
at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
at weblogic.jdbc.pool.ResultSet.getLong(ResultSet.java:304)
at weblogic.jms.store.JDBCIOStream.doRecover(JDBCIOStream.java:618)
at weblogic.jms.store.JDBCIOStream.recover(JDBCIOStream.java:728)
at weblogic.jms.store.JMSStore.recover(JMSStore.java:112)
at weblogic.jms.backend.BEStore.open(BEStore.java:179)
at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:330)
at weblogic.jms.JMSService.createBackEnd(JMSService.java:923)
at weblogic.jms.JMSService.addJMSServer(JMSService.java:1277)
at weblogic.jms.JMSService.addDeployment(JMSService.java:1174)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:23
3)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
at $Proxy40.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub
.java:2734)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:362
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:154)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
at $Proxy57.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean
_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1151)
at weblogic.management.Admin.finish(Admin.java:571)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:508)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
Tom,
thanks for the info, I'll bring this to support.
I did try the weblogic jDriver for SQL Server and it works fine, so i think it
must be the way JMS is interacting with the MS driver.
here are my components:
WLS 6.1sp1
Microsoft® SQL Server™ 2000 Driver for JDBC™ is a (Type 4 JDBC) which provides
partial JDBC 2 support (no blobs, clobs, etc)
MS SQL Server 2000 (sp2?)
thanks!
Jay Houghton
[email protected]
Tom Barnes <[email protected]> wrote:
>Hi Jay,
>
>This is not a known issue at BEA as far as I know, perhaps it is the
>result
>of a new driver/database combination. Try using a different driver,
>or a different
>version of the current driver. Meanwhile, use a file store (just as
>reliable but faster) and log a case with customer support, including
>information on your version, service-pack, and what driver you are using.
>
>Tom, BEA
>
>Jay Houghton wrote:
>
>> Greetings,
>>
>> I'm using the Microsoft SQL Server JDBC driver with WLS with JMS
>> persisted to SQL Server, during WLS startup the JMS attempts to
>> read the JMSStore and JMSState tables in the db, if they are
>> already present (say, from a previous run) the driver kicks out:
>>
>> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet
>can
>> not re-read row data for column 1.
>>
>> If the tables are not present, then WLS creates them and
>> everything proceeds fine. Now, its not a good thing to attempt
>> to reread row data for a ResultSet, especially for portability. Why
>is WLS JMS
>> doing this? is there some config I can use to adjust JMS startup behavior
>for
>> persisted JMS stores?
>>
>> Jay Houghton
>> Centiv
>> [email protected]
>>
>> long exception trace follows:
>>
>> <Oct 1, 2002 8:29:11 AM EDT> <Info> <JMS> <User connection factory
>"BroadcastTopicFactory"
>> is started.>
>> <Oct 1, 2002 8:29:18 AM EDT> <Info> <JMS> <JMSServer "EnergizerJMSServer",
>Opening
>> JDBC store tables "JMSStore
>> " and "JMSState" using connection pool "JMSConnectionPool".>
>> <Oct 1, 2002 8:29:20 AM EDT> <Alert> <JMS> <JMSServer "EnergizerJMSServer",
>store
>> failed to open, java.io.IOEx
>> ception: JMS JDBC store, connection pool = <JMSConnectionPool>, prefix
>= <null>:
>> recover
>> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet
>can
>> not re-read row data for colum
>> n 1.
>> at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
>> at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
>> at weblogic.jdbc.pool.ResultSet.getLong(ResultSet.java:304)
>> at weblogic.jms.store.JDBCIOStream.doRecover(JDBCIOStream.java:618)
>> at weblogic.jms.store.JDBCIOStream.recover(JDBCIOStream.java:728)
>> at weblogic.jms.store.JMSStore.recover(JMSStore.java:112)
>> at weblogic.jms.backend.BEStore.open(BEStore.java:179)
>> at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:330)
>> at weblogic.jms.JMSService.createBackEnd(JMSService.java:923)
>> at weblogic.jms.JMSService.addJMSServer(JMSService.java:1277)
>> at weblogic.jms.JMSService.addDeployment(JMSService.java:1174)
>> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
>> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
>> at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:23
>> 3)
>> at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
>> at java.lang.reflect.Method.invoke(Native Method)
>> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
>> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
>> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
>> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
>> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
>> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
>> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
>> at $Proxy40.updateDeployments(Unknown Source)
>> at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub
>> java:2734)
>> at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:362
>> )
>> at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:154)
>> at java.lang.reflect.Method.invoke(Native Method)
>> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
>> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
>> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
>> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
>> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
>> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
>> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
>> at $Proxy57.start(Unknown Source)
>> at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean
>> _CachingStub.java:480)
>> at weblogic.management.Admin.startApplicationManager(Admin.java:1151)
>> at weblogic.management.Admin.finish(Admin.java:571)
>> at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:508)
>> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
>> at weblogic.Server.main(Server.java:35)
>
-
MS SQL Server jdbc Driver installation on XI
Hi,
I am running XI 3 on sp11 patch 1.
We need to install the MS SQL Server jdbc driver on the XI box to connect to a SQL Server 2000 SP3 Database server.
We tried installing the driver from the MS downloads website:
http://www.microsoft.com/downloads/details.aspx?familyid=07287b11-0502-461a-b138-2aa54bfdc03a&displaylang=en
But this is giving us problems while installation as SDM does not like the format.
Can someone please tell us how do we install this driver?
Thanks
AshishHi Ashish,
i assume that u already have the drivers (msbase.jar,mssqlserver.jar,msutil.jar). All u have to do is deploy them.
The procedure is:
1.Add all jars to the archive <b>aii_af_jmsproviderlib.sda</b>, modify the <b>provider.xml</b> file and WinZip the .sda file again.
a)Copy the file: aii_af_jmsproviderlib.sda from the path ..\usr\sap\SID\DVEBMGS00\SDM\root\origin\sap.com\com.sap.aii.af.jmsproviderlib\SAP AG\3.0.20040112154003.0000. to any other drive on the server.
b)Unzip it. After Unzipping the archive there are 2 folders created under the provided directory
\META-INF
\server
c) Edit the file provider.xml
Add the vendor specific jar file names to the provider.xml file in between the tags <jars> </jars> and Save it.
For you it will be
<jars>
<jar-name>msbase.jar</jar-name>
<jar-name>mssqlserver.jar</jar-name>
<jar-name>msutil.jar</jar-name>
</jars>
d)Copy the specific driver files to the same dirctory where u have unzipped the .sda
e)Now ZIP the following files/folders from the drive/dirctory.
Vendor driver files
META-INF folder
Server folder
The name of the zip file should be the same i.e aii_af_jmsproviderlib.sda
2.Deploy the archive aii_af_jmsproviderlib.sda on to the J2ee Engine using SDM tool.
This will solve ur problem.
Regards
Sunita -
2 questions come to mind.
will it work
will TAC support you ?
available here
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a737000d-68d0-4531-b65d-da0f2a735707&displaylang=en
Brief Description
Download the SQL Server JDBC Driver 3.0, a Type 4 JDBC driver that provides database connectivity through the standard JDBC application program interfaces (APIs) available in Java Platform, Enterprise Edition 5 and above.You can test it using DBvisualizer. If you can make it work in that (actually it gives you more information about connection errors etc.), it should working in UCCX also.
-
Web logic cann't load Sql Server jdbc driver
Web logic cann't load Sql Server jdbc driver. I've got an exception:
NoClassDefFoundError: com/microsoft/sqlserver/jdbc/ISQLServerConnection
but sqljdbc.jar is in weblogic's library directory.Hi,
You can find Oracle Support id 1503650.1 (https://support.oracle.com) with the solution.
Arik -
Where to put SQL Server JDBC driver in Tomcat?
Can anyone tell me where should I put the Microsoft SQL Server JDBC driver in the Tomcat and can make it work?
You may also need to place the full path in the classpath variable. You can also download install instructions from the same page where you access the microsoft driver.
-
J2EE SDK & SQL Server JDBC Driver
I am trying to use SQL Server JDBC Driver with J2EE SDK.
Following with the instruction of Deployment tool's help, I configured both the SQL Server JDBC and JDBC-ODBC Bridge. My classpath has include SQL Server JDBC Driver's lib, and my java program can connect to SQL Server 2000 correctly. but deployment tool always told me "no suitable driver" with SQL Server JDBC Driver when I want to generate SQLs. With JDBC-ODBC bridge, it's OK.
Why? I just want to know that if there is anywhere else that I can configure the class lib. I think it's because J2EE can't find the classes of SQL Server JDBC, but I don't know how to do.step 1:download the sql driver and unzip it
step 2:copy the .jar file to $j2ee_home%/lib/system
step 3:modif userconfig.bat file ,add the .jar files
to j2ee_classpath
step 4:modify you resource.properpties files,add
yourself
JNDI name.
because i am a chinese,have poor english,if can't
trouble,send e-mail to me,i can replay to u with the
config files.I do as your steps,but it still cannot work. for bookstore1(j2ee tutorial example), it give out such exception:
javax.servlet.UnavailableException: Couldn't get database.
at BookStoreServlet.init(BookStoreServlet.java:28)
what 's the problem?
please give me some advice. -
Driver class name value for SQL Server JDBC driver
if i am using SQL Server JDBC driver to connect to DB using STRUTS DBCP
what will be the value for the property="driverClassName"
& value for property="url"
eg., <data-source type="org.apache.commons.dbcp.BasicDataSource" >
<set-property property="driverClassName" value="org.gjt.mm.mysql.Driver" />
<set-property property="url" value="jdbc:mysql://10.1.0.8/omega4105" />
<set-property property="username" value="iris"/>
<set-property property="password" value="iris"/>
</data-source>For SQL Server 2000
com.microsoft.jdbc.sqlserver.SQLServerDriver
For SQL Server 2005
com.microsoft.sqlserver.jdbc.SQLServerDriver -
SQL Server JDBC Driver Bug?
I ran into an unusual situation with the MS SQL Server JDBC driver that I think is a bug and could bite people in some unusual cases.
Here is the situation that creates the problem.
- get a connection
- make it transactional (autocommit false)
- discover that there is no work to do in the transaction so no commit or rollback is done.
- make the connection non-transactional (autocommit true)
- update other tables using the connection (should be non-transactional)
This leaves the tables updated in the last step locked as part of a transaction!
It doesn't behave this way with our DB2 driver.
While I agree that the JDBC spec is vague in many areas, this seems to be well out of bounds of any reasonable interpretation.
The workaround is to also do a rollback (in a try/catch block) before setting autocommit true.
-- FrankSince database operations are rather expensive why would you do any before checking to see if something needs to be done?
-
Problem using MS SQL Server JDBC Driver
I am trying to use MS SQL Server JBDC driver with JDeveloper9i. I followed the steps mentioned in the document
http://otn.oracle.com/products/jdev/howtos/bc4j/bc_psqlserverwalkthrough.html
Still I am getting the following error message
Error initializing data-source 'SQLTestDS': DriverManagerDataSource driver 'com.microsoft.jdbc.sqlserver.SQLServerDriver' not found
What could be the reason?Did anybody run into similar issue?
Thanks in advance.
RCI assume from your message that you are attempting to
deploy your application into OC4J - you're probably
implicitly using the inbuilt OC4J if your using JSPs.
If so, try placing the jdbc jars into the <JDEVHOME>\lib directory
and referencing them from the j2ee\home\application.xml
file:
use lines like:
<library path="../../../lib/msbase.jar" />
regards, Karl -
Microsoft SQL Server JDBC Driver problem
Hi all,
I've downloaded the JDBC driver for SQL Server 2000 from Microsoft website and I
tried creating connection pool in Weblogic (WL 6.1 SP2).
Following are the configuration from the admin console,
Name - SQL2K
URL - jdbc:microsoft:sqlserver://127.0.0.1:1433
Driver Classname - com.microsoft.jdbc.sqlserver.SQLServerDriver
ACLName - sa
Password - tonypet
After creating the config, I select to chose the target server from the Servers tab
in Targets main tab in the admin console and when I click on Apply I saw in the WL
server command prompt the following error,
<16/07/2002 11:22:55> <Error> <JDBC> <Cannot startup connection pool "SQL2K" Cannot
load driver class: com.microsoft.jdbc.sqlserver.SQLServerDriver>
I have assigned the classpath env var as follows,
CLASSPATH=;.;C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msbase.jar;C:\Program
Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msutil.jar;
C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\mssqlserver.jar;c:\bea\wlserver6.1\lib\weblogic.jar
I've tried even copying the .JAR files to the ext and lib directory of bea directory
but I'm getting the same error.
Can anyone help me please.
Thanks a lot for your help
Cheers
NanikHi. You will also be wanting to add this property for the pool to apply to that driver:
SelectMethod=cursor
Joe
Nanik Tolaram wrote:
Hi all,
After fiddling around I found a solution (hope this will help those who are having
the same problem),
1. Make sure you add the complete directory of the library of the .JAR files in the
classpath in the STARTWEBLOGIC.CMD, I made a mistake of specifying the path in the
CLASSPATH and NOT IN the STARTWEBLOGIC.CMD as the classpath is overriden in the STARTWEBLOGIC.CMD
file.
2. The other thing I found was the configuration setting. I put the full settings
in the URL in admin console as follows,
jdbc:microsoft:sqlserver://127.0.0.1:1433;user=nanik;password=tonypet;databasename=scriptbuilder
When I put it individually in the Properties filed it won't work as it is not picking
it up from there but when I moved it to the URL and put it all together it worked
fine.
Whew !!! it's been a looong day, hope the info will help.
Cheers
Nanik
"Nanik Tolaram" <[email protected]> wrote:
Hi all,
I've downloaded the JDBC driver for SQL Server 2000 from Microsoft website
and I
tried creating connection pool in Weblogic (WL 6.1 SP2).
Following are the configuration from the admin console,
Name - SQL2K
URL - jdbc:microsoft:sqlserver://127.0.0.1:1433
Driver Classname - com.microsoft.jdbc.sqlserver.SQLServerDriver
ACLName - sa
Password - tonypet
After creating the config, I select to chose the target server from the
Servers tab
in Targets main tab in the admin console and when I click on Apply I saw
in the WL
server command prompt the following error,
<16/07/2002 11:22:55> <Error> <JDBC> <Cannot startup connection pool "SQL2K"
Cannot
load driver class: com.microsoft.jdbc.sqlserver.SQLServerDriver>
I have assigned the classpath env var as follows,
CLASSPATH=;.;C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msbase.jar;C:\Program
Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msutil.jar;
C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\mssqlserver.jar;c:\bea\wlserver6.1\lib\weblogic.jar
I've tried even copying the .JAR files to the ext and lib directory of bea
directory
but I'm getting the same error.
Can anyone help me please.
Thanks a lot for your help
Cheers
Nanik
Maybe you are looking for
-
How do I upgrade my macbook pro 10.5.8 to a 10.6.3? Do I install snow leopard, if so which one and is this difficult? thanks kind of a newbie at doing this kind of stuff on my mac.
-
Can't look at laptop screen without getting migraines - any ideas?
Hi all, I used my last 15 inch macbook pro bought around 2007 for many hours every day without any problems before it recently gave up the ghost. I then purchased the latest 13 inch macbook pro model a couple of weeks ago. However, it seems I can't l
-
Hello, I have an iDoc in status 20. I already solved the problem that caused this error, and now I want to reprocess the iDoc, but I can't find a report that does this. I found reports that solve other errors, but not 20. Thank you.
-
Hello All We have call manager 7.0.1 and a billing server which gets calling informations and shows it in a web format.I have a problem sending informations to that server,from which part of the call manager i force to send information to my billing
-
Why won't my MacBook run on battery power when it is charged?
I love my 2009 MacBook but whenever I use it I have to have it plugged into the wall and if it ever comes slightly unplugged the laptop shuts off at that instant. I have checked the charge on the battery from the battery and my laptop says that