COGNOiSe.com - The IBM Cognos Community

IBM Cognos 10 Platform => Cognos 10 BI => Cognos Connection, Viewer, Scheduler => Topic started by: tallsup336 on 30 Sep 2015 02:05:20 PM

Title: Page can't be displayed error
Post by: tallsup336 on 30 Sep 2015 02:05:20 PM
We are using Cognos 10.2.1 and it is secured using https on the Gateway servers.  Everything works correctly for users and they are able to run RS reports, PowerPlay reports and Cognos Workspace Advanced reports.  But as soon as another application is opened in the same IE session using https, Cognos will randomly get the "Page can't be displayed" message.  The users get this error when they try to run a report, click on folder tab, or use the return button on a report.  The users are able to press F5 and the page will then load and they can continue as normal.

If the users open a new session for Cognos and a new session for the other application, they will never see the error.

Has anyone seen this type of behavior with Cognos?  Thanks in advance for any help
Tina
Title: Re: Page can't be displayed error
Post by: bdbits on 04 Oct 2015 07:50:09 PM
Are you running the Cognos site in compatibility mode? I have IE11 and some here use IE10, and we do not have these problems. But we do have compatibility mode enabled, as specified below.

See http://www-01.ibm.com/support/docview.wss?uid=swg27042164 (http://www-01.ibm.com/support/docview.wss?uid=swg27042164).
Title: Re: Page can't be displayed error
Post by: tallsup336 on 06 Oct 2015 12:22:01 PM
Yes we are running the Cognos site in compatibility mode.
Title: Re: Page can't be displayed error
Post by: tallsup336 on 27 Oct 2015 10:28:50 AM
We found a solution to this issue.  The issue appears to be tied to our F1 load balancer.  There were settings that had to be modified that allowed the cookie to be larger.  Once this was modified, this error has not been recreated.
Title: Re: Page can't be displayed error
Post by: Brentnik on 14 Dec 2016 11:48:33 AM
We encountered the same issue (page can't be displayed errors) after enabling the Cognos Application Firewall (CAF). Apparently the CAF sends a bigger cookie. Once the network team increased the allowed cookie size through the ACE, the problem went away.  Thanks very much @tallsup336 for mentioning your solution; it was the clue needed that worked for us!
Cheers  :) ;)