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

Similar Messages

  • Firwirer connections are not supported?

    My ipod reads "firewire connections are not supported. To transfer songs connect the USB cable provided."
    I tried to copy a CD to my ipod. It was a copy of a CD from a friend from his ipod whch I guess is not compatable with mine. He ahs a PC. I have a mac. He ahs an old 60g ipod I have a new ipod culor 30 gb. My guess is that he has firwire connections and I have USB
    I now cant turn off the ipod. I can play it but the battery goes very quickly.
    It constantly reads the above message i.e firewire connected are not supported/
    I HAVE RESTORED FACTORY SETTINGS AND DELTED THE CD FROM MY ITUNES. WHAT can I do?

    Firewire connections are not supported. To transfer songs, connect the USB cable provided.
    That is the same message I'm receiving on my iPod as of yesterday. We've been on vacation for a week and the iPod has worked flawlessly, just like it has since the day I got it. That is, until yesterday.
    We were driving down the freeway when it started pausing, skipping, and generally giving me grief. I listen to it in the van via a connection through the cassette tape player. I've been using this set up since the day I got my 80gb video iPod.
    For whatever reason, that message simply started popping up. I can't seem to get the center button trick to work most of the time, but occasionally it will. No matter what I do, I can't turn off my iPod any longer. It has to simply go to sleep.
    So, I got home and the first order of business was using the option in iTunes to wipe the iPod clean, reset it to factory defaults, then reload all 60gbs worth of data onto it. I did that. I play around with it a bit this morning, but with nothing connected to it. It seemed to work fine and would turn off as normal.
    I connected it to the cassette adapter a short while ago, got about 2 miles down the road, now its doing the same thing again. Its giving the same error message, skipping/pausing, and won't allow me to turn it off.
    Help?

  • Error message: "FireWire connections are not supported.  To transfer songs"

    I recently purchased a Monster iCarPlay to play my ipod in my car. I have had no problems until recently. Upon disconnecting my ipod from the iCarPlay wire, I the following message popped up: "FireWire connections are not supported. To transfer songs, connect the USB cable provided." It also prompts me to click the center button to dismiss the message. However, I'vd followed these instructions, and the message does not go away. Does anyone know what I can do to resolve this problem? Or is it anything to worry about?

    That is the message you see when you attach a 5th gen iPod to a computer using FIREWIRE. so... i suspect that for some reason, the 3rd party iCarPlay device must be confusing the iPod into thinking it is being docked or attached to a data line of some type and not simply charging.
    As for the sudden occurrence of the message, it does seem strange however, keep in mind that you are using a 3rd party device that may not be supported or endorsed by Apple at all.
    Beavis2084

  • Is there any way to play an iTunes rented movie from my mac on a tv that does not support HDCP?

    Is there any way to play an iTunes rented movie from my mac on a tv that does not support HDCP?

    No.

  • Since the iPod Lightning connection is not supported, how can you take videos from your iPod 5th Gen to your tv?

    Since the iPod Lightning connection is not supported, how can you take videos from your iPod 5th Gen to your tv?

    Lightning TV out
    - Via Airplay to an Apple TV.
    or one of these cables.
    - http://store.apple.com/us/product/MD826ZM/A/lightning-digital-av-adapter?fnode=3 a
    - http://store.apple.com/us/product/MD825ZM/A/lightning-to-vga-adapter?fnode=3a

  • Firewire connection is not supported. Use USB to transfer songs...

    Got message on my ipod saying "Firewire connection is not supported. Use USB to transfer songs" and then it says "Press Center to dismiss"
    Restarted the ipod no use!
    Connected with my PC no use! (its just charging) does not update of hooked to itunes)
    Any ideas how i can fix this??
    P.S I have tried cleaning the docking and the cable for any dirt still no use!

    Does it give you this error all the time or only when plugged in with the cable?
    If it does it all the time, have you checked the dock connector for bent pins?
    If it only does it when plugged in, have you tried a different cable?
    Patrick

  • "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

  • 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

  • Can't listen for connections - Operation not supported

    Hi,
    We have install OSB Client on HP-UX 11i V2 HP rx5670 Server as per Oracle Secure backup Installation Guide.
    But we are getting following error message. Please help us to solve the issue:
    2010/12/29.10:23:02 can't listen for connections - Operation not supported
    # /sbin/init.d/OracleBackup start
    Starting Oracle Secure Backup services daemon.
    2010/12/29.10:23:27 can't listen for connections - Operation not supported
    Thanks
    Khairul/Bangladesh

    Have a look at the observiced.log file to see if that has any more detail, this is in /usr/tmp.
    I would check to see if there is something else on the system that is using TCP port 400 or 10000. On Solaris I've seen the webmin installation using port 10000. Both those ports need to be free for OSB to be able to start.
    With OSB stopped, you can "telnet <hostname> 400" and "telnet <hostname> 10000" to see if it connects. If it does then something is listening on that port.
    You should be able to do "netstat -na" as well, to show you listening ports.
    Rich

  • 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!..
              >
              >
              

  • When i plug in my iphone 4s to my Xtreme Mac luna sst it says accessory not supported by iphone.  Why is it doing this??

    when i plug in my iphone 4s to my Xtreme Mac luna sst it says accessory not supported by iphone.  Why is it doing this??

    Hello AliHoward,
    You may need to completely remove iTunes, QuickTime, and other Apple software from your system prior to reinstalling. The following articles (one for Windows XP, the other for Windows Vista/7) detail the removal process. I'll also link you to the latest version of iTunes for Windows (64bit specific installer).
    Removing and Reinstalling iTunes, QuickTime, and other software components for Windows XP
    http://support.apple.com/kb/HT1925
    Removing and reinstalling iTunes, QuickTime, and other software components for Windows Vista or Windows 7
    http://support.apple.com/kb/HT1923
    iTunes 11.0.4 for Windows 64
    http://support.apple.com/kb/DL1615
    Cheers,
    Allen

  • Mac Pro to Samsung HDTV - "Mode not supported"???

    Alright, so I have just received my new Mac Pro in the mail yesterday and wanted to hook it up to my television - a 1080p Samsung (Samsung LN-T4671F) HDTV. I am using a DVI-to-VGA cable. I feel I should probably explain the entire situation so that it's all clear.
    The first time I started the computer after plugging it into the TV, the Apple logo with the Loading, spinning thing (not the multicolored wheel) showed in beautiful 1920x1080. After loading, the screen jumped to a lower resolution for a second and then went black, finally giving me a "Mode not supported" error. Thinking it was just a little hiccup, I restarted the computer and after the Apple logo screen, it showed me a screen on how to put batteries in my mouse (or something along those lines, I didn't really look), and then it had me set up my wireless keyboard. After this, it showed me the WELCOME video and allowed me to log on to my computer and start using it.
    After about 15 minutes, I was going through the system prefs and came across display. Thinking maybe I should lower the resolution to better see text, I clicked on a lower resolution around 1600xsomething. The screen went black and gave me the "Mode not supported" error again. I thought I could just wait a few seconds and if I didn't confirm the resolution, it would go back...but it never did. After trying to restart my computer a number of times and receiving the error message each time, I booted in Safe Mode, which I am in right now.
    I went into the sys prefs and made sure the resolution was set to 1920x1080, which it already was, and restarted the computer. Error again. I went into the settings of my TV and went to PC and had it auto correct the resolution to the input. Error again. I have been running in Safe Boot since - no sound is annoying - and enjoying the display in full 1920x1080 (1080p)...so the set obviously supports it (and the manual says it does too).
    My video card is an NVIDIA GeForce 8800 GT. What's most annoying is that it's pretty obvious that the display supports this resolution and yet won't allow it to work outside of Safe Boot mode.
    Please help

    Had the same problem with an AOC 1080p TV, trying to connect to it using VGA cable.
    Ivan's earlier post clued me in to solution:
    - Plug in the TV, get the "Mode not supported" message on the TV
    - Open the Display Preferences, you should see the display preferences for the laptop "Color LCD" monitor. Click the "Gather Displays" button - this should bring the display preferences for the TV behind the laptop preferences window. Switch to the TV's display preferences window.
    - In the TV's display preferences window, switch refresh rate down to 59.9 Hertz (your TV may need different refresh rate, but on mine I only get options for 59.9 or 60).
    That did it for me!

  • I am unable to sync my iPhone4 iCal to my Mac iCal. Snow Leopard does not support the Cloud. What do I do?

    I am unable to sync my iPhone4S iCal to my Mac iCal. Snow Leopard is my OS and it does not support the cloud. What do I do?

    To makeuse of iCloud you will have to upgrade your Mac to Lion or Mountain Lion, provided it meets the requirements.
    The requirements for Lion are:
    Mac computer with an Intel Core 2 Duo, Core i3, Core i5, Core i7, or Xeon processor
    2GB of memory
    OS X v10.6.6 or later (v10.6.8 recommended)
    7GB of available space
    To purchase it you will have to ring Apple at the number given at the bottom left of this page.
    The requirements for Mountain Lion are listed here:
    http://www.apple.com/osx/specs/
    It is available from the Mac App Store (in Applications).
    You should be aware that PPC programs (such as AppleWorks) will not run on Lion or above; and some other applications may not be compatible - there is a useful compatibility checklist at http://roaringapps.com/apps:table

  • 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>>

  • Mac Book With No Connection-No Linksys Support :(

    Help Please!
    Have MAC book and it still can not get connection.  I have been on hold for hours and hours and with live chat for hours and hours, they don't get it at all and we keep doing the same thing over and over.
    Have the WRT54G with the updates, kept losing connection 3-4 times per day, had to reset modem, router and shut down the computer each time.  Called in and they had me make some changes to advance settings and the channel (BTW does these changes go back to the orignal ones if you have to do a reset again - because that is what is happening)  Also wanted help with the security, they had me do the WEP,and now the MAC book will not connect at all keeps wanting a password, no one at Linksys wants to take any real knowledge of the MAC - one problem i too don't know much about them, my daughters talked me into getting it so just learning.  My desktop Dell is hardwired to router and has been keeping the connection, it is always the MAC that would drop so we would do the restart. I am sure you guys have covered this, but even in some of the posts i just don't get the procedure.  Please Please some kind people on this board help me out.  Also, can email direct at [email protected]

    Hi,
    What is the model of the router? if it falls on wrt54g v5 or v6 ; or wrt54gs v5 or v6..You need to upgrade the firmware of the router into the latest firmware..And needs to reset the router back to factory default and reconfigure so that will work again with the modem ...
    And if still it will not work, check for the ip address if it is getting an ip of 169.254.x.x it means that the router is not getting the correct ip address..so you need to assign a static ip address on your mac computer ...

Maybe you are looking for

  • F-04 (Vendor Clearing using BAPI-BAPI_ACC_DOCUMENT_POST)

    Hello all, i am using a BAPI - BAPI_ACC_DOCUMENT_POST for posting and clearing vendor payments but problem is that i m getting error that 'Account 3252995 in company code 5219 cannot be directly posted to', can anyone please help me? Regards saurabh.

  • Timesten user defined function problem

    create or replace FUNCTION FACTORIAL   n IN NUMBER          RETURN NUMBER IS val NUMBER :=1; tem number :=n; BEGIN     while tem>1 LOOP     val:=val*tem;     tem:=tem-1;   END LOOP;   RETURN val; END FACTORIAL; I create a function like this. And I  t

  • When I click a RAW file in Bridge CC, only a 40x60 px thumbnail appears in ACR.

    I am having a problem opening RAW files by clicking on them in Bridge.  ACR launches but only a tiny 20x30px image appears in the main ACR editing screen.  In Lightroom, the same RAW files open correctly without any issues.

  • What should be the logger name for Dispatcher Flush agent?

    Hi, I was trying to setup logging configuration so that the log for Replication agents can be saved on file system. I was able to do it using the logger com.day.cq.replication.Agent.publish. What would be the logger for Dispatcher Flush Agent if I ne

  • Aperture and Olympus E-1

    I just purchased a MacBook and are waiting for Aperture 1.1. I have no experience with Apreture other than a quick test run in the Apple store. I've scanned the web, but there is no information on the two working together. Anyone here using this comb