Page 1 of 1

FRM-92130: Registry is either missing, or contain

Posted: Fri Sep 29, 2006 4:09 am
by ahmadbilal
I am receiving the below error when loading up a new form. The registry.dat file exists in the correct location and is used for other forms:


<b>FRM-92130: Registry is either missing, or contains invalid, entry for Dispatcher.
Full Details: FRM-92030: Internal Error: Failed to find name of class for handleClassid=1. Missing in registry?
</b>
Details...
Java Exception:
oracles.forms.engine.RunformException: FRM-92130: Registry is either missing, or contains invalid, entry for Dispatcher.
Full Details:
Full Details: FRM-92030: Internal Error: Failed to find name of class for handleClassid=1. Missing in registry?
at oracle.forms.engine.Runform.initDispatcher(Unknown Source)
at oracle.forms.engine.Runform.startDispatcher(Unknown Source)
at oracle.forms.engine.Main.createRunform.initDispatcher(Unknown Source)
at oracle.forms.engine.Main.start(Unknown Source)
at sun/applet.AppletPanel.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

I realise this is short on detail - but I am not sure what detail to provide?

I will really appreciate any help....


Top Urgent

Posted: Fri Sep 29, 2006 5:59 am
by admin
Subject: Forms Fails To Run On One Client With FRM-92030 And FRM-92130
Doc ID: Note:308573.1 Type: PROBLEM
Last Revision Date: 20-OCT-2005 Status: PUBLISHED

In this Document
Symptoms
Cause
Solution

Applies to:
Oracle Forms - Version: 6.0.8 to 9.0
This problem can occur on any platform.
Symptoms
On a particular machine forms fails to start with :
FRM-92130 Registry is either missing, or contains invalid, entry for Dispatcher.
Full Details: FRM-92030: Internal Error: Failed to find name of class for handlerClassId=1.
Missing in registry?

This prevents from using forms on this machine.
Other clients work fine, indicating the Application Server setup is fine.
Cause

The machine at stake can not reach http://host:port/forms90/java/oracle/forms/registry/Registry.dat
As other clients access it fine, this file is not the problem, but rather there is a problem for this particular client to reach it: the proxy settings it uses may not be set correctly.
Solution

Correct the proxy settings used:

If not using the browser settings then ensure they are correct in the JVM used ( eg JInitiator or Java plug-in ).

If using the browser's proxy settings, check them, also check possible exceptions:

On IE: tools -> internet options -> connections -> network parameters -> advanced -> exceptions

On NS: Edit -> Preferences -> Advanced -> Proxies -> No proxy for

Posted: Mon Oct 02, 2006 1:28 am
by ahmadbilal
Thanks Admin Let Me Check Proposed Solution