Frm-92160

Users are receiving the above error when accessing an app via
the Web.
Please advise

Hi,
frm-92160 does not occur due to the new JDK version on the client. This error is thrown because of using incompatible versions of the frm*jar files in your forms. Couple of questions for you.
1. Does it work now with 1.4.2.06 ?
2. Are you sure you are using correct set of frm*.jar files?
3. Do you any other older version of forms installed in your machine?
-Arun

Similar Messages

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

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.

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

FRM-92160 Error running forms on the web

Hi,
I'm geting "FRM-92160: WEB client version too old." error when I try to run a form off the web. This form was running perfectly fine till yesterday. Is it because something was changed in server setting ?? please advice.

Hi
Iam also facing the same problem.
What i did was installed IAS and patch 4 on the server and tried to connect thro the browser.
Did anyone help throw some light on this issue.
Thanks
Giriraj
there is another thread with the same questions (do you guys work in teh same office!!).
Check out that tread for suggestions
Regards
Grant Ronald

FRM-92160 web version too old

Hi guys,
I had installed oracle 9i and developer6i on the server and configue IIS .When i access through client,if win 98 is installed on client it gives FRM-92160 web version too old error but on client where win2000 is installed ,it works.Any help??

Check if you have the correct version of Jinitiator on your Win 98 machine.

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 )

FRM-92160: WEB Client Version too old & Vis R12.0.4 invalid objects

Hello all,
I'm installing Vision R12.0.4 in a server. That server used to contain Vision R12.0.0 which I upgraded to R12.0.4 but still had some invalid objects (I already submitted that problem in another thread). I installed the new vision instance to the same folder used to contain R12.0.0 vision after remove the old installation.
After all installation steps completed I tried to connect from my laptop but I got this error message :
FRM-92160: WEB Client Version too old
Had tried to uninstall all java from my laptop but still had the same error message. I had oracle form & report developer 6i and 10g in my laptop. Tried to remove that installation and cleaned the registry but failed to delete LEGACY_ORACLE_LOAD_BALANCER_GO_CLIENT and some other objects.
I checked the installation and found 35 invalid objects, do APPS compile and left with 32 invalid objects. Here are the invalid objects :
OWNER     OBJECT_NAME
APPS     IGCBG_CC_NUMBER_METHODS
APPS     IGCFG_CC_NUMBER_METHODS
ORDSYS     ORDIMGEXTCODEC_PKG
ORDSYS     ORDIMG_PKG
SYS     XMLGENFORMATTYPE
SYS     LCR$_ROW_LIST
SYS     LCR$_ROW_UNIT
SYS     AQ$_SRVNTFN_MESSAGE
SYS     AQ$_REG_INFO
SYS     AQ$_REG_INFO_LIST
SYS     DBMS_SUMADV
SYS     AQ$_REG_INFO_LIST
SYS     DBMS_XPLAN_TYPE
SYS     DBMS_XPLAN_TYPE_TABLE
SYS     AQ$_DESCRIPTOR
SYS     AQ$_SRVNTFN_MESSAGE
SYS     AQ$_EVENT_MESSAGE
SYS     AQ$_REG_INFO
SYS     AQ$_SRVNTFN_MESSAGE
SYS     MSG_PROP_T
SYS     AQ$_DESCRIPTOR
XDB     servlet-list46_T
XDB     servlet52_COLL
XDB     servlet47_T
XDB     xdbconfig58_T
XDB     servlet-config-type42_T
XDB     webappconfig65_T
XDB     sysconfig59_T
XDB     XDB$RESOURCE_T
XDB     protocolconfig60_T
XDB     sysconfig59_T
XDB     xdbconfig58_T
XDB     httpconfig64_T
XDB     protocolconfig60_T
XDB     httpconfig64_T
How to solve those problems? Thanks.

The following views will remain invalid in 12.0.4:
APPS IGCBG_CC_NUMBER_METHODS
APPS IGCFG_CC_NUMBER_METHODS
This is documented in 12.0.4 Release Note:549389.1
under "Installation and Upgrade Customers"Thanks for the info. At least it solved 2 of my problem rows :P
anyway, I'm sorry that I can't tried to solve the problem anymore cause the storage was needed for another installation so I'd to remove this problem instance. Maybe if I can try it again I'll let you all know. Thanks

Frm-92160 web version too old error

plz suggest the solution to overcome from it

Actually the JRE/Jinit version has nothing to do with the error. The error is caused when the Forms applet (i.e. frmall.jar, frmall_jinit.jar) version is not in sync with the Forms Servlet or Runtime version.
Clear the JRE/Jinit JAR cache and retest. If this continues to fail, consider whether or not you have recently installed any patches to the Application Server. If so, you may have not successfully completed that task. If the client jar files (i.e. frmall.jar, frmall_jinit.jar) where not updated during a patch installation, the error you are seeing is likely to occur. This can also occur if the client accesses more than one minor version of an Application Server installation (i.e. 10.1.2.0.2 and 10.1.2.2).
Installing a new JRE only indirectly solves this problem. The reason is that when a new JRE is installed, the JRE cache is empty the first time it is used and therefore resembles the cache clearing recommendation noted above.
FYI: FRM-92150 Client version too new occurs, after a patch installation, when the client JAR files are updated but the Forms Servlet or Runtime is not. Again, clearing cache can sometimes solve this problem if recent patching was not attempted.

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.

Error in form builder 10g

HI,
I have installed oracle EBS 12.1.1 and installed developers suite 10g
while running the form builder.
It results me
frm-92160 webclient is too old.
Please help.
Thanks and Regards,
Srikanth

Yes Autoconfig completed successfully.
I have installed the R12.1.1.
later installed dev suite and concurrent manager gave a error.
i have run autoconfig and issue with conc manager fixed.
I tried to create and run a sample Form.
when running from it asked for Jinitiator.
and placed JVM of java 1.6 in the jinitiator folder.
while running it gave me frm-92160 webclient is too old.
while starting OC4J it gave following text
C:\Windows\system32>c:\DevSuiteHome_1\jdk\bin\java -Doracle.security.jazn.config=c:\DevSuiteHome_1\j2ee\DevSuite\config\jazn.xml -Doracle.home=c:\DevSuiteHome_1 -DORACLE_HOME=c:\DevSuiteHome_1 -jar c:\DevSuiteHome_1\j2ee\home\oc4j.jar -userThreads -config c:\DevSuiteHome_1\j2ee\DevSuite\config\server.xml
13/07/04 14:12:29 Auto-unpacking C:\DevSuiteHome_1\forms\j2ee\formsapp.ear... done.
13/07/04 14:12:29 Auto-unpacking C:\DevSuiteHome_1\forms\j2ee\formsapp\formsweb.war... done.
13/07/04 14:12:29 Auto-deploying forms (New server version detected)...
13/07/04 14:12:29 Auto-deploying file:/C:/DevSuiteHome_1/j2ee/home/default-web-app/ (New server version detected)...
13/07/04 14:12:29 Auto-deploying file:/C:/DevSuiteHome_1/j2ee/home/applications/dms0/ (New server version detected)...
13/07/04 14:12:29 Auto-deploying file:/C:/DevSuiteHome_1/j2ee/home/applications/dms/ (New server version detected)...
13/07/04 14:12:29 Auto-deploying Forms Services (New server version detected)...
13/07/04 14:12:29 Copying default deployment descriptor from archive at C:\DevSuiteHome_1\reports\j2ee\reports_ids\web/WEB-INF/orion-web.xml to deployment directory C:\DevSuiteHome_1\j2ee\DevSuite\application-deployments\reports\web...
13/07/04 14:12:29 Auto-deploying file:/C:/DevSuiteHome_1/reports/j2ee/reports_ids/web/ (New server version detected)...
13/07/04 14:12:29 Auto-deploying file:/C:/DevSuiteHome_1/reports/j2ee/reports_ids/demo/ (New server version detected)...
13/07/04 14:12:30 Oracle Application Server Containers for J2EE 10g (10.1.2.0.2) initialized
i tried to re install dev suite.
when dev suite installed can run the forms but conc manager is not starting .
after running autoconfig. the issue is coming.
regards,
Srikanth

Forms9i with 10gAS

HI Gentlemen,
I have a 9i DB, 9iDS and 10gASFrs installed on an XP machine. As stated in the 10gAS doc, I created a simple config section [myconfig] with only form=myform and userid=usr/pwd@dblink in FORMSWEB.CFG, added my path to FORMS90_PATH in DEFAULT.ENV and did nothing more.
Now, when I start OC4J Instance from 9iDS and issue the URL:
http://mypc:7777/forms90/f90servlet?config=myconfig
then I get "The page cannot be displayed".
When I issue the following URL:
http://mypc:8888/forms90/f90servlet?config=myconfig then the Applet starts and so does 9i FOrms Services, but it stops with FRM-92160 Version of Web Client too old.
The message is not to be found anywhere.
Confusingly, I have another computer where it goes! And I can not see any difference in any settings.
Can you help me, where I am wrong?
Thanking in advance, kind regards from
Miklos HERBOLY

