IBM Support

Page cannot be displayed error in Internet Explorer when executing the Open Portal option in a defined Remote Portal v6.0 server

Troubleshooting


Problem

Internet Explorer 6.x/7.x displays "Page cannot be displayed" when using an "Open Portal" option in a Portal v6.0 server which is remote and when "Enable Automatic Login" is checked.

Symptom

What has been done:

  1. Created a new Portal v6.0 server configuration connecting to a Remote Portal v6.0 server
    • Entered the Fully Qualified Name, clicked Next in the wizard.
    • Entered the WebSphere® Application Server (WAS) credentials, clicked Next.
    • Entered the Portal v6 Server credentials. Checked the Enable Automatic Login checkbox.
    • Clicked "Finish" to close the Server Configuration creation Wizard.
  2. Right-clicked on the defined Portal Server Configuration and clicked "Open Portal"

Internet Explorer 6.x (and 7.x) returns a "Page cannot be displayed" screen when you choose the Open Portal option in a Portal v6.0 server which is remote and when Enable Automatic Login is checked. This does not happen if you have Mozilla FireFox as your browser.


You will also see the following error in the Rational Application Developer (RAD) Console
00000069 WebApp E SRVE0026E: [Servlet Error]-[EJPSD0020E: The WAS request URL cookie was not found. This means the Login Redirector was invoked directly what is not supported.]: com.ibm.wps.auth.NoCookieSetException: EJPSD0020E: The WAS request URL cookie was not found. This means the Login Redirector was invoked directly what is not supported.
at com.ibm.wps.auth.LoginRedirector.doFilter(LoginRedirector.java:110)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:142)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:121)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:82)
at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor
.invokeFilters(DefaultExtensionProcessor.java:789)
at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor
.handleRequest(DefaultExtensionProcessor.java:581)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:2965)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:221)
at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:210)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1931)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:84)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink
.handleDiscrimination(HttpInboundLink.java:472)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink
.handleNewInformation(HttpInboundLink.java:411)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback
.complete(HttpICLReadCallback.java:101)
at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback
.complete(SSLReadServiceContext.java:1698)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager
.requestComplete(WorkQueueManager.java(Compiled Code))
at com.ibm.ws.tcp.channel.impl.WorkQueueManager
.attemptIO(WorkQueueManager.java(Compiled Code))
at com.ibm.ws.tcp.channel.impl.WorkQueueManager
.workerRun(WorkQueueManager.java(Compiled Code))
at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker
.run(WorkQueueManager.java(Compiled Code))
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))

Cause

This error occurs when the Web browser is not accepting cookies that are set by the portal server. There are two possible reasons for this:

  1. The Web browser is configured to not accept cookies.
  2. The host name of the portal server contains an invalid character, such as an underscore, which causes the Web browser to reject the cookies set by the portal server.

Environment

Internet Explorer 6.x or 7.x

Resolving The Problem

Workarounds:

  1. Uncheck the "Enable Automatic Login" option when defining the Remote Server configuration. You will have to log in to the Portal before the portlets are displayed.
  2. Make sure the Web browser is configured to accept cookies.
  3. Make sure the host name of the WebSphere Portal server does not contain invalid characters and conforms to the standards listed in RFC 952. You can use the IP address instead of the Portal DNS Name when creating the Portal v6 in the RAD v7 Server configuration.
  4. As an alternative you also can use an alternate browser like FireFox for display of your portlets.

[{"Product":{"code":"SSRTLW","label":"Rational Application Developer for WebSphere Software"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Portal \/ Portlet Development","Platform":[{"code":"PF033","label":"Windows"}],"Version":"7.0.0.3;7.0.0.4","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
16 June 2018

UID

swg21286399

Page Feedback