Tuesday, October 4, 2011

The application failed to run. There was an error while executing the application. Click "Details" for more information.

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com
Problem: The application failed to run. There was an error while executing the application. Click "Details" for more information.

On : 8.0.0.8 SIA[20430] version, Installation

After clicking on "Administration - iHelp" --> designer
the following error occurs.

ERROR
-----------------------
The application failed to run. There was an error while executing the application. Click "Details" for more information.

Symptoms:
The issue can be reproduced at will with the following steps:
1. Connect to epublicsector_enu via Siebel Web Client (using https/SSL)
2. Navigate to Administration - iHelp
3. Click on Designer tab

Getting Java errors while trying to access iHelp Designer screens.....
Getting Java errors while trying to access iHelp Designer screens. I have attached the screen shot in the word document. We have JDK 1.5.0_11
installed (1.5.0_11 JRE) on the system. Please suggest what needs to be done.

When Accessing iHelp > Designer, the designer java applet fails to launch when using thin web client via URL: http://sbldev001smtvwn.fmr.com:130/fess_enu

Instead a red X is displayed in the top left container applet.
> This issue occurs for all thin web clients.
> The issue cannot be reproduced using dedicated web client.

Log files:
Details:
Java Plug-in 1.6.0_20
Using JRE version 1.6.0_20-b02 Java HotSpot(TM) Client VM
User home directory = D:\Documents and Settings\Infovista.Arunkumar
----------------------------------------------------
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
l: dump classloader list
m: print memory usage
o: trigger logging
q: hide console
r: reload policy configuration
s: dump system and deployment properties
t: dump thread list
v: dump thread stack
x: clear classloader cache
0-5: set trace level to
----------------------------------------------------


load: class com.siebel.applets.flowchart.CSSFlowChartApplet.class not found.
java.lang.ClassNotFoundException: com.siebel.applets.flowchart.CSSFlowChartApplet.class
at sun.plugin2.applet.Applet2ClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.plugin2.applet.Plugin2ClassLoader.loadCode(Unknown Source)
at sun.plugin2.applet.Plugin2Manager.createApplet(Unknown Source)
at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: javax.net.ssl.SSLException: Received fatal alert: bad_record_mac
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Unknown Source)
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.recvAlert(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
at java.net.HttpURLConnection.getResponseCode(Unknown Source)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(Unknown Source)
at sun.plugin2.applet.Applet2ClassLoader.getBytes(Unknown Source)
at sun.plugin2.applet.Applet2ClassLoader.access$000(Unknown Source)
at sun.plugin2.applet.Applet2ClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
... 7 more
Exception: java.lang.ClassNotFoundException: com.siebel.applets.flowchart.CSSFlowChartApplet.class

increased the JRE java log levels for debugging.
Checking the java log files it shows that the SiebelFlowChart.jar is being downloaded from: http://sbldev001smtvwn.fmr.com:130/fess_enu/20412/applets/SiebelFlowChart.jar URL.

Next, checked via internet explorer if it is possible to access http://sbldev001smtvwn.fmr.com:130/fess_enu/20412/applets/SiebelFlowChart.jar directly and the error in browser occurs, file cannot be found.

Next, performed the same test of accessing the .jar URL directly via browser and it was possible to open or save the file using IE browser.

Next, On the issue environment changed the IIS virtual directory permissions to allow directory browsing.
Now it is possible to access and download the SiebelFlowChart.cab file via URL in IE browser.
It still is NOT possible to access teh SiebelFlowChart.jar file.

Next, create empty files test.cab and test jar in .\public\enu\applets directory and perform the same test as above trying to access the files directly via URL from IE browser.
The result: The test.cab file can be accessed and downloaded, the test.jar file can NOT.


Solution:



As per Node ID ” Getting Java errors while trying to access iHelp Designer screens..... ” - 740351.1

n order for ihelp > Designer to work, the java engine needs to download *.jar files in this case SiebelFlowChart.jar using the URL: http://///applets.

Since .jar file can't be downloaded due to IIS permission constrains for *.jar file, loading the Designer java applet fails.

This has been confirmed in the in-house lab environment.
After renaming the file name SWEAPP_ROOT/public/enu//applets/ SiebelFlowChart.jar to ORG_SiebelFlowChart.jar, it is possible to reproduce the issue in the iHelp > Designer and the java applet only shows a red “X”


ODM Proposed Solution
1> Check on a separate IIS web server if there are the same *.jar access restrictions
2> Check with IIS administration team.
3> Contact Microsoft support to verify how to control file extension based permissions.

ODM Proposed Solution Justif
Access issues to *.jar file on IIS is out of control from Siebel application perspective.
As per the tests in Cause Determination, it is not possible to access any *.jar, i.e. test.jar file in unrelated to Siebel specific naming or file contents.


Get Oracle Certifications for all Exams
Free Online Exams.com

No comments: