JDBC 2.0 method not supported Error occuring in WL 6.1 sp1

Hi ,
When I connect to a mssqlserver 2000 using a session bean and execute the following
statement
"stmDataAccess=conDataAccess.createStatement(ResultSet.CONCUR_UPDATABLE,ResultSet.TYPE_SCROLL_INSENSITIVE);"
i get the following error at the client and server side
what can be wrong?.Support for Jdbc 2.0 is inherent in WL 6.1 isn't it?
java.rmi.RemoteException: EJB Exception:; nested exception is:
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented]
Start server side stack trace:
java.rmi.RemoteException: EJB Exception:; nested exception is:
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented]
java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented]
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:271)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
; nested exception is:
javax.ejb.EJBException:
Start server side stack trace:
java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented]
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:271)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
Start server side stack trace:
java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
        at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
        at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
        at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
        at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
        at java.lang.reflect.Method.invoke(Native Method)
        at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
        at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
        at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
        at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
        at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
        at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
        at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
        at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
        at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
Start server side stack trace:
java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
--------------- nested within: ------------------
javax.ejb.EJBException:
Start server side stack trace:
java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented]
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:271)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
Start server side stack trace:
java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
        at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
        at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
        at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
        at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
        at java.lang.reflect.Method.invoke(Native Method)
        at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
        at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
        at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
        at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
        at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
        at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
        at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
        at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
        at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>

Hi
As I know, not all mehtods are supported by WebLogic. For Example for Oracle only
a SubSet of the JDBC methods are supported (see the link http://e-docs.bea.com/wls/docs61///////oracle/API_joci.html#1070961).
I can imagine that for Microsoft Products this is even worse.
Regards Patrick
"Thomas" <[email protected]> wrote:
>
Hi,
I'm using the driver that comes along with the application server ie
weblogic.jdbc.mssqlserver4.Driver.If
this driver doesn't support JDBC 2.0 where can i find a suitable driver
as my
app needs updatable recordsets with updateXXX methods and absolute moves?
Thanks in advance
"noone_home" <[email protected]> wrote:
Hi,
It looks like your JDBC driver does not support JDBC 2.0. I believethe
the JDBC
driver for SQL Server that came with WLS 6.x supports only JDBC 1.1.
I'm making
the assumption that that is the driver which you are using.
hth.
"Thomas" <[email protected]> wrote:
Hi ,
When I connect to a mssqlserver 2000 using a session bean and execute
the following
statement
"stmDataAccess=conDataAccess.createStatement(ResultSet.CONCUR_UPDATABLE,ResultSet.TYPE_SCROLL_INSENSITIVE);"
i get the following error at the client and server side
what can be wrong?.Support for Jdbc 2.0 is inherent in WL 6.1 isn't
it?
java.rmi.RemoteException: EJB Exception:; nested exception is:
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
is>>>not implemented
Start server side stack trace:
java.rmi.RemoteException: EJB Exception:; nested exception is:
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
is>>>not implemented
java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
is
not implemented
at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
is>>>not implemented
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:271)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
; nested exception is:
javax.ejb.EJBException:
Start server side stack trace:
java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 methodis
not implemented
at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
is>>>not implemented
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:271)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
is>>>not implemented>>> >>>Start server side stack trace:>>>java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method>is>>>not implemented>>> at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)>>> at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)>>> at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)>>> at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)>>> at java.lang.reflect.Method.invoke(Native Method)>>> at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)>>> at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)>>> at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)>>> at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)>>> at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown>>>Source)>>> at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)>>> at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)>>> at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)>>> at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)>>> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)>>> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)>>>End server side stack trace>>>
java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 methodis
not implemented
Start server side stack trace:
java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 methodis
not implemented
at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
--------------- nested within: ------------------
javax.ejb.EJBException:
Start server side stack trace:
java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 methodis
not implemented
at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
is>>>not implemented
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:271)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
is>>>not implemented>>> >>>Start server side stack trace:>>>java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method>is>>>not implemented>>> at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)>>> at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)>>> at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)>>> at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)>>> at java.lang.reflect.Method.invoke(Native Method)>>> at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)>>> at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)>>> at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)>>> at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)>>> at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown>>>Source)>>> at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)>>> at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)>>> at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)>>> at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)>>> at weblogic.kernel.ExecuteThread.execute>>(ExecuteThread.java:139)>>> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)>>>End server side stack trace>>>
<<no stack trace available>>

Similar Messages

"Function or method not supported" error at IviRFSigGen InitializeWithOptions.vi

Error 1074135023 at "IviRFSigGen Initialize With Options.vi", Primary Error (Hex 0xBFFA0011) "Function or method not supported". Error occurs when using Agilent IVI driver for RF Signal Generator (E4437B) with LabView. Instrument also does not switch to remote mode in response to the IVI initialize command from LabView, but direct communication using NI-488.2 Communicator works.

It looks like you are using the NI IVI Class Drivers, and have configured them to use the Agilent IVI-C driver under the hood. For some reason, it looks like the class drivers aren't happy with the Agilent driver, and that's the cause of the error.
You should first confirm your IVI configuration in MAX. You should make sure IVI Logical Name is pointing to the right Agilent driver, correct instrument address, etc. That name is what you pass into Initialize with Options.
If this doesn't pan out, it looks like you'll have to debug things.
First of all, do you need to use IVI? If not, then I'd recommend you download our LabVIEW instrument driver for this instrument, so that you can get LabVIEW source code.
It's available on http://ni.com/idnet/ at
href="http://zone.ni.com/idnet97.nsf/9b2b33e1993d877786256436006ec498/539916348394adc7862568ab005fbb....
If you do need IVI, then I'd suggest you try NI's IVI-C driver for this instrument, also on http://ni.com/idnet/ at this link. This includes LabVIEW Wrapper VIs for the driver.
If you want to use Agilent's driver, did they provide LabVIEW support with their driver? That is, did they include LabVIEW wrapper VIs? If so, you might try just calling the "AGE4437B InitializeWithOptions.vi" directly and see if you get an error. If they did not provide wrapper functions, I'd call them up and ask if they can give them to you.
I hope this helps. Let us know what you figure out.
Brian

A Method Not Allowed error occured communiting to server

Log on to Workspace URL gone to File>Preferences the followin error occurred
URI: http://oracle.vision.com:19000/hfm/GlobalWorkspaceNav/bpm/modules/com/hyperion/hfm/web/prefs/Adf.asp
Status: 405 - Method Not Allowed
Content: text/html; charset=utf-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>IIS 7.0 Detailed Error - 405.0 - Method Not Allowed</title>
<style type="text/css">

</style>
</head>
<body>
<div id="header"><h1>Server Error in Application "DEFAULT WEB SITE/HFM"</h1></div>
<div id="server_version"><p>Internet Information Services 7.0</p></div>
<div id="content">
<div class="content-container">
<fieldset><legend>Error Summary</legend>
<h2>HTTP Error 405.0 - Method Not Allowed</h2>
<h3>The page you are looking for cannot be displayed because an invalid method (HTTP verb) is being used.</h3>
</fieldset>
</div>
<div class="content-container">
<fieldset><legend>Detailed Error Information</legend>
<div id="details-left">
<table border="0" cellpadding="0" cellspacing="0">
<tr class="alt"><th>Module</th><td>StaticFileModule</td></tr>
<tr><th>Notification</th><td>ExecuteRequestHandler</td></tr>
<tr class="alt"><th>Handler</th><td>StaticFile</td></tr>
<tr><th>Error Code</th><td>0x80070001</td></tr>
</table>
</div>
<div id="details-right">
<table border="0" cellpadding="0" cellspacing="0">
<tr class="alt"><th>Requested URL</th><td>http://oracle.vision.com:80/hfm/GlobalWorkspaceNav/bpm/modules/com/hyperion/hfm/web/prefs/Adf.asp</td></tr>
<tr><th>Physical Path</th><td>E:\Oracle\Middleware\EPMSystem11R1\products\FinancialManagement\Web\HFM\GlobalWorkspaceNav\bpm\modules\com\hyperion\hfm\web\prefs\Adf.asp</td></tr>
<tr class="alt"><th>Logon Method</th><td>Anonymous</td></tr>
<tr><th>Logon User</th><td>Anonymous</td></tr>
</table>
<div class="clear"></div>
</div>
</fieldset>
</div>
<div class="content-container">
<fieldset><legend>Most likely causes:</legend>
<ul> <li>The request sent to the Web server used an HTTP verb that is not allowed by the module configured to handle the request.</li> <li>A request was sent to the server that contained an invalid HTTP verb.</li> <li>The request is for static content and contains an HTTP verb other than GET or HEAD.</li> <li>A request was sent to a virtual directory using the HTTP verb POST and the default document is a static file that does not support HTTP verbs other than GET or HEAD.</li> </ul>
</fieldset>
</div>
<div class="content-container">
<fieldset><legend>Things you can try:</legend>
<ul> <li>Verify the list of verbs enabled for the module handler this request was sent to, and ensure that this verb should be allowed for the Web site.</li> <li>Check the IIS log file to see which verb is not allowed for the request.</li> <li>Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here. </li> </ul>
</fieldset>
</div>
<div class="content-container">
<fieldset><legend>Links and More Information</legend>
This error means that the request sent to the Web server contained an HTTP verb that is not allowed by the configured module handler for the request.
<p>View more information »</p>

Please post this to the BI+ or HFM Forum.

JDBC 2.0 method not implemented error using bea jDriver for MS-SQLServer 2000

I'm trying to reconfigure WebLogic Portal 7.0 (Platform 7.0 SP2) to run on MS SQLServer
2000. According to the supported platform docs, the MS JDBC driver is not supported
by Portal, hence I'm using the BEA jDriver for SQLServer.
I'm now getting the following error when starting up Weblogic Portal which requires
a re-sync with the EBCC before the applications will work.
<28-Aug-03 09:28:30 BST> <Error> <Data Synchronization> <000000> <Application:
portalApp; Corrupted data encountered in the persistent store; PLEASE RE-SYNCHRONIZE
YOUR APPLICATION DATA WITH MODE "refresh-from-client" BEFORE CONTINUING! Failure
to do so may result in incomplete or otherwise corrupted server state.
Exception[com.bea.p13n.management.data.repository.PersistenceException: Failed
to refresh JDBC Persistence Manager.] - with embedded exception: [java.sql.SQLException:
java.sql.SQLException: This JDBC 2.0 method is not implemented] at com.bea.p13n.management.data.repository.persistence.JdbcDataSource.refresh(JdbcDataSource.java:506)
Has anyone else come across this problem and know how to resolve it. I have tried
using the MS JDBC Driver on the off chance that it would work, but this also produced
SQL Exceptions with the persistance store and would not work at all even after
syncing with the EBCC

Jim,
Thanks, I'm awaiting for my account to be enabled with customer contract support.
When this is done I will raise a case and send files as requested.
In the mean time it's worth noting that these settings have been made. Connection
to the DB is fine, the createDB, loadads, loaddocs and sync etc all worked fine.
The problem only exists when restarting the server and the portal persistance
store is trying to be refereshed. Once EBCC is re-synced all the DB access works
fine.
Steve
Jim Litton <reply@newsgroup> wrote:
Please open a support case and send in your set-environment.bat,
db_settings.properties, and config.xml from your domain directory after
trying the following.
Given that your operating system is Windows for performing all database
operations like create_db, loaddocs, sync. (because you should not
bother trying to run them on with UNIX).
Restore your set-environment.bat to it's original state. It does not
need to be touched.
Uncomment the MSSQL section in db_settings.properties.
database=MSSQL
db_version=2000
jdbcdriver=weblogic.jdbc.mssqlserver4.Driver
server=@MSSQL_SERVER@
port=@MSSQL_PORT@
dblogin=@MSSQL_USER@
dbpassword=@MSSQL_PASSWORD@
connection=jdbc:weblogic:mssqlserver4:@MSSQL_SERVER@:@MSSQL_PORT@
The dataSyncPool entry in config.xml should appear as:
<JDBCConnectionPool
Name="dataSyncPool"
DriverName="weblogic.jdbc.mssqlserver4.Driver"
URL="jdbc:weblogic:mssqlserver4:@MSSQL_SERVER@:@MSSQL_PORT@"
Properties="user=@MSSQL_USER@;password=@MSSQL_PASSWORD@"
Password="@MSSQL_PASSWORD@"
InitialCapacity="1"
MaxCapacity="5"
CapacityIncrement="1"
RefreshMinutes="99999"
ShrinkingEnabled="false"
Targets="sampleportalServer"
TestConnectionsOnReserve="false"
TestTableName="WEBLOGIC_IS_ALIVE"
/>
-- Jim

Error: "Function or method not supported." when using RF List Mode on NI 5673E

Hi,
I am trying to use the RF List Mode in NI RFSG 5673E. I tried running the sample code "RFSG Configuration List Frequency and Power Sweep.vi" but an error would show up:
"Error: niRFSGCreateConfigurationList.VI <ERR> The LO reported the following error: Function or method not supported." with the error code: BFFA4239.
I also tried running other sample codes that contain the Configuration List VI's but the same error appeared. I am using NI RFSG 1.8.5.
I would really appreciate any help on this. Thanks!

Hello jdlabrador,
I setup a 5673E here and tried to run the same example. I did not encounter an error.
Other reports I've found pertaining to this error usually involved a large number of steps - there was not enough space on the hardware to accommodate them. The error text you're seeing is a little different in that it states that the Create Configuration List method isn't supported for the LO.
Do each of the modules in your 5673E (5450, 5611, 5652) pass a self-test in MAX?
Have you associated the 5450 and 5652 with the 5611?
Could you post a screenshot of the fully-expanded Devices and Interfaces tree from MAX?
Since RFSG 1.9.5 is available, it may be a good first-step to upgrade to it.
Best regards,
Matthew H.
Applications Engineer
National Instruments

JDBC/RMI driver does not support BLOB data type

WLS 5.1 JDBC/RMI driver does not support BLOB data type. It is said in the Weblogic e-doc.
I am using DataSource for database connections, meaning JDBC/RMI driver is actually producing
database connections. I need several columns of BLOB types in my Oracle tables.
Should I use the "JTS" driver instead in order to have the BLOB types supported ?
Thanks for help.
[att1.html]

The error java.rmi.UnmarshalException seems to indicate you are somehow accessing the data-source over RMI, this seems odd. Are you running TopLink on a client and trying to connect to a WebLogic DataSource on the server?
Maybe try connecting directly to the DataSource without going through TopLink and see if you encounter the same issue.
You could also look at the TopLink WebLogic Examples and see how their configuration is different than your own.

Intel Mac 10.4.x "Connection Method not supported -9786"

we have a customer with the new intel powerbook and tiger system.
but if he want to print via tcp/ip he get this error on the screen:
"Connection Method not supported -9786"
i could nowhere found this error code.
any ideas ????
andy
powerbook g4 Mac OS X (10.4.6)

Hi Andy,
I just read your posting from two weeks ago and thought I would add some info.
Yesterday I had a customer suffering the same problem. They had just purchased an iMac w Intel and were attempting to connect to a Canon iR4570. They had other PPC Mac's which were running varying versions of 10.4 and were all printing okay. But this iMac was getting the error -9786.
I found that he was trying to connect via IPP, but entering the queue name as LP (which is what you do for LPR connections). By changing the queue to socket://ip address:9100 the error was resolved.
The thing to note about this situation was that since this was the first printer he was adding to his Mac, the protocol was defaulted to IPP. With the previous driver installations he had performed on the other Mac's, the protocol was defaulted to LPR. This would have been due to this protocol being the last one used previously. But the customer had only been taught to add the IP address and the queue name and wasn't aware of the protocol menu...

POST method not supported by this URL

Hello gentlemen,
          We are trying to migrate our servlets from another Web Application
          Server (IBM WebSphere 2.02) to Weblogic 4.5.1.
          A servlet that did work fine with WebSphere, now produces the "POST
          method not supported by this URL" error under Weblogic.
          Of course, we implement doPost method in our servlet.
          Any idea to fix this problem? thank you.
          emanuele


          Emanuele--
          In the ICSessionServlet file you are posting the data to ICIdentification servlet which is
          again a servlet
          So you need to register this servlet in weblogic.properties file before you post something to
          this servlet.
          Also the way you are calling the servlet is totally wrong from weblogic standpoint
          You don't need to specify the package name in weblogic(this is OK in java web server) for e.g.
          icdoor.myservlet.session.ICIdentificationServlet.
          Because we are registering the servlet with full package name in properties file so we don't
          need to mention the package
          name here..
          Call the servlet in the following way or whichever way is suitable for you.
          Here is how i'm calling ICIdentificationServlet
          http://localhost:7001/ICIdentificationServlet
          Here is the output i'm getting after entering user name/password
          "Welcome Startfighter"
          Requested URL
          http://localhost:7001/Stupida
          Hope this helps
          Kumar
          emanuele wrote:
          > Here's the source code for a servlet producing "HTTP method POST is not
          > supported by this URL".
          >
          > I have registered servlet Stupida in the file weblogic.properties. This
          > servlet subclass the ICSessionServlet.
          > The service() method of ICSessionServlet ask for a userid and a password
          > (user and password are not verified, anyway) and then calls the doPost()
          > method of ICIdentification servlet. This one displays a sort of "Welcome
          > page" and then the calling URL. (if it works fine...).
          >
          > On WebSphere, it works. On Weblogic, it doesn't.
          >
          > Any idea?
          >
          > emanuele
          >
          > "Kumaraswamy A." wrote:
          >
          > > can you post the stacktrace , also if possible send your java file
          > > too!..
          >
          >

