C370 - 7.6.3-019 An application fault occurred: ('snmp/ipmi_handlers.py _handle_fan_result|370'

I got the following CRITICAL error at C370:
The Critical message is:
An application fault occurred: ('snmp/ipmi_handlers.py _handle_fan_result|370', "<type 'exceptions.ValueError'>", "invalid literal for int() with base 10: 'no reading'", '[_coro.pyx coro._coro._wrap1 (coro/_coro.c:8477)|757] [egg/interface_controller.py poll_ipmi|1409] [snmp/hardware.py update_sensors|89] [snmp/ipmi_handlers.py update_sensors|609] [snmp/ipmi_handlers.py _parse_sensor_lines|583] [snmp/ipmi_handlers.py _handle_fan_result|370]')
Version: 7.6.3-019
Maybe this bug is related to WSA bug CSCzv78978...
Need a help to see if this bug is resolved at 8.0.1-023 release.

This is ESA defect on 7.6 family... see the following:
https://tools.cisco.com/bugsearch/bug/CSCzv22991
You'll need to upgrade to 8.0.1-023, or you can open support case, we can provision 8.5.6 FCS, or you can wait for our 8.5.6 GA release shortly...
I hope this helps!
-Robert
(*If you have received the answer to your original question, and found this helpful/correct - please mark the question as answered, and be sure to leave a rating to reflect!)

Similar Messages

"An application fault occurred" with AsyncOS 8.0.1 on multiple ESAs

Ever since upgrading to AsyncOS 8.0.1-023, we have been getting the following application fault intermittently but it has been triggering constantly this morning on all 4 appliances in a cluster and 2 others in a separate cluster:
An application fault occurred: ('egg/coro_ssl.py _non_blocking_retry|140', "<class 'sslip.Error'>", "(336195711, 'error:1409F07F:SSL routines:SSL3_WRITE_PENDING:bad write retry')", '[egg/smtp_client.py run|885] [egg/smtp_client.py _run|964] [egg/coro_ssl.py close|238] [egg/coro_ssl.py shutdown|218] [egg/coro_ssl.py _non_blocking_retry|140]')
The only thread I see regarding this is that is an known bug with the OS version. Is there a way to temporarily correct this and is there a known cause to this such as a corrupt message? We do not want to keep receiving this alert until a fix is released and do not want to be forced to turn off the alerting.
https://supportforums.cisco.com/discussion/12071286/cscug73383-ironport-esa-version-801-023

The same for our 2 ESA C370, Version: 8.0.1-023 AND a similiar message for our M670 Version: 8.1.1-013. They were upgraded vom V 7.x last weekend.
Suprisingly we drive 2 ESA C360, 1 M670 and 1 M160 for another customer without this error. Tose machines were upgraded to the same 8.x versions mentioned above in December last year! Looks a bit strange to me ...
The Critical message is (on M670):
An application fault occurred: ('navigation/HelpBarYUI.py my_tasks_list_submenu|462', "<type 'exceptions.KeyError'>", "'varstore'", '[util/Aquarium.py screenLoop|408] [util/InternalLibrary.py inverseExtend|328] [util/InternalLibrary.py __call__|769] [layout/Bare.py __call__|578] [util/InternalLibrary.py __call__|769] [layout/CssAndJavaScript.py __call__|451] [util/InternalLibrary.py __call__|769] [layout/Sparse.py __call__|1483] [Cheetah/NameMapper.py valueFromSearchList|250] [Cheetah/NameMapper.py _valueForName|229] [layout/Sparse.py doTop|851] [Cheetah/NameMapper.py valueFromSearchList|250] [Cheetah/NameMapper.py _valueForName|229] [layout/Sparse.py doHelpBar|795] [util/InternalLibrary.py call|280] [navigation/HelpBar.py __call__|154] [Cheetah/NameMapper.py valueFromSearchList|250] [Cheetah/NameMapper.py _valueForName|229] [navigation/HelpBarYUI.py options_and_help_yui_menubar|217] [Cheetah/NameMapper.py valueFromSearchList|250] [Cheetah/NameMapper.py _valueForName|229] [navigation/HelpBarYUI.py my_tasks_mainmenu|275] [Cheetah/NameMapper.py valueFromSearchList|250] [Cheetah/NameMapper.py _valueForName|229] [navigation/HelpBarYUI.py my_tasks_list_submenu|462]')
Version: 8.1.1-013

SMA problem : An application fault occurred

Hi,
I've a problem with a SMA in 8.3.6-039 version.
When i click on "System administration" then " User Roles" i've the following message :
Application Error
An application error has occurred and has been logged to the GUI log
Return to the default screen.
After, i receive the following email :
The Critical message is:
An application fault occurred: ('access/custom_roles_view.py format_privileges_reports|582', "<type 'exceptions.KeyError'>", "'group-1422520728.0'", '[util/Aquarium.py screenLoop|408] [util/InternalLibrary.py inverseExtend|328] [util/InternalLibrary.py __call__|769] [layout/Bare.py __call__|578] [util/InternalLibrary.py __call__|769] [layout/CssAndJavaScript.py __call__|451] [util/InternalLibrary.py __call__|769] [layout/Sparse.py __call__|1527] [util/InternalLibrary.py __call__|771] [access/custom_roles_view.py __call__|183] [access/custom_roles_view.py esa_section|314] [access/custom_roles_view.py format_privileges_common|424] [access/custom_roles_view.py format_privileges_reports|582]')
Version: 8.3.6-039
Do you have an idea about this problem ?
Regards,
Julien

We had two defects that were opened and marked as fixed, only have internal side information regarding. Is this a continual issue when going through GUI System Administration > User Roles?
Do you have any roles configured? Or - have you removed any roles, and these are still tied to old user accounts?
-Robert

Ironport - An application fault occurred: ('egg/message_queue.py rehydrate|425'

Hi,
We have over the last 24 hours received messages like this:
Critical: An application fault occurred: ('egg/message_queue.py rehydrate|425', "<type 'exceptions.IndexError'>", 'list index out of range', '[egg/message_queue.py filter|462] [egg/message_queue.py pop|266] [egg/message_queue.py _get_pop_queue|116] [egg/message_queue.py rehydrate|425]')
Sun Aug 12 20:51:59 2012 Critical: An application fault occurred: ('egg/message_queue.py rehydrate|425', "<type 'exceptions.IndexError'>", 'list index out of range', '[egg/smtp_client.py _connect_to_ip|1128] [egg/omh.py connect_success|2468] [egg/omh.py bounce_old_and_warn|2556] [egg/message_queue.py filter|488] [egg/message_queue.py join|494] [egg/message_queue.py pop|266] [egg/message_queue.py _get_pop_queue|116] [egg/message_queue.py rehydrate|425]') ip:203.188.197.119
Could anyone explain to me -why
Thakns.

Hello Jaime,
that's a relatively new bug in your version,caused by some messages that can't be delivered. I'd suggest you to contact customer support to have that checked and to get rid of the error. You could also reset your queue, but of course, that would remove all other mmessages as well.
Hope that helps,
Andreas

Critical message C680 IronPort - An application fault occurred: ('egg/coro_ssl.py _non_blocking_retry|118'

Hi,
We keep receiving these messages, can someone tell me what this refers to please?
The Critical message is:
An application fault occurred: ('egg/coro_ssl.py _non_blocking_retry|118', "<type 'exceptions.OSError'>", '[Errno 0] Error', '[egg/smtp_client.py run|879] [egg/smtp_client.py _run|958] [egg/coro_ssl.py close|216] [egg/coro_ssl.py shutdown|196] [egg/coro_ssl.py _non_blocking_retry|118]')
Last message occurred 26 times between Fri Jun 20 11:26:14 2014 and Fri Jun 20 11:37:15 2014.
Version: 7.8.0-360

Such an application fault is generally caused by an issue where a TLS session fails to close properly. In this scenario, the email does deliver successfully, but can produce an application fault. In general, these application faults do not indicate a problem with the appliance, and shall be suppressed in a future release of AsyncOS.
With running 7.8.0 - which shipped on the appliance, you may benefit to upgrade to 8.0.1-023, or open a support request to have the appliance properly provisioned for 8.5.6 FCS, which may help to correct seen TLS issues, such as this.
I hope this helps!
-Robert
(*If you have received the answer to your original question, and found this helpful/correct - please mark the question as answered, and be sure to leave a rating to reflect!)

WSA Critical: An application fault occurred:

hello my WSA is sending the next message:
Critical: An application fault occurred: ('updater/app_thread.py _set_abandoned_versions|883', "<type 'exceptions.TypeError'>", "'NoneType' object is unsubscriptable", '[updater/app_thread.py update_handler|1149] [updater/app_thread.py _run_update|739] [updater/app_thread.py _set_abandoned_versions|883]')
the error occurs in date 17 and time 08:31 and goes on
any advice

I would recommend you to check if the appliance can connect to the update servers. In the GUI, go to System Administration > Upgrade and Update Settings. Take note of the Routing Table that is used for updates (Management or Data).
Once you have the above info, go to the CLI and test the appliance to see if it has connectivity to the update/upgrade servers.
telnet
(select the interface - Management if Management Routing Table is used for updates; P1/P2 if Data is used for updates)
The sites to test are:
update-manifests.ironport.com on port 443
updates.ironport.com on port 80
upgrades.ironport.com on port 80
-Vance

Critical Errror:-An application fault occurred.....

HI,
I am getting this Error
An application fault occurred: ('screen/not_found.py __call__|28', "<type 'exceptions.AttributeError'>", "Bean instance has no attribute '__getitem__'", '[util/Aquarium.py screenLoop|407] [util/InternalLibrary.py inverseExtend|328] [util/InternalLibrary.py __call__|769] [screen/Controller.py __call__|23] [util/InternalLibrary.py __call__|769] [screen/CommonController.py __call__|38] [util/InternalLibrary.py __call__|769] [screen/AppController.py __call__|167] [util/InternalLibrary.py __call__|771] [screen/not_found.py __call__|28]')
Last message occurred 2 times between Wed Nov 7 17:26:56 2012 and Wed Nov 7 17:39:42 2012.
ANY HELP WILL BE APPRECIATED

Hi Yashwant,
as the version your appliance is running on is End of Life since March 2012 I'd suggest first upgrading to a newer version.
http://www.cisco.com/web/ironport/asyncOS_esa_eol_dates.html
It is very possible that this application fault was already addressed in a bug and got fixed in a later version, e.g. version 7.6.1. In case after upgrading application faults still occur, please open a case with TAC.
Best regards,
Enrico

Application fault for Sync Send holds up the ccBPM queues

Hello Experts,
I have the following scenario which I have realized using a ccBPM in SAP PI 7.31.
I receive a nomination idoc from ECC from which I create a nomination request to be sent in Sync manner to a web service. The response received from the web service is sent through another idoc, back to ECC. In case of any failure during this, an ALEAUD idoc is sent back to ECC to convey the failure. This web service returns an application fault in case any data in the request is improper and there is no fault message in the WSDL for the web service.
I have used a ccBPM to receive the nomination idoc from ECC, transform it to web service request and send it using a Sync Send step. In case an application fault occurs, the SOAP receiver channel shows the error as application fault and my Sync Send step does not receive the expected response. However, a SOAP message with envelope is received from the web service which leads to the BPM queue land in error 'Permanent error in BPE inbound processing'.
However, in case of the application fault I want to make the Sync Send step trigger an exception so that the ALEAUD idoc is sent back to ECC system.
Any thoughts on how i can achieve this?
Thanks in adv.
Diptee

Hello Experts,
I have the following scenario which I have realized using a ccBPM in SAP PI 7.31.
I receive a nomination idoc from ECC from which I create a nomination request to be sent in Sync manner to a web service. The response received from the web service is sent through another idoc, back to ECC. In case of any failure during this, an ALEAUD idoc is sent back to ECC to convey the failure. This web service returns an application fault in case any data in the request is improper and there is no fault message in the WSDL for the web service.
I have used a ccBPM to receive the nomination idoc from ECC, transform it to web service request and send it using a Sync Send step. In case an application fault occurs, the SOAP receiver channel shows the error as application fault and my Sync Send step does not receive the expected response. However, a SOAP message with envelope is received from the web service which leads to the BPM queue land in error 'Permanent error in BPE inbound processing'.
However, in case of the application fault I want to make the Sync Send step trigger an exception so that the ALEAUD idoc is sent back to ECC system.
Any thoughts on how i can achieve this?
Thanks in adv.
Diptee

Application/UNKNOWN/APPLICATION_ERROR - application fault

Hi!
I am creating HTTP-XI-SOAP synchronous scenario and I've got some error in RWB:
SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
How can I fix that problem??
Any sugestions??

Hi ,
Please refer the following thread , This might help you
Application/UNKNOWN/APPLICATION_ERROR
Regards.,
V.Rangarajan

WLS 7.0SP2 Apache Plug-in application fault

I'm running WLS 7.0SP2 on XP and have the WLS Apache plug-in in Apache 2.0.49.
I get this application fault alot...
Faulting application apache.exe, version 2.0.49.0, faulting module unknown, version
0.0.0.0, fault address 0x008be6ae.
The only other non-default module I'm using mod_headers.
I have the same problem in Apache 2.0.45, 2.0.46, 2.0.47, 2.0.48, and 2.0.49
Has anyone else run across this problem? I'd REALLY like to know the root cause..
Thanks,

I'm running WLS 7.0SP2 on XP and have the WLS Apache plug-in in Apache 2.0.49.
I get this application fault alot...
Faulting application apache.exe, version 2.0.49.0, faulting module unknown, version
0.0.0.0, fault address 0x008be6ae.
The only other non-default module I'm using mod_headers.
I have the same problem in Apache 2.0.45, 2.0.46, 2.0.47, 2.0.48, and 2.0.49
Has anyone else run across this problem? I'd REALLY like to know the root cause..
Thanks,

Application errors occured in ccBPM not restartable?

hello experts,
We are using ccBPM for some of the integration scenarios and synchronously posting data to SAP R/3. When an BAPI returns an application error code (e.g. material locked by an user), we are unable to restart these messages from SXMB_MONI hence we have to manually edit and retransfer XML files. This is very cumbersome and error prone. We have informed the implementation partner but they are saying that application specific errors can not be restarted.
We have gone through the documentation http://help.sap.com/saphelp_nw04/helpdata/en/ea/2f053d39177608e10000000a114084/content.htm and it says :
"Application error (restart possible)
An application error occurred during message processing. For asynchronous processing, this status only occurs in the receiver system; for synchronous processing, it occurs in all systems involved."
We have also gone through the blog /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1 by Shabarish Vijayakumar. We want the same result but we are using ccBPM send step to invoke a standard BAPI via RFC adapter instead of using ABAP server proxy.
Can someone please help us out? users are complaining the old R/3 LSWM uploads were much more feature rich & user friendly
thanks & regards,
Harsha.

Hi Uri,
thanks for the suggestion. I would assume this will require changes in the BPM. Why cant we simply catch the BAPI return code 'E' and mark the message as an application error, which is restartable?
This is a very basic requirement and I am sure there must be a way of achieving what we want but I don't have enough knowledge on XI to do it.
Is there any place we can find a how-to guide?
thanks & regards,
Harsha.

Exception in SAP Application Integrator occured: Unable to process templat

Hi,
We are trying to execute a BI report in portal through BEx web and we are getting the below error
[EXCEPTION]
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to process template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname><BWLauncherComponent[PORTAL_URL]>;jsessionid=<Request.JSessionID>?sap-ext-sid=<ESID[url_ENCODE]>&Language=<Request.Language>&theme=<LAF.Theme[url_ENCODE]>&sap-lafversions=<LAF.AllVersions[url_ENCODE]>&<Authentication>&<Report>&<BusinessParameters>', because 'Report' is an invalid terminal property of the Root context.
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
I have tested the connection in the system and also checked the webas name and host details in the system. they look fine.
please help me with your inputs.
Thanks.
Kind Regards,
Priyanka.

This could be the problem . In your portal , copy the pcd path of a folder under which you would like to place this report and paste it in the bex analyser while publishing (pcd link) , see if this helps . A few more points .
1) You can also publish these queries as reports in portal using Bex Query designer - there will be an option to publish in portal . You will see it depending upon the version of designer. If you are able to see that option , selecting the pcd location would require you to have content admin role in portal .
2) Manually create iviews in portal (BI Reports) using the query string given to you by your BI folks . You can create either Bex 3.X or 7.0 depending upon the query string .
Regards
Mayank

HTTP 500 internal Server ERROR, Application error occurred ...

Hello Friends, 
i'm facing a suspictious problem and hope, one of you can help me. When i try to connect to J2EE-Startpage http://<server>:50000 or http://<server>:8000 i get the following Error 
500 internal Server Error 
Application error occurred during the request procession. 
Details: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: 
Error compiling [/main.jsp] of alias [/] of J2EE application [sap.com/com.sap.engine.docs.examples]. 
Exception id: 005056906BAB0255000A676D00000F800004855341DFB776 
 
What happened before: 
I applied the J2EE-Part of EHP4 Upgrade with JSPM to the Java-Stack. Deployment has finished without any errors. 
 
Situation: 
Java-Stack is running and connected per SAPJSF to ABAP-Stack. Processes in SAPMMC are green. Java-Stack is allocating it's memory (about 1.5 GB) as i can see in Taskmanager and sysinternal`s processxplorer. I set Java-Parameter corresponding to note 723909 (696410, 716604) and upgraded JDK to latest version (1.4.2_26). Starting and stopping the Java-Stack with transaction SMICM works as it should. Even the Webservices for 3'rd Party-Applications supplied by the java-stack are working. Deployed Components in Service "Deploy" in VisualAdmin -> Server_0 are OK and connection to DB is up. Reboot of server doesn't help in this case. Anything seem's to be fine except i'm not able to access J2EE-Applications per Webbrowser, not on the werver itself by using localhost, nor by using fqdn on my client workstation. System: w2K3 x32Bit, MaxDB 7.7.07 Build 16, SUN JDK 1.4.2_26 
 
access the portal http://<server>:50000/irj/portal throws the following Error: 
Portal-Laufzeitfehler 
Ausnahme bei der Verarbeitung des Requests; senden Sie die ID der Ausnahme an Ihren Portaladministrator 
Ausnahme-ID 01:24_29/04/10_0001_2133850 
Weitere Details zu dieser Ausnahme finden Sie in der entsprechenden Protokolldatei 
 
http://<server>:50000/sld 
500 Internal server Error 
Application error occurred during the request procession. 
Details: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: 
Error compiling [/index.jsp] of alias [sld] of J2EE application [sap.com/com.sap.lcr]. 
Exception id: [005056906BAB00C3000085210000096C0004855448A9FAC3] 
 
http://<server>:50000/useradmin 
500 Internal server Error 
Application error occurred during the request procession. 
Details: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: 
Error compiling [/index.jsp] of alias [useradmin] of J2EE application [sap.com/com.sap.security.core.admin]. 
Exception id: [005056906BAB00280000A0A50000096C00048554574171DB] 
 
but connecting to "Hello World" Example http://<server>:50000/Hello works pretty good (don't know why) 
 
Many many thanks for your ideas, suggestions ...
Regards
Matthias

Hi Shitij,
thank you very much for your advice and sorry for beeing so late. 
You're absolutely right. there are some error's i've to look for. 
The confusing thing is, that the tracefiles DefaultTrace.<NO>.trc are filled up in about 5 seconds with 10 MB Stuff. In our productive Environment, this is not the case. Below, i attached the last lines from DefaultTrace.1.trc where i tried to connect to the webaccess. By the Way, there's an DB-connect error, even though there are some SAPEC6DB sessions in DBM-Gui. Probably i've to raise up the numbers of maximum connections in VisualAdmin.DB-session usage in DMB-gui is 53%. I will post DM-Connection error from DefaultTrace.<NO> in next Post.
 
<pre>
part 1:
#1.5 #005056906BAB016C000010C700002A380004855B94F9FD87#1272528294816#com.sap.engine.compilation#sap.com/com.sap.engine.docs.examples#com.sap.engine.compilation.DirObject.deleteDir(true)#J2EE_GUEST#0##n/a##e54700ce536511dfb80c005056906bab#SAPEngine_Application_Thread[impl:3]_33##0#0#Debug##Plain###The directory [D:
usr
sap
EC6
DVEBMGS00
j2ee
cluster
server0
compilerTempDir
compiler_Apr_29_at_10.4] was successfully deleted.#
#1.5 #005056906BAB016C000010C800002A380004855B94FA0015#1272528294816#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/com.sap.engine.docs.examples#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#J2EE_GUEST#0##n/a##e54700ce536511dfb80c005056906bab#SAPEngine_Application_Thread[impl:3]_33##0#0#Error##Plain###application [] Error in compiling the jsp file D:/usr/sap/EC6/DVEBMGS00/j2ee/cluster/server0/apps/sap.com/com.sap.engine.docs.examples/servlet_jsp/_default/root/main.jsp. The error is: java.lang.NullPointerException
 at com.sap.engine.compilation.ExternalCompiler.getErrorMessage(ExternalCompiler.java:188)
 at com.sap.engine.services.servlets_jsp.server.jsp.JavaCompiler.compileExternalWithCompilationLib(JavaCompiler.java:109)
 at com.sap.engine.services.servlets_jsp.server.jsp.JavaCompiler.compile(JavaCompiler.java:319)
 at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.generateJavaFile(JSPParser.java:369)
 at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:107)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.getClassName(JSPServlet.java:242)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.reCompileAndGetClassName(JSPServlet.java:532)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:181)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