Hi,
the Forms Services version in 10g AS is newer than the version In Oracle9iDS, which is why you get the error message. Try and clean the Oracle jar cache before re-running the application in Oracle 9iDS. Best is to upgrade your IDS to 10g as well.
The "The page cannot be displayed" message doesn't point to a Forms problem but maybe calling teh wrong port. Did you try port 80 or 7779 ?
Frank

9iDS / ODS 10g co-existance problem

I have a 9.2 database, 9ids (9.0.2.12.2) and ODS 10g (9.0.4.0.19) installed in separate Oracle Homes.
After installation my PATH looks like:
P:\oracle\10g\bin;O:\oracle\9iDS\bin;O:\oracle\ora92\bin;P:\oracle\10g\jdk\jre\bin\classic;P:\oracle\10g\jdk\jre\bin;P:\oracle\10g\jdk\jre\bin\client;P:\oracle\10g\jlib;P:\oracle\10g\jre\1.4.1\bin;P:\oracle\10g\jre\1.1.8\bin;O:\oracle\9iDS\jre\1.3.1\bin;O:\oracle\9iDS\jre\1.4.0\bin;O:\oracle\9iDS\jdk\jre\bin\classic;O:\oracle\9iDS\jdk\jre\bin;O:\oracle\9iDS\jlib;G:\Program Files\Oracle\jre\1.3.1\bin;G:\Program Files\Oracle\jre\1.1.8\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;G:\Program Files\Common Files\Adaptec Shared\System;O:\Program Files\Executive Software\Diskeeper\
When I now start the OC4J instance of the 9ids oracle home, then I get a FRM-92160: WEB Client Version too old when I open the url http://localhost:8888/forms90/f90servlet.
When I stop OC4J, remove every entry of 10g from the PATH environment variable, restart OC4J of 9iDS, then everything is OK.
I have no problems with the OC4J-instance of 10g when the PATH contains the 10g, 9ids and the database entries.

Jean,
the Oracle10g IDS was shipped because OracelAS 10g went production on Solaris. The AS port for Windows is expected for early next year and so is iDS. To allow people to test and develope against OracleAS 10g, the ids was released as preview (this is as far as I know yet).
when you start OC4J the Oracle Home is passed to the java program, so if the OC4J needs to call programs, it must
search relative to this Oracle Home and not relay on the PATH environment variable of the operating system
This is only true for Forms modules. When you add both directories to the System path then its Windows that decides how to pick a named executable. You would have to set the PATH explicilty when launching OC4J to avoid this conflict.
Fran

Upgraded Win2000 to SP4: Now cannot run in 9i Forms Builder

I upgraded to SP4 for Win2000 professional. Now when I attempt to run a form through 9i Forms Builder I get "FRM-92160: Web client version too old".
Do I need a new OC4J? If so, where is is within OTN?
Thanks

Sounds like maybe you need to clear out the cache for jinitiator or you are pointing to an different version of the JAR file. Did you apply a Forms patch as well?
I would suggest getting on metalink.oracle.com since there are a few notes which talk you through this.
Hope this helps.
regards
Grant Ronald
Forms Product management

Getting error message FRM-40700:No such trigger: SPECIAL20

Hi,
We have designed a custom report (Quote) and would like to use Special Menu's(Reports Menu) to open this custom Report. When I try to open this Report using
REPORTS->Quote, The Report is opening seccuessfully but i am getting following error message at the bottom of screen bar.How can I clear this message ?
FRM-40700:No such trigger: SPECIAL20
The code which I wrote in the custom.pll is
IF (form_name = 'OEXOEORD') THEN
-- Enable View Order Report -- V1.4 --
if (event_name = 'WHEN-NEW-FORM-INSTANCE') then
app_special.instantiate('SPECIAL20', 'View Order Report');
app_special.enable('SPECIAL20',PROPERTY_OFF);
else
if (event_name='WHEN-NEW-BLOCK-INSTANCE') THEN
if block_name='ORDER' then
app_special.enable('SPECIAL20',PROPERTY_ON);
else
app_special.enable('SPECIAL20',PROPERTY_OFF);
end if;
end if;
end if;
if (event_name='SPECIAL20' and block_name='ORDER') then
param_to_pass1 := name_in('ORDER.HEADER_ID');
select order_number into param_to_pass2 from oe_order_headers_all where header_id=param_to_pass1;
editor_pkg.report(BSI_Quote(param_to_pass2), 'Y');
null;
end if;
end if;
Please give me valuable inputs on this issue.
Thanks,
HTH

Hi,
your package " app_special" does a call to "execute_trigger('SPECIAL20');" ,
but there is no trigger with this name in your form. ( perhaps an Menu-item exists with this name.)
Lock for "execute_trigger" in:
app_special.instantiate('SPECIAL20', 'View Order Report');

Frm-92160

Similar Messages

Maybe you are looking for