Blank browser window opens in RTC client when opening the Operation history of a stream

It's hard to say what exactly is going on (with out further information), but normally for Windows users, it will use IE as the embedded browser. Perhaps that user specifically removed IE from the computer (try re-installing IE).

As a workaround though, you can have this view open up in an external browser of your choice (vs using the embedded one in Eclipse). See the preference under "Team" --> "Jazz Source Control" --> and the "History Graph" group. It's always recommended to use the embedded one in the rich client though, as this allows the ability to use context menu actions (such as opening a selection of change sets in the Change Explorer view).

As another test, open up the view that comes with Eclipse called "Internal Web Browser" and try to go to some web pages (including the URL that represents the Operation History View.. if this view doesn't work at all, it at least suggests there is no issue on the RTC code side... and it's an issue with Eclipse trying to use the embedded IE browser.

(Please add as a comment any relevant results of your tests...)

This issue can be caused by the case of the Jazz Repository Connection URI configured in Eclipse.

For example, if the repository connection is "https://rationalalmserver.com/ccm/" operation history works okay

However, if instead a user enters "https://Rationalalmserver.com/ccm/" for the URI (note the difference is the case of the first "R" in "rational") then most RTC functionality works correctly, however operational history does not work, instead of opening the operation history in a history view, it opens a web page and Eclipse shows a progress bar "Fetching operation history" which is stuck at 0%.

To workaround the issue:

In Eclipse Team Artifacts view, in Repository Connections, select the repository connection with the issue, Right-Click and select Properties.

In Properties for the repository connection, Open Jazz Repository Connection property, and check the URI has been entered with the correct case.  If it has not been entered with precisely the correct case, then create a completely new Eclipse Client workspace and setup a connection to the server with the correct case (note that just modifying the case within the existing workspace may cause unexpected results, the easiest approach is to create a new workspace and delete the previous one).