I do not think that this is a security-related issue.
My Teammate believes that the problem is due to a deficiency in the TruClient protocol wherein it does not know how to handle client-side popups. In this use case, for example, in one step, we need to "browse" for the desired file to send using QuickFile. When the user clicks browse, a Windows popup file system navigation window opens, allowing the user the ability to find the target file. Once they "Open" the file, the window disappears. Unfortunately, in LoadRunner TruClient, the popup is displayed, but does not close. As a result, the next step, pressing the Send button does not really work, even though the step is determined to be successful by LoadRunner. Note: I can manually intervene in the playback and close the popup. The use case then succeeds.
As a result, my Teammate and the rest of my Team are going to try to use the Web protocol to test QuickFile, which I am sure will be quite a nightmare. I am less than optimistic.
I have only a couple of days to complete this testing engagement, but I anticipate failure because of an inability to build a working script in a timely fashion.
I have communicated this type of experience to the HP R&D Team, and they promise to continue to make TruClient better. In the mean time, I am stuck with another testing project failure. I will add it to my list, which seems to be growing these days. I think this is number 4 in the past 6 months.