Wanted to reach out to the community to see if anyone else is experiencing this issue. We have tried to work an SR on it, but just have not been getting anywhere w/support.
We recently upgraded from 188.8.131.52 to 184.108.40.206.
When using a SSL connection (https://...8094), our Discoverer Viewer IE users are encountering "Page cannot be found" errors when running reports and when trying to export. The problems are not encountered for users utilizing Firefox or Chrome, just IE.
A couple notes:
We've found that by dialing down the number of rows to display, that will most often allow the report to work, e.g. if the report is set to display 25 rows, the report will fail and we'll just get the IE "Page cannot be found". If we change the display rows to 5, then the exact same report with the exact same parameters will work. Although it would be nice to be able to display more than just 5 rows of data :-) .
When the report runs successfully, we've also found that users get a lot of failures when exporting to .XLS. Often they can be successful exporting to .csv instead of .xls, but some reports still fail to export .csv.
We didn't have any of these issues prior to upgrading from 220.127.116.11 to 18.104.22.168, and again the issues only impact IE users when connecting in SSL mode. If we test the exact same reports/parameters using a non-SSL connection (same web-server, just using http://....:8090 instead of https://.....:8094), everything works great. Something just doesn't seem to be compatible between IE, SSL and the Web Server for the page calls over some certain size.
Just wanted to reach out to see if any Disco Web Server gurus out there might have any ideas of things for us to try.
Thanks a ton!
Thanks for the FYI....I hope you guys get further w/Oracle than we did. They couldn't provide a solution for us and we had to revert back to 22.214.171.124 due the significant user impact it was causing. Hoping Oracle can eventually resolve it and then we'll take another run at the 126.96.36.199 (or later) upgrade.
So, I did this:
edited $INSTANCE_HOME/config/OHS/ohs1/ssl.conf file.
Commented/removed the following section (Took a backup of the file before modifying it)
BrowserMatch ".*MSIE.*" \
nokeepalive ssl-unclean-shutdown \
The Viewer problem seems to be gone. Oracle is adding a note to MOS for this issue, possibly with this solution.