Error While Accessing Web Dynpro application in Windows 8, Internet Explorer 10

[Former Member]

Hi Experts,

We have done SP level upgrade in our SBM portal and SAP CE recently to make the enviroment compatible with Windows 8 and IE 10, firefox 12.0.

In SBM Portal 7.02 SP9 to 7.02 SP12

In SAP CE from 7.2. SP03 to SP08.

After upgrade, when we access web dynpro application in Portal, It is showing the intial form. But when we navigate or click on some button. The loading is going on endlessly. We found the error details in CE server logs.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Failed to show error page for session expiration. RID=da674dac6bbc11e28b7400000050281e

[EXCEPTION]

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:457)

at com.sap.tc.webdynpro.clientserver.session.RequestManager$ExceptionHandler.handleExpiration(RequestManager.java:1149)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:351)

at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)

at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)

at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:55)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:734)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:361)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:478)

at com.sap.tc.webdynpro.serverimpl.wdc.ForwardServlet.doPost(ForwardServlet.java:63)

at com.sap.tc.webdynpro.serverimpl.wdc.ForwardServlet.doGet(ForwardServlet.java:31)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:734)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:403)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:203)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:440)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:429)

at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:82)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:268)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)

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:54)

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:447)

at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:264)

at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

Caused by: com.sap.tc.webdynpro.services.cal.core.exceptions.WDClientException: Found no client: clientNameReqParam=null, clientNameAppParam=null, useragent=Java/1.4.2_34

at com.sap.tc.webdynpro.clientserver.cal.ClientInspector.findClientContainer(ClientInspector.java:211)

at com.sap.tc.webdynpro.clientserver.cal.ClientInspector.getClient(ClientInspector.java:103)

at com.sap.tc.webdynpro.clientserver.task.Task.getClient(Task.java:455)

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Note:

After upgrade the same applications are working fine with Windows 7 IE 8 and Firefox. It is also working perfectly with Windows 8 , firefox 12.0.

We are looking for your help on this issue.

Thanks in Advance.

Best Regards,

Karthika

[hofmann]

When it comes to IE10 and Win8, read also the note https://service.sap.com/sap/support/notes/1785100 which is referenced in the PAM PDF.

[c_vdwouw]

We are currently facing the exact same problem with IE10. Our WDP's do work as expected outside of the portal. But within the portal a lot of actions (sometimes triggering dialog boxes, sometimes only triggering another view through firing a plug) end up with the loading image. In IE9 we do not have this problem

We have 7.3 EH1, SP5, which according to the PAM should support IE10. Unfortunately the note mentioned above (1785100) which explicitly is about IE10 support, is currently not available.

I'll be keeping an eye on this thread, or post a solution if we find one.

[hofmann]

I am accessing the note right now, so the note is available.

Some important remarks from the note:

• IE10 uses HTML5 quirks or standards mode per defualt. Many SAP  applications however require the older Quirks mode.
• The IE10 Interoperable HTML5 Quirks Mode is not supported.
• 64bit version of IE10 is not supported.

[c_vdwouw]

Hi Tobias,

According to the note it was released yesterday around 14:00h. About 30 minutes after my post, hence why I couldn't open it.;-)

Anyway, thanks for your reply. I'll look into the platforms architecture tomorrow. I'm not sure if it's 64-bit or not.

I've read the note, but what still puzzles me is the fact that all our Web dynpro's perfectly work outside of the portal, but acts weird within the portal (both standard portal desktop as in our custom desktop)

As we're running our own custom AFP desktop, I'll fiddle with the doctypes and see what happens

[Former Member]

Does SAP note 1814711 help?

https://service.sap.com/sap/support/notes/1814711

[hofmann]

Per default, the SAP Portal is trying to enforce the portal theme to WDA/J applications. Normally, the application server with the higher SP wins and you should be on the save side. In case your portal is on a lower SP and still wins the race, your WD apps may not work due to a CSS that is not compatible with IE10.

[c_vdwouw]

Hi, thanks again for your reply

Currently even in standard portal, opening for example the portal content studio, results in the portal showing the animated waiting gif indefinitely. The portal itself is still responsive, so I can navigate to other applications, like the UME. In the UME I can press the start button, which results in the table filled with users, but followed with again the waiting gif, leaving the UME application unresponsive.

This only occurs with IE10 64-bit. Since Microsoft is pushing this version, this becomes a serious problem which I hope will be addressed by SAP  

Also, when running _outside_ of the portal, this problem does not exist, for example by running the useradmin directly (http://<host>:50000/useradmin)

[c_vdwouw]

Thanks for your reply.

That note does not apply for our problem. We're using Wdp for Java.

[hofmann]

This only occurs with IE10 64-bit.

I am afraid that the above note (https://service.sap.com/sap/support/notes/1785100) applies as it is stated there that 64bit version of IE10 are not supported.

You can still open a OSS message and ask for clarification and also point out that you need IE10 64bit supported.

[amolgupta]

The issue if caused by higher version of the IE should be resolved by reading the following -

http://scn.sap.com/docs/DOC-28709

[junwu]

have you checked the PAM?  win 8 IE10 supported?