These errors indicate that the form or link referenced in the script are not found on the current web page. Possible causes for this include: Session time outs - it is possible that because session ids are not being passed correctly the user is not being directed to the correct page. It may be necessary to parse the session ID"s. Due to an error occurring previously the user is not being directed to the correct page Dynamic links (i.e. the name of the link changes), or the link cannot be found on the page on replay. If the link name is dynamic then you could consider referencing the link as a number and specifying a NULL instead of the link name in the WebPageLink function call. Context has been lost for the previous WebUrl call and thus the link/form cannot be found (may be a result of using multiple transaction in the bdf and context not being carried) BACKGROUND ------------------------------ An example of when these errors occur could be described as follows: You have an application that contains dynamic links to user accounts. During recording you access several of these accounts and make changes, updating, expiring, etc. On replay of your script against the application some of the fictitious accounts are not there as they have been expired or updated. Therefore the subsequent pages are unavailable to the Virtual user upon replaying the script. As a result of this there are several HTTP errors in the XLG file. You should use SilkPerformer"s TrueLog Explorer"s "Customize Session Handling" wizard to find differences between your record and replay xlg"s and help detect if the error is related to session id"s that exist in the script but have expired. Please refer to the TrueLog Explorer"s User Guide for more information on how to use TrueLog Explorer to detect unique values that may need to be customized. The guide can be found in TrueLog Explorer under the Help dialog. If you only experience the error under load conditions then it may be that the server is not serving the correct content or if a load balancer is used it may be sending some requests to a server that is not delivering the correct content. Old KB# 19083
↧