#1.5 #005056906BAB016C000010CA00002A380004855B94FA00EC#1272528294816#com.sap.engine.services.servlets_jsp.server.jsp.JSPParser#sap.com/com.sap.engine.docs.examples#com.sap.engine.services.servlets_jsp.server.jsp.JSPParser#J2EE_GUEST#0##n/a##e54700ce536511dfb80c005056906bab#SAPEngine_Application_Thread[impl:3]_33##0#0#Error#1#/System/Server/WebRequests#Plain###application [] Error in compiling the jsp file D:/usr/sap/EC6/DVEBMGS00/j2ee/cluster/server0/apps/sap.com/com.sap.engine.docs.examples/servlet_jsp/_default/root/main.jsp.
The error is: java.lang.NullPointerException: null
Exception id: [005056906BAB016C000010C800002A380004855B94FA0015]#
#1.5 #005056906BAB016C000010CB00002A380004855B94FA041F#1272528294816#com.sap.engine.services.WebContainer#sap.com/com.sap.engine.docs.examples#com.sap.engine.services.WebContainer#J2EE_GUEST#0##n/a##e54700ce536511dfb80c005056906bab#SAPEngine_Application_Thread[impl:3]_33##0#0#Path##Java###Exception #1#: Error while compiling JSP file [D:/usr/sap/EC6/DVEBMGS00/j2ee/cluster/server0/apps/sap.com/com.sap.engine.docs.examples/servlet_jsp/_default/root/main.jsp].
java.lang.Exception
 at com.sap.exception.BaseExceptionInfo.traceAutomatically(BaseExceptionInfo.java:1175)
 at com.sap.exception.BaseExceptionInfo.<init>(BaseExceptionInfo.java:263)
 at com.sap.engine.services.servlets_jsp.server.exceptions.WebServletException.<init>(WebServletException.java:57)
 at com.sap.engine.services.servlets_jsp.server.jsp.exceptions.CompilingException.<init>(CompilingException.java:67)
 at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.generateJavaFile(JSPParser.java:384)
 at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:107)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.getClassName(JSPServlet.java:242)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.reCompileAndGetClassName(JSPServlet.java:532)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:181)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: java.lang.NullPointerException
 at com.sap.engine.compilation.ExternalCompiler.getErrorMessage(ExternalCompiler.java:188)
 at com.sap.engine.services.servlets_jsp.server.jsp.JavaCompiler.compileExternalWithCompilationLib(JavaCompiler.java:109)
 at com.sap.engine.services.servlets_jsp.server.jsp.JavaCompiler.compile(JavaCompiler.java:319)
 at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.generateJavaFile(JSPParser.java:369)
 at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:107)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.getClassName(JSPServlet.java:242)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.reCompileAndGetClassName(JSPServlet.java:532)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:181)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
