During WWW playback, a required content string was not found or a prohibited content string was detected.
The WWW server had an error and returned an error page.
The script is not correctly parameterized.
The network may be overloaded with traffic and an incomplete page was returned.
Check the server to see if any error have occurred on it. Checking the condition of a web server varies from server to server, please refer to your server's documentation.
Either the content check or the data sent to the server with in Fill_In, Set CGI_PARAMETER, Set POST_DATA, or Set POST_FILE needs to be properly parameterized correctly.
Check with the network administrator to see if the network has been overloaded during the performance test.
Another cause is that you have created a Content Check that has specific data that works with the first transaction, but the second transaction contains different data that cannot be found in the content check as written.
Note that you can parameterize a content check with dynamic test data. An easy way to check to see if the content check is not coded correctly is to simply re-record with data from the second transaction, and check to see what content is present.