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.]

Continue reading

Why does Outlook add-in connect to server when opening meeting?

When opening any meeting in the Microsoft Outlook calendar, the TRIRIGA Reserve Outlook add-in will connect to the TRIRIGA server and send a small package.

This happens regardless of whether the meeting was created with the TRIRIGA add-in or not. When opening an appointment (which has no participants, in contrast to a meeting), there is no connection to the TRIRIGA server. It can be reproduced by opening Fiddler, opening Outlook, and then opening any item in the calendar that has participants (i.e. a meeting).

The consequence of this is that a session is opened for the user on the TRIRIGA server, taking up capacity on the server, thereby reducing the number of real users that the system can support. Has anyone else noticed this behavior? Can it be changed through configuration?

Continue reading

How do you use Fiddler to trace TRIRIGA web traffic?

When using the IBM TRIRIGA product, I am experiencing an issue that might be related to the network layer and I want to trace the web traffic for troubleshooting purposes. How can I use Fiddler for that purpose? I need to trace and analyze the incoming and outcoming network package flow for my Internet Browser session while troubleshooting an issue impacting the IBM TRIRIGA product and I want to use Fiddler for this purpose.

Fiddler is a third-party tool for monitoring requests made and received by a web browser. This information is often invaluable when troubleshooting a problem with the IBM TRIRIGA product. Due to the nature of IBM TRIRIGA, an error message may not always display the true cause of the error. A Fiddler trace will help by logging all HTTP requests or responses that may have been made. Fiddler can be downloaded from the following URL… http://www.telerik.com/fiddler

Continue reading 

Troubleshooting interface display issues in IBM TRIRIGA

When you have portions of the data displayed incorrectly or not being displayed in the front end interface, you must collect a log that is more accurate for interface logging.

You can resolve simple interface issues by flushing the global cache via the Admin Console. If that does not resolve the issue, you can collect an interface log, collect a Fiddler trace, and contact IBM TRIRIGA Support to analyze the issue.

Continue reading 

Clicking on Geocode Address gives a 401 error

In the Integration Object execute history record, we are seeing the following text in the integration summary.

Error 401
FW-1 at fw72d: Unauthorized to access the document.
· Authorization is needed for FW-1.
and error:

Do you know what is causing this? There are no other errors on the server.log that tells me why its happening. I also enabled Fiddler with no luck. I also noticed that the custom task in the “Location – Synchronous – Geocode Address” workflow is failing. It doesn’t provide additional information and so that is why we had to check the execution history for the integration object of building.

Continue reading