Why are there HTTP 413 errors (“Entity too large” in IIS) in IE10?

Several TRIRIGA users are receiving HTTP 413 errors (“Entity too large” from IIS) under Internet Explorer 10 (IE10). The problem may be caused by a very large page that is exceeding the size of the browser’s cache…

In an effort to fix this issue, the uploadReadAheadSize (IIS) was increased from the default of 48K up to 128K, and the responseBufferLimit (webconfig) from the default of 4M to 16M. We also attempted to clear the browser cache. None of these changes resolved the problem. Finally, we identified a very large page that was exceeding the size of the browser’s cache limitation.

To resolve the problem, increase the size of the browser cache. For Internet Explorer 10, navigate to Settings > Internet Options, select Settings in the “Browsing History” section, then select the “Caches and Databases” tab. The default value might be 10 MB. After increasing it to 25 MB, there were no further problems.

[Admin: To see other related posts, use the Internet Explorer tag or Browser tag.]

Advertisements

IV97614: Cannot revise project in Schedule tab with Gantt section

If you attempt to revise a project from the Schedule tab, where the Gantt chart is visible, your session is expired and you receive an invalid session error. The issue was observed in Internet Explorer and Chrome, but not in Firefox.

An analysis from a Fiddler trace shows that when revising the project in Chrome, this POST to GanttDataUpload.jsp seems to kill the session. In Firefox, for whatever reason, this POST doesn’t occur, and the state transition is successful. To confirm that this is the scenario you are experiencing, use the following technote to run a Fiddler trace and check for the same GanttDataUpload.jsp call: IBM TRIRIGA using Fiddler for tracing web browser traffic.

As a temporary fix, use Firefox. When the record is in a read-only state, no Save action should be called on the Gantt. Moving forward, we resolved the session-kill issue when the user performs a Revise action on a project in the Schedule tab.

[Admin: This post is related to the 08.18.15 post about using Fiddler to trace TRIRIGA web traffic. To see other related posts, use the Gantt tag or Fiddler tag.]

Why does the Print Preview in IE11 print a blank page?

We are currently using TRIRIGA 10.5.1/3.5.1.1. In IE11, when a record is selected to print, the printer gives a blank page. Whereas before printing, selecting Print Preview shows the page correctly. This behavior was not observed with Google Chrome, where everything gets printed without any issues.

After further investigation, it looks like a Microsoft Windows Update broke this print functionality, and they have since reverted the change that broke it. If you are on the absolute latest IE11 patch, the Print Preview should be working again. Take a look at this blog link. Microsoft has released KB4032782 to address the issue.

[Admin: This post is related to the 11.07.16 post about the font in the Print Preview and printed hardcopy being too small. To see other related posts, use the Print tag or Print Preview tag.]

IV96587: Getting error that URL is too large for queries with filters

After applying the TRIRIGA 3.5.2.2 fix pack, if you have an editable query with at least 10 filter columns, when you filter on the report, you will get the URL error.

We needed to implement the same code from viewPageReport.jsp to viewPage.jsp. Moving forward, we resolved an issue, where filtering on an editable query will make the URL big enough to break the specified limit for URLs on Internet Explorer.

[Admin: A similar article is also posted in the IBM TRIRIGA blog. This post is related to the 05.18.17 post about reports with filters creating long URIs in 3.5.2.2. To see other related posts, use the Filter tag.]

IV96356: Portal sections not sizing correctly within panel in IE only

Panels that didn’t have vertical scrolling in-frame now have vertical scroll bars. That is, they are not presenting the whole information within the visible area as before. Frames and portal sections are not sized correctly and some clickable areas might not work until some other action is performed. This is a change in behavior from TRIRIGA 3.5.1 to 3.5.2 when this behavior could be observed for customized forms.

Internet Explorer does not correctly calculate the new height of the content internal to the portal. We needed to rework the logic to resize to the actual content size. Moving forward, an issue that caused an extra scroll bar to appear when rendering a record in the portal has been resolved.

[Admin: To see other related posts, use the Portal tag.]

Why does accessing the 3.5.2 Admin Console result in a blank screen?

We’ve noticed with the change from TRIRIGA 3.5.1 to 3.5.2, there is some strange behavior when switching to the Admin Console. First, after logging into the front end of TRIRIGA (http://{servername}:9080), and second, after attempting to switch to the Admin Console (http://{servername}:9080/html/en/default/admin), this results in a blank screen (both in IE and Chrome).

It is necessary to close the window or clear the browser cache in order to access the Admin Console successfully. Is this intentional security behavior or something that we have misconfigured?

This is a known issue that was regressed with the security changes in 3.5.2. The workaround is to make sure you specify the endpoint for either page:

• Instead of {servername}:9080, use => {servername}:9080/index.html
• Instead of {servername}:9080/html/en/default/admin, use => {servername}:9080/html/en/default/admin/index.jsp

IV94622: Maximum length for URL field type is 400 characters

In TRIRIGA 3.5.2, the maximum length for the URL field type is 400 characters. The maximum URL/URI length for the URL field type must be 2083 characters to respect the Microsoft browser specification. Since TRIRIGA may need to store long URIs provided from IBM and external integrations, we extended the URL field type length.

Moving forward, URL fields can now handle a maximum of 2083 characters. The 2083 is the least common denominator in length of characters for supported browsers. Microsoft Internet Explorer (IE) has a maximum URL length of 2083. New URL fields will be created with a max length of 2083 characters. Existing URL field lengths will remain untouched until the BO is republished.