#1.5 #005056906BAB016C000010CC00002A380004855B94FA06F2#1272528294816#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/com.sap.engine.docs.examples#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#J2EE_GUEST#0##n/a##e54700ce536511dfb80c005056906bab#SAPEngine_Application_Thread[impl:3]_33##0#0#Error##Plain###application [/] Processing HTTP request to servlet [jsp] finished with error. The error is: com.sap.engine.services.servlets_jsp.server.jsp.exceptions.CompilingException: Error while compiling JSP file [D:/usr/sap/EC6/DVEBMGS00/j2ee/cluster/server0/apps/sap.com/com.sap.engine.docs.examples/servlet_jsp/_default/root/main.jsp].
 at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.generateJavaFile(JSPParser.java:384)
 at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:107)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.getClassName(JSPServlet.java:242)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.reCompileAndGetClassName(JSPServlet.java:532)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:181)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: java.lang.NullPointerException
 at com.sap.engine.compilation.ExternalCompiler.getErrorMessage(ExternalCompiler.java:188)
 at com.sap.engine.services.servlets_jsp.server.jsp.JavaCompiler.compileExternalWithCompilationLib(JavaCompiler.java:109)
 at com.sap.engine.services.servlets_jsp.server.jsp.JavaCompiler.compile(JavaCompiler.java:319)
 at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.generateJavaFile(JSPParser.java:369)
 ... 19 more