Datatype : 25 not supported error while saving Logical Query in BIP Dataset

Hi All,
I have created a nested logical Query in OBIEE Publisher Datamodel using parameters.
Here is the simple query :
Select name, revenue, date from
select "SubjectAreaName"."TableName"."Name" name,
case when :Date > date '2012-01-01' then "SubjectAreaName"."TableName"."Revenue" else NULL end Revenue,
date date
from
"SubjectAreaName"
where
date = :Date
) T1
Note - :Date is the parameter. When I try saving this dataset as-is, it throws me Datatype : 25 not supported error. But, when i replace the parameter :Date with actual date, then the query works. Also, the inner query works with or without parameters. The issue arises when I use the outer query and the parameters.
Please let me know if you have come across such a problem ?
Any help on this regard would be highly appreciated.
Thanks
Swarna

ya i can understand we wont do the sql logic at the data model part as some time performance issue may come when comparaed to sql run in package and sql running in data model . so i have mostly done using package and i will just do select * from table in the data set of data model so i didn't face any issue's like this .
once check this tutorial may be you already
i use to create parameters like this i didn't face any issue
SELECT * from TEST where ID=:p_id
http://st-curriculum.oracle.com/obe/fmw/bi/bip/bip11g/gettingstarted/gettingstarted.htm

CS4 install problem "you cannot run...architecture not supported" error

Just received my copy of CS4 (Mac) from amazon.com. Installed it. But could not get it to run. Got a "You cannot run....architecture not supported" error message. Can't understand why? This is my first version of Photoshop CS. Didn't install CS3...etc. Nor did I previously install the "master" edition. And I am running a MBP 2.5GHz laptop. So it has to be software related. A corrupt file perhaps?
I also cannot install Adobe AIR. Suddenly 3 windows pop up. Telling me I can't install AIR.
Not happy. Expensive software not running. Not good. :P What gives???
Please help me soon!

Where were you yesterday Buko?? :) Where would one find the "CS4 Cleanscript" any how? Would have been nice if you provided a link. Heh...
Any how. Last night. I did d/l the trial version of CS4 Extended. Installed it. Then read the READ.ME file. Stresses that you MUST use their uninstall program. That you can't simply drag the folder to the TRASH (or use AppDelete or AppZapper...as you would be doing the same thing pretty much). So, I used Adobe's CS4 uninstaller. Did a very thorough job of removing the right files.
I managed to sucessfully install my copy of CS4. I even got the proper SETUP dialogue box this time (6 tabs). Previously only 3 tabs were visible. This one asks you to input your serial # and even register before you finish.
Now I see the blue PS folder icon. Have copied a few PS program icons to my dock. Working now as it should.
Moral of the story? Read the READ.ME file!! And use proprietary uninstall programs for huge complicated programs like PS CS4. :) Later guys.

AFP fails to connect to a PC volume and gives a "version of the server you are trying to connect to is not supported" error message.

AFP fails to connect to a PC volume and gives a "version of the server you are trying to connect to is not supported" error message.
Has anybody come across this error and found a fool-proof solution? I have found some stuff on the web but nothing seems to work. In particular this one on the Apple Help doesn't:
http://support.apple.com/kb/HT4700
I have a W2K3 server where the volume is. It's a new Mac with OSX 10.8 and is connecting with AFP (I don’t want to move to SMB yet). There are older Macs with lower OS and all of them work fine. I have checked all the basic stuff and it is set-up correctly (hosts file on Mac, network, etc.).
Any help greatly appreciated,
Cheers,
Ian

This may work for you:
http://www.zdnet.com/mavericks-smb2-problem-and-fixes-7000022519/

Cure for "501 Method Not Implemented" error at site in Firefox but not Chrome or IE?

I am receiving a "501 Method Not Implemented" error message at a site in Firefox but not in Chrome or IE. How can this be cured?

Do you get that error if you access the site or if you click a link to got to another page?
You can reload the page and bypass the cache with:
* Press and hold Shift and left-click the Reload button.
* Press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
* Press "Cmd + Shift + R" (MAC)
See [[Keyboard shortcuts]] and [[Mouse shortcuts]]
* "Clear the Cache": Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now"
* "Remove the Cookies" from sites that cause problems: Tools > Options > Privacy > Cookies: "Show Cookies"
Start Firefox in [[Safe Mode]] to check if one of your add-ons is causing your problem (switch to the DEFAULT theme: Tools > Add-ons > Themes).
* Don't make any changes on the Safe mode start window.
See [[Troubleshooting extensions and themes]] and [[Troubleshooting plugins]]

JDBC-ODBC Bridge does not support Unicode UTF-16

Hi
I'm using Jdeveloper 10.0.3 IDE in order to develop an application for data transformation between MS Access 2003 (source) and Oracle 10g (destination). Clients use Windows XP.
JDBC-ODBC Bridge still does not support Unicode UTF-16 which is the Charest used by MS Access 2000/2003.
Note that when I changed locale in regional setting, destination Connection to Ora10g failed to open a connection, it works only with English locale, so I can't change my locale information.
How can I read Unicode from source DB?
Any help would be appreciated. I look forward to see your response.
Thanks,

i also heared that JDBC-ODBC Bridge still does not support Unicode UTF-16,
but i guess this is not in my case.That's the key in fact. JDBC-ODBC Bridge does not support UTF-16, which is the charset used by MS Access 2000/2003.
or do i need to use a third party driver for jdbc odbc bridge?Free library at http://jackcess.sourceforge.net/
Commerical JDBC driver at http://www.hxtt.com/access.html
Yonghong Zhao
System Analyst
www.hxtt.com

Cannot create application - 405 Method Not Allowed error

Installed 11.1.2.1. Tried using EPMA to deploy app. Getting abort with the Method Not Allowed Error. Tried using Classic and getting the same error. Some of the details says "Server Error in Application "DEFAULT WEB SITE/HFM", "The page you are looking for cannot be displayed because an invalid method (HTTP verb) is being used." Any thoughts on possible causes?

Hi Fsotto,
The below document would resolve the issue.
New Install on IIS 7, Cannot Access HFM from Workspace 404.3 Error in IIS Logs on HFM Web Server (Doc ID 1285684.1)
Hope this helps,
Please feel free to mark the answer as Helpful Answer/ Correct Answer should you find the relevant posting helpful so that it also helps us in keeping track of the answered queries.
Thank you,
Charles Babu J

Jabber 4.4 "Graphics card or driver not supported" error on one machine but not another.

Hi, I looked at the KB document but the email link on it no longer works.
I have two end-users using Jabber 4.4 on identical machines, same specs, same driver build and OS image. One gets the "Graphics card or driver not supported" error, the other does not.
We have two DellOptiPlex 7010's,
Both had 2 instances of AMD Radeon HD 7470 - they are dual monitor machines.
In both cases the driver version 8.922.0.0, Driver Date 12/6/2011. This is the latest Dell has on their website.
On one machine when I run a fresh install for Jabber for TelePresence 4.4 it works fine. But on another the user first gets
"supportabilitytest.exe has stopped working
A oriblem cause the program to stop working correctly. Please close the program."
Then when that's closed out we get:
"Graphics card or driver not supported!
New features in this version of Jabber Video are not supported by your computer's graphics driver.
Update to the newest graphics driver available and run Jabber Video again."
I can't believe it's just a matter of upgrading the drivers because in this case one machine with identical drivers works.
I appreciate any insights, thanks !

Hi ksouthall,
It sounds like the openGL supported version did not install on the one that is failing. There isn't much we can do regarding that error. Best practice is to always upgrade to the latest manufacturer's available driver. Client requirements are below.
Windows 7 (32-bit or 64-bit), Vista, or XP (SP 2 or newer), with OpenGL 1.2 or newer.
For 720p HD video calls, Intel Core2Duo @ 1.2GHz or better.
For VGA video calls, Intel Atom @ 1.6GHz or better.
Webcam, built-in or external. You need an HD webcam if you want other callers to see you in HD.
Broadband Internet connection with a recommended bandwidth of 768kbps upstream and downstream. You need about 1.2Mbps upstream and downstream for 720p HD video calls.
Regards,
Jason

JDBC 2.0 method not supported Error occuring in WL 6.1 sp1

Similar Messages

Maybe you are looking for