From your statement, let me first assume that the script runs multiple iterations in Vugen without failing. If this is not the case, you must go back to Vugen and run your script through multiple iterations until it runs without error.

Once you have verified script execution in Vugen, try the following in the order listed.

* Run a single user in the Controller with full logging turned on and ''Snapshot on Error''. If the test run throws an error, look at the error message, the Vuser log, and any snapshots to determine the source of the error. Typically, an error here indicates something is not properly setup on the Load Generator.

* Run three users in the Controller with full logging turned on and ''Snapshot on Error''. If the test run throws an error, look at the error message, the Vuser log, and any snapshots to determine the source of the error. Typically, an error here will be caused by multiple users using the same credentials to log in to the application. Some applications will not allow this. Also, verify all correlations in the script are successful and that they are saving the correct expected value. Take a hard look at any dates that might be out of range during the time period you are running the test.

* Once you are successful with the above two test, you should be ready to proceed with your performance tests. Before you begin, turn on logging on error only. I recommend that for the next test, that you ramp up slowly while monitoring your Load Generators and the application under test. During this slow ramp-up, you should be able to determine the root cause of any failures.