Error Messages not getting Displayed in controller
218 views
Skip to first unread message
Rajeev R R S
Sep 30, 2010, 4:46:33 AM9/30/10
to LoadRunner
Hi,
I am trying to open my error messages while trying to run a test on
the controller, but it is not getting popped out or nither it is
getting displayed, i have tried to restart my Controller machine but
is also of no use.
Regards,
Rajeev R R S
I am trying to open my error messages while trying to run a test on
the controller, but it is not getting popped out or nither it is
getting displayed, i have tried to restart my Controller machine but
is also of no use.
Regards,
Rajeev R R S
prasenjit dutta
Nov 7, 2010, 11:23:47 AM11/7/10
to lr-loa...@googlegroups.com
check ur rts and changed it......
--
Prasenjit
--
You received this message because you are subscribed to the Google "LoadRunner" group.
To post to this group, send email to LR-Loa...@googlegroups.com
To unsubscribe from this group, send email to
LR-LoadRunne...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/LR-LoadRunner?hl=en
--
Prasenjit
chaitanya bhatt
Nov 7, 2010, 1:01:56 PM11/7/10
to lr-loa...@googlegroups.com
There are couple of possibilities here:
1. You have a situation with too many Vusers with each Vu throwing hundreds of error messages onto the output window. Solution: If you have used lr_error_message function in your script, then try to minimize the usage of it. Plus, you can also ensure that your script throws minimal errors by incorporating correlation and content checks.
2. You are using an older version of LR (9.0 or 8.1 or older) The older version had problems with dockable output window settings. If you have accidentally placed the window in a negative co-ordinate(outside the context of controller window) then your OUTPUT_FRAME_PLACE parameter in wlrun7.ini(drive:hp/loadrunner/config/) would be set with a negative value, which means your output window should technically fall outside the controller window and hence the problem.(Solution: Restart controller and reset your to output_frame parameter to a safe value. eg: OUTPUT_FRAME_PLACE=63,254,955,616,)
3. Your output window is docked and/or miniaturized or placed in a corner and you are overlooking it. Solution: Find it and expand it ;). I have seen many people goofing up because of this.
-Chaitanya M Bhatt
http://www.performancecompetence.com
1. You have a situation with too many Vusers with each Vu throwing hundreds of error messages onto the output window. Solution: If you have used lr_error_message function in your script, then try to minimize the usage of it. Plus, you can also ensure that your script throws minimal errors by incorporating correlation and content checks.
2. You are using an older version of LR (9.0 or 8.1 or older) The older version had problems with dockable output window settings. If you have accidentally placed the window in a negative co-ordinate(outside the context of controller window) then your OUTPUT_FRAME_PLACE parameter in wlrun7.ini(drive:hp/loadrunner/config/) would be set with a negative value, which means your output window should technically fall outside the controller window and hence the problem.(Solution: Restart controller and reset your to output_frame parameter to a safe value. eg: OUTPUT_FRAME_PLACE=63,254,955,616,)
3. Your output window is docked and/or miniaturized or placed in a corner and you are overlooking it. Solution: Find it and expand it ;). I have seen many people goofing up because of this.
-Chaitanya M Bhatt
http://www.performancecompetence.com
On Thu, Sep 30, 2010 at 2:16 PM, Rajeev R R S <raje...@gmail.com> wrote:
Reply all
Reply to author
Forward
0 new messages