This content has been marked as final. Show 2 replies
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 188.8.131.52. 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.