There appears to be a problem with VuGen / TruClient / Controller when we replay scripts where there is an object timeout.
I ran my script around 150 times without any problem with an object timeout of 170 seconds. All of my transactions start well and end well. In the transaction editor, the start point is always triggered by “Step started” because I want to be sure this event is called every time. I read in another post that a user had problems ending some transactions and he therefore changed the end point event to something that always happen, such as “After step endend”. He did that because he got tricked sometimes by the “Step network completed event”. Other users fixed their problems by matchting their transaction end point event with the step end event.
But in my case, I have a problem with the start transaction operation which is not called every time even though the trigger is “Step started”. I got this error when I wanted to simulate a real life situation using TruClient options. I only changed the Wait for Object timeout after my login from 170 seconds to 16 seconds because I knew this value would generate some good and bad logins as if the server was slow sometimes.
START TRANSACTION LOGIN
Navigate www.xyz.com
Wait for Object ABC for 16 seconds
END TRANSACTION LOGIN
Starting iteration 4.
Starting action Action.
Notify: Transaction "711_S01_Fcogr_000_Login" started.
t=00128946ms: ** 1: Navigate to "https://www.abc.change.in.log.com ** started [MsgId: MMSG-205180]
t=00129492ms: ** 1: Navigate to "https://www.abc.change.in.log.com" ** successfully completed [MsgId: MMSG-205180]
t=00129513ms: ** 2: Wait for File d'attente textbox ** started [MsgId: MMSG-205180]
t=00145762ms: Error -205177: ** 2: Wait for File d'attente textbox ** failed - target object was not found. Snapshot Info [MSH 4 0] [MsgId: MERR-205177]
Ending action Action.
Notify: Transaction "711_S01_Fcogr_000_Login" ended with a "Fail" status (Duration: 16,9447).
Notify: Transaction "711_S01_Fcogr_000_Login" has 0 error message(s).
Ending iteration 4.
Waiting 2.000000 seconds for iteration pacing.
Starting iteration 5.
Starting action Action.
t=00149038ms: ** 1: Navigate to "https://www.abc.change.in.log.com" ** started [MsgId: MMSG-205180]
t=00150918ms: ** 1: Navigate to "https://www.abc.change.in.log.com" ** successfully completed [MsgId: MMSG-205180]
t=00150931ms: ** 2: Wait for File d'attente textbox ** started [MsgId: MMSG-205180]
t=00151191ms: ** 2: Wait for File d'attente textbox ** successfully completed [MsgId: MMSG-205180]
Error: Failed to end Transaction "711_S01_Fcogr_000_Login" (by name). Please check that you made a call to start transaction operation.
t=00151197ms: Internal problem -205177: In TransactionsAdapter::HandleMessage, calling EndTransaction failed [MsgId: MWAR-205177]
…
…
Ending action Action.
Ending iteration 5.
Waiting 2.000000 seconds for iteration pacing.
Starting iteration 6.
Starting action Action.
Notify: Transaction "711_S01_Fcogr_000_Login" started.
t=00183765ms: ** 1: Navigate to "https://www.abc.change.in.log.com" ** started [MsgId: MMSG-205180]
t=00184327ms: ** 1: Navigate to "https://www.abc.change.in.log.com" ** successfully completed [MsgId: MMSG-205180]
t=00184348ms: ** 2: Wait for File d'attente textbox ** started [MsgId: MMSG-205180]
t=00199009ms: ** 2: Wait for File d'attente textbox ** successfully completed [MsgId: MMSG-205180]
Notify: Transaction "711_S01_Fcogr_000_Login" ended with a "Pass" status (Duration: 15,2500 Think Time: 0,0160 Wasted Time: 0,6070).
...
... see attached mdrv.log
As you can see, the start transaction is triggered at the beginning for iteration #4:
Notify: Transaction "711_S01_Fcogr_000_Login" started.
But when Step 2 fails due to my intentional low timeout…
Wait for File d'attente textbox ** failed - target object was not found
…the start transaction is not called anymore in the next iteration #5. There is a missing line in the log between “Starting action Action” and “=00149038ms: ** 1: Navigate to…”. Then, LoadRunner fails to end the transaction:
Error: Failed to end Transaction "711_S01_Fcogr_000_Login" (by name). Please check that you made a call to start transaction operation.
t=00151197ms: Internal problem -205177: In TransactionsAdapter::HandleMessage, calling EndTransaction failed [MsgId: MWAR-205177]
Furthermore, since there was no object timeout in iteration #5 (I believe there is a logic there...!), the start transaction for the login is called again in iteration #6:
Notify: Transaction "711_S01_Fcogr_000_Login" started.
Since I get this problem all time, I put all my timeouts to 170 seconds. I know the server is a lot faster than this and I was able to ran the script with no error for around 150 times. On the other hand, I am very scared that in a real life situation a server might get slow then all of my metrics won’t be good because this is not only a VuGen problem! When I run my script with the Controller instead, the passed / failed transactions numbers don’t add up anymore. It is therefore difficult to provide our clients with a good report / result / analysis.
Attachment: mdrv.log
LoadRunner 12.02
TruClient for Internet Explorer 11
Windows 7
UAC / DEP off.
McAfee ScriptScan exceptions for some LR .exe. No more TCS error.
