08-07-2013 12:34 AM
I've created a script based on the HTML protocol with VUGEN 11.52. When recording, everything seems to be fine. When doing the relpay I get the information that the "Replay status passed". However, in the replay log I see a message "Resource Page Timeoout is a warning: No [Msgid: MMSG-27029].
In the Run-Time-Seetings the timeouts is set to 240.
Further down I also see the following:
Action.c(14): Warning -26376: Requested parameter "sessionID" found in 2 different pages/frames. Use web_reg_save_param with more restrictive LB/RB/RelFrameId [MsgId: MWAR-26376]
Action.c(14): Warning -26375: Parameter "sessionID" saved from "RelFrameId=1" (URL="http://nomac/cgi-bin/Maconomy/MaconomyPortal
Note: The following parameter is in the script, web_reg_save_param("session", "LB=logon.msc?sessionid=", "RB=\">", LAST);
When checking the test results I see the following etc.:
- Disable your popupblocker to make the Maconomy portal function correctly.
Note: The popupblocker is not enabled in IE 8.
- The session has timed out. You must log on again.
Note: Not possible to reconnect.
In the sript one of the parameters is:
Does anyone have any idea how to solve this?
Thanks in advance for any help.
08-07-2013 07:24 AM
The message "The session has timed out. You must log on again." could be related to the correlation which need to be modified. Please try with this correlation first.
Regarding the pop up blocker you can try to disable the pop blocker during record and reply the script again and check if "Disable your popup blocker to make the portal function correctly" will disappear during replay.
If you haven’t tried it yet, come and join us in our entitled forums at Support Customer Forums
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution and give Kudos to the author for their assistance.
08-07-2013 11:39 AM
Do you know what reousrce is failing to download, sometimes if the script does not error out you can ignore some resoruces but you can check other replays to see if you get the same warning consistently it may not be an issue at all.
If you are customer you can try posting on our internal forums for more personalized support.
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.