Monday 2 December 2013

error message as "Action.c(400): Error -27979: Requested form not found [MsgId: MERR-27979]" in load runner

While executing some scripts in replay it shows that the script is logged out and its shows "Form not available" error message as it again shows the login page.Do u know why? chances are that the problem is not at the web_submit_form call. Again, Based on the error message it looks like the problem is taking place before the web_submit_form call. As some people suggested, take a look at the logs from start to finish. Make sure the script is working find all the way up to this "web_submit_form" call. Very important, double check corralation and Test data. Talk to SMEs about this, you might be missing or doing something that is not part of the process. Try the process manually with the test data and see if that works just fine.Correlate exact values it will works fine,Causes are

Scripting Problem :
You can identify this by running your Vuser with the extended log turned on in VuGen for at least two iterations. Then, review the log file and try to identify the cause of error. Very often this is caused by dynamic values in the script.

 HTML Recording Mode Problem:
If your site contains JavaScript, in the source, check if there are any nested pairs of (e.g., from a document.write statement) within the for the JavaScript. If so, switch to HTTP mode recording. 

Server Problem:
 If your server could return different pages for a request, make sure that you include the logic in the script. If you can detect the behavior as to why your server would send a different page, it is best to get the help of your administrator for further diagnosis. Monitor the servers on the back end (including the Web, database, and application servers) for any unusual behavior. A typical error returned to a Web client might be a 500 Internal Server Error. The specific reason for this is not obvious based on the message, it simply indicates that somethingwent wrong when trying to process the request by the client. Rerun the test as necessary to pinpoint the issue.