FRM-92160: "Version of WEB-Client too old"

HI Gentlemen,
From Frank Nimphius I have got an idea to delete the Oracle jar files on the client PC (--> user --> Oracle Jar Cache). Sorry, it still complains with the above message which I can not find anywhere.
I first performed a brand new install of 9iDS, then installed 10gAS in its own OracleHome, configured formsweb.cfg UNDER 10gAS and edited the rest according to to rules. I added the configuration according to Webutil beta, not production. And that's it. Please help, if I instead configure for Webutil production, do I gain anything? The whole application does not start and hangs on this malicious message.
Thanks in advance, greetings from
Miklos HERBOLY

Maybe change the Home selector to point to the new 10g application.

Similar Messages

  • FRM-92160: Fatal error: web client version is too old

    Hi All,
    We have upgrade the forms and reports from version  from 11.1.2.0.0 to 11.1.2.1.0 so the existing applet (11.1.2.0) still there the cache casing the the "FRM-92160: Fatal error: web client version is too old" issue (The new applet version is 11.1.2.1). but this can be resolved by clearing the java cache.
    As the the end user count is huge, is there any other possible way to get the cache clear when they access the URL for the first time.
    Thanks in Advance
    Salai

    Hi
    maybe you can change default setting in client (user) java option .
    path like ( control panel > java > General > temporary internet files > setting button > unchecked keep temporary file )

  • Web Client too Old

    HI Gentlemen,
    I installed on my XP machine Oracle Forms & Reports Services from 10g AS to regularly deploy my forms and reports. Since then, I get a message like "Web Client too Old" and the application does not start. Earlier it was simply deployed using 9iDS, however, it was highly unstable and I had a lot of problems with printing. However, by starting OC4J Instance ahead brought a relatively stable execution environment.
    My question is: Where can I be wrong? Do I have to go thru the whole 10g AS doc to find out how to launch a simple application? This would be terrible. Can you suggest a workaround to gain time?
    Thanks, kind regards from
    Miklos HERBOLY

    HI Frank,
    Thank you very much. Another important thing: 1. When I earlier only installed 9iDS, it created a program group "Oracle 9iAS" as well and placed some programs into it. Do I still have to install Forms and Reports Services FROM AS, a very big package of about 500 MB unzipped on every client in order to get access to the application via the URL? Or is it enough to install OC4J Instance?
    2. With ONLY 9iDS I also configured (perhaps) Forms Services by editing formsweb.cfg etc. Did I thereby deploy using AS implicitly or was it a non-recommended DS deployment? How can I deploy "USING" AS? When editing those files it is completely transparent to me if I have AS or not! And I could not start 10g AS by emctl start, because it always complained about an invalid argument and accepted nothing!
    So I ame completely jammed, and the doc is unbelievably huge to go thru.
    Thanks, kind regards from
    Miklos HERBOLY

  • FRM-92150 Fatal error web client version is too new

    Need help!!
    OS 2008 64 bit
    1.     Installed Weblogic server 10.3.5
    2.     Installed Forms and reports ONLY 11.1.2
    3.     Configured --> everything worked
    We have a need to run a Discoverer 11G a well. Since Discoverer was not part of original Forms and Reports install, I downloaded and installed Portal, Forms, Reports and Discoverer 11.1.1.2 then downloaded and installed patch set #6 11.1.1.7. Then run config bat and created NEW domain and installed only Discoverer.
    Now when I run the http://localhost:8888/forms/frmservlet?config=prod I get FRM-92150 Fatal error web client version is too new.
    I need both features to work. What is the trick? Any advice is appreciated. Sonya
    Updating Path variable to point to 1st oracle home resolved this issue. SK
    Edited by: user8461308 on May 23, 2013 3:46 PM

    Updating Path variable to original Oracle home resolved this issue.

  • "SQlite Version Error The application has been updated, but your version of SQlite is too old and the application cannot run." What is this all about?? Shall I give up on Firefox?

    When I tried to use Firefox this morning I got this message with exclamation marks.
    "SQlite Version Error The application has been updated, but your version of SQlite is too old and the application cannot run."
    What is this all about?? Shall I give up on Firefox?

    Sorry to hear that. I understand your frustration and I hope they send back a better working N78-3.
    Myself, I count myself lucky. Everything works perfectly for me right now...email, bluetooth, maps, gps, 3rd party apps, battery life, 3G, wifi, etc. etc.
    The only issue I've been having is the dreaded reboots but I believe that may have to do with 3rd party apps. I recently uninstalled Google Search app from my N78 and since then it hasn't rebooted or shown any issues. This seems odd at first but makes sense if you think about the fact that the Google Search app loads itself into memory and runs in the background at all times.
    I did this this past Tuesday night and so far no reboots, crashes or any problems. I'm sure I just jinxed myself but I've been using it heavily over the last few days with no issues. Prior to this, it would usually reboot every 2 days. If it doesn't reboot for another few days I'll be happy.
    I would normally not stand for this but I just love the phone and if I got something else it'd probably be the iPhone 3G which has perhaps more software bugs and issues than the N78-3!!
    Best of luck. Here's hoping they release an update soon.

  • Labview version 7.1 is too old to convert to current Labview version 8.0

    I had developed my Labview code sometime back using LV-7.1 and now I am trying to deploy it on a new PC. The Test Stand version that I have is 3.1. I did everything right and after I installed my deployment package, I get the error that the Labview version 7.1 is too old to convert to current Labview version 8.0.
    I am going to look into converting my code using Labview 8.0, but I am puzzled, why would it matter, as am using the same Labview (7.1) and TestStand (3.1) as before, and getting this error? I also installed the old Traditional DAQ drivers (instead of the DAQmx) and so everything is the same except that the PC is new.
    Shoab
    Attachments:
    ErrorMessage.jpg ‏225 KB

    Hey Shoab,
    Are you getting this when you run the sequence in the Sequence Editor?  If so then I would suggest checking the adapter configurations.  Go to Configure>>Adapters select LabVIEW and click the Configure.. button. Once in there you can change the run-time engine to 7.1.
    Let me know if that helps.
    Regards,
    jigg
    CTA, CLA
    teststandhelp.com
    ~Will work for kudos and/or BBQ~

  • Labview load error code 10:VI version (8.2b23) is too old to convert to the current

    trabajo en la version de LabVIEW 8.2, 20th aniversary edition, Professional y cuando intentaba abrir la parte de examples en la primera ventana me aparecia el siguiente error:
    LABVIEW:VI version is too early to convert to the current labview version.
    An error occurred loading VI "find examples.vi".
    Labview load error code 10:VI version (8.2b23) is too old to convert to the current
    labview version (8.2.1f4)
    luego de la primera intaslacion de la version 8.2b23 tambien me salia el mismo error, desintale y reinstale pero igual, asi que probe instalar un parche que actuliza a la version 8.2.1f4, pero como ven sigo con el mismo problema ademas de intentar mass compile pero no me funcina al parecer son muchos VIs que hay que compilar... tambien busque el LabVIEW conversion kit, pero son para versiones demasiado anteriores agradeceria me ayudaran a solucionar este problema.
    MUCHAS GRACIAS
    ATT: Carlos Andres Rosero, Colombia

    According to this, 8.2b23 is an illegal, bootlegged copy of LabVIEW.

  • Frm-92160 Web client is old

    I have 9i installed in D:/oracle/oracle9i
    Now i installed 10g in d:/oracle/10gas
    After installation 10g.
    I tried to login to 9i and run form.I am getting an error
    frm-92160
    What i did so far from documents:
    1) Clean up files in c:/documentssettings/<username>/Oracle Jar Cache
    2) Clean up file contents in
    c:/documentssettings/<username>/.jinit
    3) Unistalled Jinitaitor and Reinstalled
    Still getting same error
    Thanks for all your help

    after you done the cleaning steps, change the Oracle Home to the version you installed (use Oracle Installation Products tool) , and then restart the OC4J instance, and run form builder

  • Svn client too old

    svn complains that client is too old. Does apple need to release an update or is this a different issue?
    ski:george$ svn update
    svn: This client is too old to work with working copy '.'; please get a newer Subversion client
    ski:george$

    What client and version are you using? Find it Preferences ->Versioning ->Subversion
    If you are using the JavaHL native client I would suggest moving to JDeveloper's built-in SVNKit client.
    I am using SVNKit 1.1.4
    rgds
    Susan
    http://www.susanduncan.blogspot.com

  • FRM-92160:Fatal error:Webclient version too old

    Somebody pls assist.
    I am running 11gR2 on Redhat, the forms can run on ie9 but can't on ie8. I am getting "FRM-92160:Fatal error:Webclient version too old". Anything I didn't do? I need this wotking as well on ie8.
    Any help would be appreciated.
    regards
    Mo

    Fortunately, the "Web client too old" or "Web client too new" errors are very accurate and clear. When a Forms application attempts to start, one of the first things which occurs is a verification that the client applet (frmall.jar) is of the same version as the server side runtime which is about to host it. "Web client too old", means that the client jar is of an older version than the server side runtime (i.e. frmweb.exe). This can occur if more than one Forms version has been accessed from the same server. Remember that the jar files are cached on the client (in the JRE). So, if you were to run something like v10 from serverA then attempt to run v11 from the same server, you likely would end up with a client too old error. The same would be true if you first try to run 11.1.1 then attempt to access 11.1.2 from the same machine. The issue can also occur if for some reason the jar files in the installation were not patched during a patch installation. This would be rare, but could occur if the patch installation failed during the process. It could also occur if you copies old files into the installation. This is never a good idea.
    So, as mentioned, start by clearing the JRE cache and retesting.
    1. Close ALL open browsers.
    2. Open the JRE Control Panel (found on the Windows Control Panel).
    3. On the General tab, click on "Settings..."
    4. Then click on "Delete files..."
    5. Then click on "Ok".
    6. Exit the JRE Control Panel and retest.
    Important to note is that JRE7 is NOT supported with 11.1.2.0. Be sure that you are using JRE6. If you have JRE7 installed, I would recommend closing ALL open browsers and uninstalling it. You should have only JRE6 installed before testing.

  • Web client version is too new

    hi
    i installed form 11g 64 bit on win 2008 r2
    us client use win xp and i installed on all client jre 6u26
    when load this url :
    http://192.168.90.27:9001/forms/frmservlet?config=test
    i get this error :
    Forms Applet version is 11.1.1.3
    network: Connecting http://192.168.90.27:9001/forms/lservlet;jsessionid=CVVKT7DhrR8BlxtQtl5KSMqGg7ht40bsf727J2BxvYscCyPdBW7h!927090843 with proxy=DIRECT
    FRM-92150: Fatal error: web client version is too new.
    network: Cache entry not found [url: http://192.168.90.27:9001/forms/java/oracle/ewt/alert/resource/AlertBundle_en.class, version: null]
    network: Connecting http://192.168.90.27:9001/forms/java/oracle/ewt/alert/resource/AlertBundle_en.class with proxy=DIRECT
    network: Cache entry not found [url: http://192.168.90.27:9001/forms/java/oracle/ewt/alert/resource/AlertBundle_en.properties, version: null]
    network: Connecting http://192.168.90.27:9001/forms/java/oracle/ewt/alert/resource/AlertBundle_en.properties with proxy=DIRECT
    network: Cache entry not found [url: http://192.168.90.27:9001/forms/java/oracle/ewt/alert/resource/AlertBundle_en_US.class, version: null]
    network: Connecting http://192.168.90.27:9001/forms/java/oracle/ewt/alert/resource/AlertBundle_en_US.class with proxy=DIRECT
    network: Cache entry not found [url: http://192.168.90.27:9001/forms/java/oracle/ewt/alert/resource/AlertBundle_en_US.properties, version: null]
    network: Connecting http://192.168.90.27:9001/forms/java/oracle/ewt/alert/resource/AlertBundle_en_US.properties with proxy=DIRECT
    network: Connecting http://192.168.90.27:9001/forms/lservlet;jsessionid=CVVKT7DhrR8BlxtQtl5KSMqGg7ht40bsf727J2BxvYscCyPdBW7h!927090843 with proxy=DIRECT

    Updating Path variable to original Oracle home resolved this issue.

  • Version too old to administrate site

    We have four administrators for our site, due to its large
    size. One of the administrators downloaded the trial version of CS3
    to test it out. Now, since she used the administration features
    with that version, none of the rest of us can use the admin
    features with our version (3.1). It says "Your version of
    Contribute is too old to administer this website. Please use a
    newer version of Contribute, or contact another administrator."
    Any way to fix this, other than upgrading?

    If you kept a backup of the "_mm" folder on your site you
    might could overwrite the newer copy of the folder.
    Short of this I don't think you have any other options other
    than upgrading. When upgrading the Administrative functions
    Contribute CS3 makes changes to the formatting of the XML files
    where the site infromation is stored.

  • ITunes too old to sync photos to iPhone 3G?

    When I first got my iPhone (late December) I set up a folder of photos in iPhoto that would sync with my iPhone... and did a successful sync.
    Since updating my iPhone to 2.1, and 2.11, I can no longer sync photos to my iPhone via that folder. I get an error message when I choose to sync that says that in order to sync photos to my iPhone I must have iLife 9 on my computer. I believe that is the version mentioned - I am not at home at the moment with the laptop that I sync with. What I believe I'm seeing, is that my version of iPhoto is too old to sync with the updated iPhone. All choices to sync with are grayed out. The only option is to sync the whole library... I don't want to sync my entire library.
    I've not seen this particular problem on this forum. If I've missed a solution - would someone post the link here? I don't want to install a newer iLife on this old laptop. I have other newer MacBook pro computers - but I use them for work projects and would rather not clutter them up with all my photos.
    Any help?
    Thanks

    Terry Bacon wrote:
    I do find it interesting that I was able to do that initial sync of my photo album...
    I wondered about that, myself... But, even without iPhoto, you can sync with a folder on the Mac. Older versions of iPhoto stored their pictures more transparently (in folders in the Pictures folder), so if you selected a folder in iTunes it would work.
    You could try copying the pics into a folder elsewhere on the Titanium G4's HDD and selecting that folder to sync. In iTunes, with the iPhone connected and selected in the devices tab, click the Photos tab and set the top pop-up menu to a folder. You can use one level of subfolders for 'albums' that will show up as such on the iPhone.
    Or, as you state, you could just move the pics to a newer machine.

  • Mac and iPhoto too old to order prints etc?

    I have an early 2008 MacBook and use iPhoto 08 and OSX 10.7.5 - all fine until now. I wanted to order some photo cards but it said I was no longer able to as my version of iphoto was too old and I needed to upgrade. So I went to the App Store to upgrade to the latest iphoto, but it said I had to be using OSX 10.9 or later. When I tried to upgrade to latest OSX (Mavericks) it said my Macbook was too old to support this.
    So at present I am unable to order anything from iphoto. Any ideas as to how to get round this?
    thanks

    Purchase an iLIfe 11 or iLIfe 09 install disk and install from that. You may be able to get these atAMazon or ebay.

  • FRM-92160: Web Client version too old

    Hi folks,
    i have been developing and running my forms using Oracle 9iDS and the Oracle 9i database. The forms are run in the browser using the version of OC4J that comes with the developer suite.
    i installed Oracle 10g Application server forms and reports services recently, however i have decided not to run my forms through the application server as yet.
    when i tried to run running a form, i had an error message saying
    FRM-92160: Web Client version too old.
    I tried looking up the error but couldn't find it anywhere.
    I can't run my forms now and i do not want to go through the application server as yet.
    Any suggestions as to what to do?
    Thanks in advance.

    I run into the same problem after upgrading my AS10g/W2k to 904011: Forms from the MiddleTier did run, but a Forms started from the DevSuite-environment would raise FRM-92160.
    What worked in my case was copying the MidTier's '...\forms90\java' files over to the DevSuite, ie.
    - backup [DevSuite_Home]\forms90\java to java0
    - copy [MidTier_Home]\forms90\java to [DevSuite_Home]
    After that, my Forms run flawlessly from both DevSuite's OC4J and the AS MidTier. I also 'upgraded' formsweb.cfg in [DevSuite_Home] from JInit 1.3.1.17 to 1.3.1.18 - works.
    Cheers
    Tino

Maybe you are looking for