"Import string" method not supported in LabVIEW 7.1

We have made an application that support multi-language (English, French, etc.). In LabVIEW 6.1, we used the "import string" VI method to support this option. The method was executed just before to open front panel. The code was based on this example found in NI Developer Zone:
Translation/Localization Tools in LabVIEW
(http://sine.ni.com/apps/we/niepd_web_display.disp​lay_epd4?...
But surprise in version 7.1, this method can't be loaded without the diagram block. So the built application doesn't support it! It works only in the development interface. Why this change?
If someone has an idea to solve this, let me know.

If you build that example into an EXE under LabVIEW 7.1, it should work fine as long as you add the non top-level VIs as Dynamic VIs and add the language files as Support Files when you create the executable, making sure to specify in "Custom Destinations" that you want the string files to end up in the same directory as the EXE.
Your point about the method requiring the block diagram is correct, according to the help for the method. However, I think the diagrams will be available to the run-time engine as long as you haven't purposefully removed them prior to creating the EXE in the manner described above. Maybe someone else can chime in on this point, because I know the App Builder changes a lot with every new major LabVIEW version (and sometimes, with minor versions too!).
In any case, I just did a test where I downloaded the example you referenced, created a .BLD file as I indicated above, and got a successful executable that was able to use the Import VI Strings method to load the desired language at run-time.
Regards,
John

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

  • Exchange 2010, khi: failed to execute Troubleshoot-DatabaseSpace.ps1 Error formatting a string: Format string is not supported

    Hi,
    Exchange 2010 MP fails to run Troubleshoot-DatabaseSpace.ps1. Results in a Warning with "Error formatting a string: Format string is not supported". The EventNumber is 402. The Microsoft article it points to is useless at http://technet.microsoft.com/en-us/library/749e0eac-ebb2-41e3-8fa2-4a03a1bd3571.aspx 
    Run ".\Troubleshoot-DatabaseSpace.ps1 -Server MailboxServer.domain.com -MonitoringContext" and works fine.
    Any help appreciated.
    thanks

    Hi,
    Before the newer MP release, we can disable  these 4 monitor via override and this should not run the Troubleshoot-DatabaseSpace.ps1 :
    KHI: Failed to execute Troubleshoot-DatabaseSpace.ps1.
    KHI: The database copy is low on database volume space and continues to grow. The volume is under 25% free
    KHI: The database copy is low on database volume space and continues to grow. The volume has reached error levels under 16% free.
    KHI: The database copy is low on database volume space and continues to grow. The volume has reached critical levels 8% free.
    Alex Zhao
    TechNet Community Support

  • 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

  • Workflow manager 1.0 : runtime error 400 running Add-WFHost "The api-version in the query string is not supported"

    Installing Workflow Manager 1.0 for SharePoint Server 2013 SP1 everything is fine until the last step of the configuration and last powershell command : 
    Add-WFHost -WFFarmDBConnectionString 'myconnectionstring' -RunAsPassword $WFRunAsPassword -EnableFirewallRules $true -SBClientConfiguration $SBClientConfiguration -CertificateAutoGenerationKey $WFCertAutoGenerationKey -Verbose;
    gives me the following error : 
    Add-WFHost : The remote server returned an error: (400) Bad Request. The api-version in the query string is not supported. Either remove it from the Uri or use one of '2012-03'..TrackingId:412684e3-3539-468e-91e6-17838c6eaa55_GS
    P,TimeStamp:04/04/2014 12:54:11
    At line:1 char:1
    Can't find anything about this subject except this
    thread which does not help me that much in SharePoint dev env ...
    Removing workflow manager 1.0 and service bus (leave the farm using wizzard, remove binaries and databases) does not help.
    Who already faces this issue and how can I try to resolve it ?
    Best regards !
    Alexandre DAVID

    The API version is hardcoded in Microsoft.ServiceBus.dll, which ships as part of the Service Bus. Each version of this lib has a different string.
    If you install workflow manager 1.0, here are the pre-requisites:
    .NET Framework 4 Platform Update 3 or .NET Framework 4.5
    Service Bus 1.0
    Workflow Client 1.0
    PowerShell 3.0
    The following are the pre-requisites to configure Workflow Manager 1.0
    Instance of SQL Server 2008 R2 SP1, SQL Server Express 2008 R2 SP1, or SQL Server 2012.
    TCP/IP connections or named pipes must be configured in SQL Server.
    Windows Firewall must be enabled. [Windows Firewall is Off on target server]
    Ports 12290 and 12291 must be available.
    Here are the reference for installing and configuring Workflow Manager 1.0:
    http://lennytech.wordpress.com/2013/06/02/installing-workflow-manager-1-0/
    http://lennytech.wordpress.com/2013/06/02/configuring-workflow-manager-1-0/
    http://social.technet.microsoft.com/Forums/en-US/c74507fb-ac2d-405f-b19c-2712b1055708/workflow-manager-10-configuration-service-bus-for-windows-server-the-api-version-is-not?forum=sharepointadmin

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

  • Web service Method not supported

    Hy, i have this serious problem.
    I have any web service method  that in , Visual Composer 7.1, have the suffix "Not supported".
    I don't understand this situation because i can test it on web service navigator with success.
    This is the SOAP request/response from Web service navigator test:
    SOAP request:
    <?xml version="1.0" encoding="utf-8"?>
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <SOAP-ENV:Body>
        <pns:getMaterialDetail xmlns:pns="urn:WsMaterialGetDetailVi">
          <pns:matnr/>
          <pns:werks/>
        </pns:getMaterialDetail>
      </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    SOAP response:
    <?xml version="1.0" encoding="UTF-8"?>
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <SOAP-ENV:Body>
        <rpl:getMaterialDetailResponse xmlns:rpl="urn:WsMaterialGetDetailVi">
          <rpl:Response xmlns:pns="urn:it.futura.lib.ws">
            <pns:returnCode>3</pns:returnCode>
            <pns:returnCodeDescription>Codice Materiale non fornito</pns:returnCodeDescription>
            <pns:returnCodes xmlns:tns="java:sap/standard" xsi:type="tns:Vector">
              <tns:Vector xsi:type="xs:string">0</tns:Vector>
              <tns:Vector xsi:type="xs:string">0</tns:Vector>
              <tns:Vector xsi:type="xs:string">3</tns:Vector>
            </pns:returnCodes>
            <pns:returnCodesDescription xmlns:tns="java:sap/standard" xsi:type="tns:Vector">
              <tns:Vector xsi:type="xs:string">Environment name found: NVP</tns:Vector>
              <tns:Vector xsi:type="xs:string">Dettagli ambiente trovato: NVP</tns:Vector>
              <tns:Vector xsi:type="xs:string">Codice Materiale non fornito</tns:Vector>
            </pns:returnCodesDescription>
          </rpl:Response>
        </rpl:getMaterialDetailResponse>
      </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    Sincerely yours
    Thank's
    Andrea Maraviglia

    Thank's Shay. I'm thinking that the problem is about NWDS for this reason: at the moment i am testing a standard web service present on WAS( http://serverWAS:53000/IciUserService/IciUserConf?wsdl)that with a method ( getAttributes) that return an array of classes on VC and this test is ok.
    So i'm creating an similar web service that return array of classes with my NWDS (vers. 7.0.7..) and wizard but on VC it's don't supported.
    The SOAP Response of standard web service and my web service, have different structure. I'm thinking that the problem is NWDS because the SOAP response is function of the WSDL generated by Wizard on NWDS.
    Thank's in advance.
    Andrea Maraviglia
    Edited by: Andrea Maraviglia on Nov 28, 2008 5:46 PM

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

  • ICompanyService.GetGeneralService(System.String) Method Not found error

    Hi,
    When I am running my code in SAP 2007, I am getting following on calling of UDO.
    Method not found: 'SAPbobsCOM.GeneralService SAPbobsCOM.ICompanyService.GetGeneralService(System.String)'
    I could not understand why this error is occuring, although same code in running very well in SAP 8.8 and 8.81.
    Please suggest me a solutions.

    Hi
    sorry it is mistake from me. Check this SAP note regarding GeneralService it is available from SAP Business One 2007 A SP00 PL46 onwards . Please check you PL version
    How to use the GeneralService functionality to access UDOs via DI API.
    Solution
    The GeneralService allows access to User-Defined Objects (UDOs) via the DI API. Using the GeneralService, you can add, update and delete UDOs. This feature was added in SAP Business One 2007 A SP00 PL46.
    The following is an example of how to add data to a UDO. This example relates to a UDO with the following properties:
    Type = Document
    Unique ID = "Ex_1"
    Name = "EX_DOC"
    User-Defined Field = "Field1"
    Child Object Name = "EX_DOC_LINE"
    User-Defined Field (Child Object) = "Property1"
    Use this (VB.NET) code to add data to the UDO:
               Dim oGeneralService As SAPbobsCOM.GeneralService
               Dim oGeneralData As SAPbobsCOM.GeneralData
               Dim oGeneralDataChild As SAPbobsCOM.GeneralData
                 'Get the UDO by referencing the Unique ID (using the CompanyService Object)
               oGeneralService = oCompanyService. GetGeneralService("EX_1")
                         'Create data for new row in UDO - (Document Table)
               oGeneralData = oGeneralService.GetDataInterface(SAPbobsCOM. GeneralServiceDataInterfaces.gsGeneralData)
               oGeneralData.SetProperty("U_Field1", "A")
               'Create data for new row in the UDO Child - (Document Row Table)
          oGeneralDataChild = oGeneralData.Child("EX_DOC_LINE"). Add()
               oGeneralDataChild.SetProperty("U_Property1", "B")
               oGeneralService.Add(oGeneralData)
    See the following Blog for more information and another example:
               "UDO Access via DI API (in PL46)"
               http://www.sdn.sap. com/irj/scn/weblogs?blog=/pub/wlg/13008
    Regards
    Arun

  • Can't import mpeg video - not supported

    Production Premium user.
    The whole purpose of multitracking against video is useless as I've just found out Audition does not support MPEG MPEG-2.
    I went to the Apple site where I was led to believe that buying the
    QuickTime MPEG-2 Playback Component for Windows
    would give me a fix to the QuickTime component - nope - just wasted £15 on an add-on that doesn't work. The player opens and plays as if it were reading the file but no video (black) - and no audio. Apple, please can I have my £15 back?
    Anyone else really hacked off with this, especially having sat watching a "Senior Evangelist" gush about how great Audition is for Multitacking against video.

    Hey Steve, thanks for your reply, but not to leave you out...
    Your comment "...because I don't do video..."
    Now here's me thinking that Production Premium with Prem Pro and AE etc was geared toward video editors and video producers like me... So the inclusion of an application like Audition is aimed at a wider market. Hey Ho... Rather like Canon finding that their DSLRs could do HDV video (but not very well) but had other USPs.
    Report Back:
    <File> <Sequence... Right Click Edit Adobe Audition...Sequence> <Export without or with Preview Video>
    Defaults to AVI... AVI if left up to its own render is rubbish - pixilated and low def - especially when you're used to working in HDV. And just try undocking the video panel to a 32-inch plasma - oh no...
    Reformatting to H.264 and importing H.264 it just can't handle cross application satisfactorily. Stutter playback - in Audition - and outside using an undocked panel.
    I operate i7 hex intel 970 24GB tri channel RAM and 5 drive HDD with SSD OS on Windows 7.
    This is just not an application which can claim Multitrack mixing to video sync - okay perhaps in the DV and those early days but not now. Rather reminds me of old high-end audio console digital software - always maintained its not the the software but the user. It rather looks like you development guys just didn't think this was important - well not in the short-term.
    Not good enough for my needs. Steve - I don't know what you use Audition for but it's not professsional video applications - as you state. But thank you for replying.
    6/10, and only for the fact it tried but fell over.
    Edit: Forgot to add I'm also running Nvidia GTX580 1.5GB Video Card.

  • Usrp driver 1.3 do not support for Labview 2013 64 bit ??

    Hello, dear all
    Is anyone install the latest USRP driver 1.3 for LV 2013 64 bit ?  I found there is no version for 64 bit LV 2013. 

    Currently the 1.3 driver supports only LabVIEW 2013 32 bit (even on 64 bit computers.)
    The LabVIEW 2014 version will support 64 bit and will be available to download very soon.
    Please check here within the next week or so:  http://search.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/ssnav:drv/q/usrp/

  • ORA-26744: STREAMS capture process "STRING" does not support "STRING"

    Hi All,
    I have configured oracle streams using Note "How To Setup One-Way SCHEMA Level Streams Replication [ID 301431.1]" at schema level
    All the changes are getting reflected perfectly and was running smooth, but today suddenly I faced the below error and capture is aborted
    ORA-26744: STREAMS capture process "STREAM_CAPTURE" does not support "AMSATMS_PAWS"."B_SEARCH_PREFERENCE" because of the following reason:
    ORA-26783: Column data type not supported
    Couple of suggestions on forum are to add a negative ruleset, please suggest me how do i add a negative rule set and if this is added to negative ruleset then how the changes to this table will reflect in target database...?
    Please help me...
    Thanks

    I do not have any idea why it treats your XMLTYPE stored as CLOB like a XMLTYPE binary. From the doc, we read :
    http://download.oracle.com/docs/cd/B28359_01/server.111/b28321/ap_restrictions.htm#BABGIFEA
    Unsupported Data Types for Capture Processes
    A capture process does not capture the results of DML changes to columns of the following data types:
        *       SecureFile CLOB, NCLOB, and BLOB
        *      BFILE
        *      ROWID
        *      User-defined types (including object types, REFs, varrays, and nested tables)
        *      XMLType stored object relationally or as binary XML                   <----------------------------
        *      The following Oracle-supplied types: Any types, URI types, spatial types, and media types
    A capture process raises an error if it tries to create a row LCR for a DML change to a column of
    an unsupported data type. When a capture process raises an error, it writes the LCR that caused
    the error into its trace file, raises an ORA-26744 error, and becomes disabled. For your support
    NOTE:556742.1 - Extended Datatype Support (EDS) for Streams
    to exclude the table:
    NOTE:239623.1 - How To Exclude A Table From Schema Capture And Replication When Using Schema Level Streams Replication
    Sound like a specific patch. You did not stated which version of Oracle you are running.

  • Static methods not supported?

    When I create a static function in netbeans 6.5 like:
    class Conversions
        static function c2f (celcius: Number): Number
            9.0/5.0*celcius+32.0
    }I get the warning that *'static is no longer supported, it will be removed soon, use script-level declarations'.*
    Does anybody know what this means, how do I declare class level functions?
    Besides that, where is a good, uptodate, complete language reference, I get all unknown pages?

    Found it myself, but I think that there's an inconsistency with the javafx plugin and the javafx compiler, because the code in my first message gives a warning, but does run.
    When you change the 'static' into 'public', it behaves as a class method, in the IDE. The following code, does not cause a warning in Netbeans:
    class Conversions {
        public function c2f (celcius: Number): Number {
            9.0 / 5.0 * celcius + 32.0
    print(Conversions.c2f(37.0));But, unfortunately, it doesn't run:
    non-static method c2f(double) cannot be referenced from a static context
    print(Conversions.c2f(37.0));
    1 errorAny suggestions, is there an update (for Netbeans or my javafx) to fix this?

  • Import & Export Strings method

    Hi,
    I have a multilanguage application. I have used export & import
    strings methods. I have one .txt file for each language but when I
    modify something in my vi I must export all again and then modify the
    tags again for each language file... Is there a way that I can modify
    my vi and I don't have to export all again?
    Thanks,
    ToNi.

    As far as i know you need to export strings again only if you have made any changes on front panel.
    exported file is nothing but a xml file so that you can manually edit it instead of exporting everything again (helpfule if you have done very small changes on front panel)
    Tushar Jambhekar
    [email protected]
    Jambhekar Automation Solutions
    LabVIEW Consultancy, LabVIEW Training
    Rent a LabVIEW Developer, My Blog

Maybe you are looking for