</pre>

Application error occurred during the request procession.

Hi all
i am geeting this error when i am ruuning my JSP page through NWDS.
Application error occurred during the request procession.
Details: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException:
Error compiling [/InvokeProxy.jsp] of alias [ProxySenderWeb] of J2EE application [sap.com/Refrence].
Exception id: [001279D06B4E00C6000027C700002DFC000445047AAE5AD8]
Thanks in advance

Dear Kunnal,
Please share your solution with the community.
Thank you.

Error: "Application error occurred during the request processing

Hello,
I have successfully installed NW7 CE with MaxDB database. Then trying to logon to NWA/User Admin etc, & couldn't logon. Getting the following error.
I am using Internet exploreer 7
500   Internal Server Error
SAP NetWeaver Application Server 7.11 / AS Java 7.11
Error: "Application error occurred during the request processing."
Troubleshooting Guide https://sdn.sap.com/irj/sdn/wiki?path=/display/jsts/home
Details: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to retrieve client for current request. Causing exception is nested.
     at com.sap.tc.webdynpro.clientserver.task.Task.getClient(Task.java:493)
     at com.sap.tc.webdynpro.serverimpl.wdc.um.ClientUserFactory.checkAuthentication(ClientUserFactory.java:200)
     at com.sap.tc.webdynpro.serverimpl.core.um.AbstractClientUserFactory$1.checkAuthentication(AbstractClientUserFactory.java:151)
     at com.sap.tc.webdynpro.services.sal.um.api.WDClientUser.checkAuthentication(WDClientUser.java:214)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.checkAuthentication(RequestManager.java:713)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:237)
     at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)
     at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
     at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
     at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
     at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)
     at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)
     at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)
     at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
     at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:54)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
     at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
     at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:240)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:425)
     at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:250)
     at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Caused by: com.sap.tc.webdynpro.services.cal.core.exceptions.WDClientException: Found no client: clientNameReqParam=null, clientNameAppParam=null, useragent=Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; Trident/4.0; GTB6; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
     at com.sap.tc.webdynpro.clientserver.cal.ClientInspector.findClientContainer(ClientInspector.java:212)
     at com.sap.tc.webdynpro.clientserver.cal.ClientInspector.getClient(ClientInspector.java:104)
     at com.sap.tc.webdynpro.clientserver.task.Task.getClient(Task.java:491)
     ... 51 more
Checked hostname resolution, check any network issues...everything looks good. Suggest a solution.

It's a problem with the browser.
Please try the following possiblities:
- use a different browser or at least a different IE-Version
- restart the problems (helped me several times)
- try comptability view in IE
Regards
Adrian

C370 - 7.6.3-019 An application fault occurred: ('snmp/ipmi_handlers.py _handle_fan_result|370'

Similar Messages

Maybe you are looking for