Discoverer 4i Connection Fails With 'AppServer Connection failed with:SessionConnectionException: Communication error or ORB internal error' After Cloning An E-Business 11i Instance on Windows (Doc ID 262717.1)

Last updated on SEPTEMBER 27, 2016

Applies to:

Oracle Discoverer - Version 4.1.48.06 to 4.1.48.08 [Release 4.1]
z*OBSOLETE: Microsoft Windows 2000
***Checked for relevance on 26-Sep-2012***


Symptoms

After cloning an E-Business Suite installation with Discoverer 4i included in the tech stack,  you could receive from Discoverer 4i Plus/Viewer the error :

Unable to connect to the Oracle Discoverer Application Server: Communication error or ORB internal error.
::: org.omg.CORBA.TRANSIENT
::: org.omg.CORBA.NO_RESPONSE
AppServer Connection failed with:SessionConnectionException: Communication error or ORB internal error
- Hint: An administrator can further diagnose connection problems by running the "checkdiscoverer" script under /806/discwb4/util..org.omg.CORBA.NO_RESPONSE[completed=NO]
SessionConnectionException: Communication error or ORB internal error
- Hint: An administrator can further diagnose connection problems by running the "checkdiscoverer" script under /806/discwb4/util..org.omg.CORBA.NO_RESPONSE[completed=NO]
at oracle/disco/model/corbaserver/connection/ConnectionManager.establishConnection



Executing the checkdiscoverer.bat script, displays:
...

Checking for OSAgent...
Error: OSAgent is not running. Discoverer will not function correctly unless there is at least one OSAgent running in the subnet.

Binding to Discoverer Server...
::: org.omg.CORBA.NO_RESPONSE
Error: Failed to bind to Discoverer Server.



The osagent.exe is showing it has started.

Furthermore, in the MS OS Event Viewer - Application Log , the following information is obtained while trying to Start Discoverer Service :

- Could not read the value for
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\DCW4_OAD_TIMEOUT
- Could not Read OAD_SERVER_TIMEOUT key. Default timout value is 60.
- Could not read the value for
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\DCW4_INSTANCE_NAME
- Could not find instance name, will use defalut names for Locator and
Preferences, can cause errors
Interesting, though DCW4_INSTANCE_NAME does exist in the registry, with value
"discoverer_server_instance_name".

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms