Permanent solution for Java iView Runtime error ?
Hi
I have SAP IDES installed in my system...recently i am getting following error when i am trying to login Portal :
Java iView Runtime
Copyright 2002 SAP AG. All rights reserved.
An exception occured while processing your request.
If this situation persists, please contact your system administrator.
I have searched SDN many discussions say that restart server and check memory and...etc......etc
My system also if i restart server problem is solved temprarely....
My system memory is not a problem because i have 16GB Ram amd 1 Tera hard disk still i have 500 GB hard diskk free space...
If i restart simply MMC my J2ee table will not connected so i have to restart hole sytem them start MMC .....then server is up and i can connect to portal .......it seems connection for j2ee table are getting lost.....
Can some one suggest me permanent solution
thanks in advance
Hi Maya,
BEx Web Analyzer requires Portal and is basically a Web template called 0ANALYSIS_PATTERN.
Is Portal configured in your system landscape? If yes try to see if its configured probably using transaction RSPOR_CUST01.
If you have access to SM59, you can test the RFC connection to the portal by running the Test Connection for the corresponding RFC destination ID that you see in RSPOR_CUST01 transaction.
Assign points if helpful
Regards, Uday
Similar Messages
-
Java Iview Runtime error after logon
Hello,
we are facing some problem regarding our EP 7.0 SP13. We have an anonymous page as our home page, with some anonymous ivews, like "help", "news", etc and one iview with authentication set to default where users log into the portal and access to the private section of the portal.
That ivew does a redirection to /irj/portal and since the user is athenticated it will led him to the private home. The problem is that after logon, a Java iview runtime error appears, and users must refresh the browser to access the private section. (user is logged before the error appears).
We have checked this is not happening with users with "super admin" o "content admin" role. They are able to log into the portal, and redirection is working fine. So we think there can be some problem with security zones or authentication somewhere in the portal, but since this is the standard logon component i don´t know why is this not working.
We have checked that the redirection is working, and we have made some tests with different kind of iviews like KM iviews, URL iviews, pictures, etc. Only admin users are able to log in correctly, the others get the java iview runtime error, so we think the problem is with to standard logon...
Here goes a trace of our problem (defaultrace.trc):
#1.5 #000802B3F434005C00000434000024680004646E64997E00#1236325203820#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection#
#1.5 #000802B3F434005C00000435000024680004646E64998C55#1236325203820#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:304)#
#1.5 #000802B3F434005C00000436000024680004646E64998E05#1236325203820#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)#
#1.5 #000802B3F434005C00000437000024680004646E6499900A#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at java.security.AccessController.doPrivileged(Native Method)#
#1.5 #000802B3F434005C00000438000024680004646E64999183#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)#
#1.5 #000802B3F434005C00000439000024680004646E649992D1#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
#1.5 #000802B3F434005C0000043A000024680004646E6499941A#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)#
#1.5 #000802B3F434005C0000043B000024680004646E6499955B#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
#1.5 #000802B3F434005C0000043C000024680004646E64999690#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)#
#1.5 #000802B3F434005C0000043D000024680004646E6499984F#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)#
#1.5 #000802B3F434005C0000043E000024680004646E6499999C#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)#
#1.5 #000802B3F434005C0000043F000024680004646E64999AEB#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)#
#1.5 #000802B3F434005C00000440000024680004646E64999C2F#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)#
#1.5 #000802B3F434005C00000441000024680004646E64999D76#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)#
#1.5 #000802B3F434005C00000442000024680004646E64999EDA#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)#
#1.5 #000802B3F434005C00000443000024680004646E6499A01D#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)#
#1.5 #000802B3F434005C00000444000024680004646E6499A15E#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)#
#1.5 #000802B3F434005C00000445000024680004646E6499A30A#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)#
#1.5 #000802B3F434005C00000446000024680004646E6499A479#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
#1.5 #000802B3F434005C00000447000024680004646E6499A5B7#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at java.security.AccessController.doPrivileged(Native Method)#
#1.5 #000802B3F434005C00000448000024680004646E6499A718#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)#
#1.5 #000802B3F434005C00000449000024680004646E6499A855#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)#
#1.5 #000802B3F434005C0000044A000024680004646E6499B6CC#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: PortalRuntimeException#
#1.5 #000802B3F434005C0000044B000024680004646E6499B86B#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:284)#
#1.5 #000802B3F434005C0000044C000024680004646E6499BA7E#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### ... 20 more#
#1.5 #000802B3F434005C0000044D000024680004646E6499CB8B#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.core.PortalRequestManagerException: PortalRuntimeException#
#1.5 #000802B3F434005C0000044E000024680004646E6499CD54#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:143)#
#1.5 #000802B3F434005C0000044F000024680004646E6499CE9B#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)#
#1.5 #000802B3F434005C00000450000024680004646E6499CFDD#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)#
#1.5 #000802B3F434005C00000451000024680004646E6499D130#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sapportals.portal.prt.connection.ContentExceptionHandler.handleException(ContentExceptionHandler.java:100)#
#1.5 #000802B3F434005C00000452000024680004646E6499D277#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sapportals.portal.prt.connection.ContentExceptionHandler.handlePortalRuntimeException(ContentExceptionHandler.java:27)#
#1.5 #000802B3F434005C00000453000024680004646E6499D512#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.handleRequestException(PortalRequestManager.java:917)#
#1.5 #000802B3F434005C00000454000024680004646E6499D677#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:803)#
#1.5 #000802B3F434005C00000455000024680004646E6499D7F3#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)#
#1.5 #000802B3F434005C00000456000024680004646E6499D943#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### ... 20 more#
#1.5 #000802B3F434005C00000457000024680004646E6499EB58#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###Caused by: java.lang.UnsupportedOperationException: this implementation does not support getComponentContext()#
#1.5 #000802B3F434005C00000458000024680004646E6499ECFD#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sapportals.portal.prt.service.hook.RedirectNode.getComponentContext(RedirectNode.java:50)#
#1.5 #000802B3F434005C00000459000024680004646E6499EE40#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:343)#
#1.5 #000802B3F434005C0000045A000024680004646E6499EF97#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:238)#
#1.5 #000802B3F434005C0000045B000024680004646E6499F0E1#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)#
#1.5 #000802B3F434005C0000045C000024680004646E6499F21D#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain### ... 27 more#
can anyone help us with this problem?
Thanks in advanceThe problem was solved, it was a permission problem.
The anonymous role which allow access to the anonymous section of the portal was assigned to anonymous user, but it hasn´t everyone permission. So anonymous users were able to see anonymous pages, but when they login they lose the role, and java iview error happened, unless they had admin rights.
Solved assigned by assigning everyone to that role.
Thanks -
Java iview runtime error occuring in EP
Dear Friends ,
We are currently getting java iview runtime error while trying to
access EP logon screen through one of our application server.
We are not facing any errors while trying to access the same logon
screen through the other 2 application servers.
Please look into this issue.
Regards
GauravHi,
Check whether is there any network problem between application server and CI.
This problem generally comes when there is a problem between connection of UME.
Thanks
Anil -
Java Iview runtime error for WAD 7.0
Hi,
When I try to open Web Application designer of 7.0 from Start>Programs>Business explorer> Web application designer, the system is popping up to enter the userid &password after entering it , I cannot see any screen, when I asked my team member about this he told that the IT still did not release the 7.0 Web application designer and he told me to use 3.X Web application designer ,but when I try to open in rrmx my going to meu oprtion BEX Analyzer>Tools -->BEx web analyzer then its opening in the internet explorer and giving me the message
Java iView Runtime
An exception occured while processing your request.
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:304)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
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:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.NullPointerException
at com.sapportals.portal.prt.service.authenticationservice.AuthenticationService.getLoggedInUser(AuthenticationService.java:333)
at com.sapportals.portal.prt.connection.UMHandler.handleUM(UMHandler.java:96)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:186)
... 20 more
If this situation persists, please contact your system administrator
What could be the ProblemHi Maya,
BEx Web Analyzer requires Portal and is basically a Web template called 0ANALYSIS_PATTERN.
Is Portal configured in your system landscape? If yes try to see if its configured probably using transaction RSPOR_CUST01.
If you have access to SM59, you can test the RFC connection to the portal by running the Test Connection for the corresponding RFC destination ID that you see in RSPOR_CUST01 transaction.
Assign points if helpful
Regards, Uday -
Java Iview Runtime error at the time of logon
Hi All
i am getting the below error page instead of Portal log on Page.
At the same time when i am connecting to the NWA it is opening successfully,
There I am getting the login Page also.
But when i am trying http://<Server>:50000/irj/portal.
i am getting below error.
Java iView Runtime
Copyright 2002 SAP AG. All rights reserved.
An exception occured while processing your request.
If this situation persists, please contact your system administrator.
I have not touch the portal logon Page.
Neither i have modified any standard Portal page.
Kindly help me with you valuable suggestion and document.
It is effecting the business process of client.
Prashant krishenHi Robin,
Thanks for immediate response.
Please help me to find out the log.
i am using this path :
http://<Server>/irj/servlet/prt/portal/prtroot/com.sap.portal.runtime.admin.logviewer.defau
But here in the default trace there are so many default trace file like
defaultTrace.0.trc ;
defaultTrace.1.trc ;
defaultTrace.2.trc ;
defaultTrace.3.trc
defaultTrace.4.trc ;
defaultTrace.5.trc ;
in all the file date has not been maintained. That is why i am not able to send you the exact log .
kindly help me to find the log .
thanx in Advance. -
Problem in logging onto portal "Java iView Runtime " error
Hi,
We are getting the following message when trying to logon to the portal.
"Java iView Runtime
Version : 5.0.200212121529
(c) 2001 SAP Portals
The following exception occured while processing your request:
com.sapportals.portal.prt.runtime.PortalRuntimeException: delegatedplugin
Exceptions details :
com.sapportals.portal.prt.runtime.PortalRuntimeException: delegatedplugin
at com.sapportals.portal.prt.portalconnection.sapnative.DelegatedPlugIn.handleRequest(DelegatedPlugIn.java:1044)
at com.sapportals.portal.prt.portalconnection.sapnative.PortalPlugIn.handleRequest(PortalPlugIn.java:132)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:635)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:149)
at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:833)
at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:672)
at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:314)
at com.inqmy.services.httpserver.server.Response.handle(Response.java:173)
at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1288)
at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
at com.inqmy.core.cluster.impl3.ParserRunner.run(ParserRunner.java:30)
at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
at java.security.AccessController.doPrivileged(Native Method)
at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
Caused by: javax.naming.NameNotFoundException: PortalLicense not found
at com.sapportals.portal.prt.service.jndi.PortalServiceProviderContext.lookup(PortalServiceProviderContext.java:58)
at com.sapportals.portal.prt.service.jndi.PortalServiceProviderContext.lookup(PortalServiceProviderContext.java:65)
at javax.naming.InitialContext.lookup(InitialContext.java:345)
at com.sapportals.portal.prt.portalconnection.sapnative.DelegatedPlugIn.handleRequest(DelegatedPlugIn.java:240)
at com.sapportals.portal.prt.portalconnection.sapnative.PortalPlugIn.handleRequest(PortalPlugIn.java:132)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:635)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:149)
at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:833)
at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:672)
at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:314)
at com.inqmy.services.httpserver.server.Response.handle(Response.java:173)
at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1288)
at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
at com.inqmy.core.cluster.impl3.ParserRunner.run(ParserRunner.java:30)
at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
at java.security.AccessController.doPrivileged(Native Method)
at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
If this situation persists, please contact your system administrator"
Tried restarting the portal servers but the problem still persists.
Request you to please suggest the solution for the same.Hi Sireesha,
When it is working last time.
Are any changes made to portal recently
may be it is a permission issue in security zones.
Below links may help you.
http://help.sap.com/saphelp_nw04s/helpdata/en/25/85de55a94c4b5fa7a2d74e8ed201b0/content.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/ee/acd8403e37762ae10000000a155106/content.htm
Raghu -
Java iView Runtime error occurs whilw changing Theme Editor
Hi,
i have to face the following error while changing Theme.
<b>Java iView Runtime
Version : 6.4.200512140312
+ Copyright 2002 SAP AG. All rights reserved.
An exception occured while processing your request.
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:304)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
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:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: PortalRuntimeException
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:284)
... 20 more
Caused by: java.lang.OutOfMemoryError
If this situation persists, please contact your system administrator.</b>
Please give me right solution.
Thanks & Regards,
Nisarg PatelHi,
Try out the answers given in the following threads:
Theme Editor : Runtime error
Problem with Theme Editor
Regards,
Pooja. -
Java iView Runtime Error while loading EP Logon page
hi,
When i load my Enterprise Portal from the url http://epserver:50000/irj/portal i am getting the following error page.
Anyone please help me in this issue.
The Error Page content is given below:
Java iView Runtime
Version : 6.4.200410200018
+ Copyright 2002 SAP AG. All rights reserved.
An exception occured while processing your request.
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:296)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
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.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:316)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:372)
at com.sap.portal.navigation.Gateway.service(Gateway.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: PortalRuntimeException
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:276)
... 24 more
Caused by: com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component : com.sap.portal.runtime.system.hooks.ErrorComponent
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
at com.sapportals.portal.prt.connection.ContentExceptionHandler.handleException(ContentExceptionHandler.java:67)
at com.sapportals.portal.prt.connection.ContentExceptionHandler.handlePortalRuntimeException(ContentExceptionHandler.java:27)
at com.sapportals.portal.prt.core.PortalRequestManager.handleRequestException(PortalRequestManager.java:917)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:803)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
... 24 more
Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.prt.component.error.ErrorComponent of Portal Component com.sap.portal.runtime.system.hooks.ErrorComponent because: Could not instantiate implementation class
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:269)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
... 32 more
Caused by: com.sapportals.portal.prt.core.broker.PortalApplicationNotFoundException: Could not find portal application com.sap.portal.themes.lafservice
at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:413)
at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:385)
at com.sapportals.portal.prt.core.broker.PortalApplicationItem._refresh(PortalApplicationItem.java:505)
at com.sapportals.portal.prt.core.broker.PortalApplicationItem.getCoreLoader(PortalApplicationItem.java:1334)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.getClassLoader(PortalComponentItem.java:569)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getClassLoader(PortalComponentItemFacade.java:102)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
... 36 more
If this situation persists, please contact your system administrator.hi sir,
i checked that .... J2ee Service is running.
Sorry for not including default.trc log file error in my first message.
Here it is ...
JMX connector exception occurred while processing external JMX request [ JMX request (java) v1.0 len: 314 | src: cluster target-node: 3584000 req: invoke params-number: 4 params-bytes: 0 | :name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=3584000,SAP_J2EECluster="" null null null ]
[EXCEPTION]
com.sap.engine.services.jmx.exception.JmxConnectorException: Unable to de-serialize request parameters, message [ JMX request (java) v1.0 len: 314 | src: cluster target-node: 3584000 req: invoke params-number: 4 params-bytes: 0 | :name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=3584000,SAP_J2EECluster="" null null null ]
at com.sap.engine.services.jmx.RequestMessage.readParams(RequestMessage.java:531)
at com.sap.engine.services.jmx.RequestMessage.getParams(RequestMessage.java:580)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:90)
at com.sap.engine.services.jmx.JmxServiceConnectorServer.receiveWait(JmxServiceConnectorServer.java:172)
at com.sap.engine.core.service630.context.cluster.message.MessageListenerWrapper.process(MessageListenerWrapper.java:81)
at com.sap.engine.core.cluster.impl6.ms.MSListenerThread.run(MSListenerThread.java:47)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)
at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)
Caused by: javax.management.InstanceNotFoundException: MBean with name com.sap.default:name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=3584000,SAP_J2EECluster=NET not found in repository
at com.sap.pj.jmx.server.MBeanServerImpl.getClassLoaderFor(MBeanServerImpl.java:1408)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getClassLoaderFor(MBeanServerWrapperInterceptor.java:455)
at com.sap.engine.services.jmx.CompletionInterceptor.getClassLoaderFor(CompletionInterceptor.java:576)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getClassLoaderFor(BasicMBeanServerInterceptor.java:438)
at com.sap.jmx.provider.ProviderInterceptor.getClassLoaderFor(ProviderInterceptor.java:330)
at com.sap.engine.services.jmx.RedirectInterceptor.getClassLoaderFor(RedirectInterceptor.java:501)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getClassLoaderFor(MBeanServerInterceptorChain.java:443)
at com.sap.engine.services.jmx.RequestMessage.readParams(RequestMessage.java:525)
... 8 more -
Java iView runtime error while portal startup
Hi ,
I am facing a problem in starting up the portal .
It was working Fine, But i had to restart it manually through the visual administrator .The J2ee server has started up but not the portal .
following is the error i am getting
Java iView Runtime
Version : 6.4.200512140312
+ Copyright 2002 SAP AG. All rights reserved.
An exception occured while processing your request.
com.sapportals.portal.prt.dispatcher.DispatcherException: Could not find connection portal
com.sapportals.portal.prt.dispatcher.DispatcherException: Could not find connection portal
at java.lang.Throwable.<init>(Throwable.java:194)
at java.lang.Exception.<init>(Exception.java:41)
at com.sapportals.portal.prt.dispatcher.DispatcherException.<init>(DispatcherException.java:45)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:528)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
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.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:312)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:368)
at com.sap.portal.navigation.Gateway.service(Gateway.java:101)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:30)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:35)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:99)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
If this situation persists, please contact your system administrator
Restarting the whole system didn't help too.
I found that ppl faced this problem , but there was no solution given to any . Can anyone help me in bringing up the portal
Thanks in Advances
LakshmiHi Vaibhav ,
DB is running fine , J2EE server is also up .
Below is the log from defaulttrace. we got an error while deploying a par file, and it didn't let us to deploy any par files , then we restarted the system and since then we are facting htis problem. Any chances that an application arroe could bring the whole portal server down? If so can you let me know how to trace and fix it
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process<u><b>(ApplicationSessionMessageListener.java:30)#</b></u>
_0##0#0#Error##Plain###<u><i><b>com.sapportals.portal.prt.dispatcher.DispatcherException: Could not find connection portal#</b></i></u>
#1.5#000255532C17004000000AE6000008370004108DF574116A#1144101801300#System.err#sap.com/irj#System.err#Guest#647####aa09ba30c35d11dab15d000255532c17#SAPEngine_Application_Thread[impl:3]_0##0#0#Error##Plain### at java.lang.Throwable.<init>(Throwable.java:194)#
#1.5#000255532C17004000000AE7000008370004108DF57411DA#1144101801300#System.err#sap.com/irj#System.err#Guest#647####aa09ba30c35d11dab15d000255532c17#SAPEngine_Application_Thread[impl:3]_0##0#0#Error##Plain### at java.lang.Exception.<init>(Exception.java:41)#
Thanks,
lakshmi -
Java iView runtime error on portal 7.3
Hi Experts
There is a specific user who is facing an issue with our client portal version 7.31.
When the user is trying to access portal link, an error message is observed for the user.This message comes instead of the logon page.
Error message details :
Java iView Runtime
An exception occured while processing your request.
Please help to resolve the same.
The same user is able to logint though citrix.
Regards
ShailyHi Shaily,
If this is just happening for one particular user and the same user is able to access the portal through Citrix, this could be a browser issue.
Please ask the user to clear the browser cookies / cache and then try again.
Hope he is using the <FQDN> while accessing the Portal Url.
BR,
Anurag -
Java iView Runtime Error in BEx Designer
Hi,
Through analyzer, Query is working absolutely fine
When trying to run a query via the query designer I get the two messages :
1.In development
Java iView Runtime
copyright 2002 SAP AG.All rights reserved.
An exception occured while processing your request.
If this situation persists,please contact your system administrator
2.and in Quality
503 Service Unavailable
Application Stopped
Thanking you,
Tarun Brijwani.Hi,
Thank you very much for your reply.
From your reply, I have some doubts.
You mentioned that you reduced the no of info objects in the rows in query definition and the problem got solved.
1.Did you check that for the some queries which were already containing less no.of rows, it did not show this error.
2.And you were getting this this error only in the those particular queries which were containing more no.of rows?
3.Have you again tried by placing more no.of info objects in rows after you solved the error?
Please reply even if you didn't try all these things coz it will be very helpfull for us in further investigation.
Thanking You,
Tarun Brijwani.
Edited by: Tarun Brijwani on Feb 6, 2009 12:02 PM -
Java iview Runtime error in Portal Logon
hi
I login portal with
http://<ipaddress>:50000/irj/portal
Java iView Runtime
An exception occured while processing your request.
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection
If this situation persists, please contact your system administrator.
Can any one help me,,,how to sort this error.
Regards
sushmaHi Sushma,
It seems that there are problems with permissions in Security Zones.
Check this links below to know more:
http://help.sap.com/saphelp_nw04/helpdata/en/25/85de55a94c4b5fa7a2d74e8ed201b0/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ee/acd8403e37762ae10000000a155106/content.htm
Thanks
Mihir -
Java iView Runtime error when try connectin to portal
H, iin my VC i have filled in the address of my portal http://address:50000
Then i click the traffic light icon, and giving me a popup
windows that saying Java iView Runtime
I wonder what could be wrong, i have deployed the portal content and visual composer sda.
And i'm using super userIn fact we're not quite sure on what exactly caused the problem ...
What we did was :
- deploy from NWDS of Webdynpros ... but we don't see how an apllication deployment may has caused a such big issue
- we also enabled 2 services in the portal : Activity Reporting service and Activity data Collector ... may enabling these 2 services have cause this global issue ?
Thanks for your quick response,
Regards, -
Java iView Runtime Error While Report
Hi,
I am Angeline, I having some problem when I click Export to Excel from web-reporting... under NW 2004s, BI 7.0 Windows 2003 server all updated JDK, JRE, Framworks
Report shows in Potals but when I click on Export to Excel It does blow errors:
Remember Report has more then 80000 Records
Error:
JAVA iView Runtime
Copyright 2002 SAP A.G. All rights reserved
An exception occured while processing your request.
If this situation presist, please contact your system administrator
I tried to clear cache, but there is not option to clear cache, so I restart server, I have 12GB memory in PRD server, I treid increase memory xxMaxSize 2GB, and J2EE Engine is running fine... check user authroziation works fine...
Please help me where is that problem, Remember Repoarts has more then 4000 records
Thanks in Advanced
Edited by: T A on Sep 1, 2009 7:06 PMProblem Solved by myself
Just incr. Heap memory now its ok -
We are having an intermittent problem when we go to hit the logout button the portal. It will sometimes come back with the following web pag dialog box:
Java iView Runtime
Version: 7.00.200705080819
+copyright 2002 SAP AG. All rights reserved.
AGain, it doesnt' happen all the time when we go to log off, just sometimes. Any ideas what might be causing this to happen. We are using EP 7.0 and just got upgrade to SPS12 Patch #3.Hi Kathy,
We are also facing the same problem on EP 7.0 SP13.
Can you kindly let us know what is the note number or patch that you had applied?
Thanks and regards
Aarthi
Maybe you are looking for
-
What cable do I use to connect my iBook to my iMac so it displays the iBook's screen?
What cable do I use to connect my iBook to my iMac so it displays the iBook's screen?
-
Flash Builder 4.5 and lccs.swc compatibility
Hi, I'm using Flash Builder 4.5 on Windows 7 trying to create a LCCS application, starting with the available LCCS examples. I installed the LCCS SDK. I updated to playerglobal.swc 10.3 and lccs.swc 10.3. Flash Builder is configured to use 10.3 versi
-
Auto Payment debit entries not considered
Dear All, As per our practice we make the payment to the vendors 03 days in advance prior to due date for Cheque issuing formalities. While processing auto payment System takes Invoices of these 3 days but It does not consider debit notes which are d
-
I am interested to get OC course material, could anyone help me in this? Thanks.
-
Plug-in stops in 1.3.1_02 (and _01a) with IE
We're having a problem with the latest versions of the plug-in. We've been using the plug-in in IE (various versions) for sometime with 1.3.0.4 and 1.3.1.1. However, when we try 1.3.1_01a and 1.3.1_02, the plug-in stops working: our html causes the p