Error Messages

Last modified on October 8, 2020.

Below is a list of error messages you may encounter when working with LoadNinja.

The error occurs if the expected URL was not opened during the script run.

Possible reasons:

  • The server was not available.

  • There is a bug in the tested application.

  • A wrong URL was specified.

  • You have an internal application, and you tried to play back your script while your proxy was disconnected.

  • Poor server performance. Consider using a high-capacity server.

This error occurs if the browser used in your test has not started.

Possible reason:

There is a problem on the LoadNinja side. If you get this error, please contact our Support team.

This error occurs if the communication with the browser used in your test has timed out.

Possible reasons:

  • There is a syntax error in a custom JavaScript validation and the next page could not be opened.

  • Custom validation took more than 30 seconds to complete. This could happen if the validation didn’t pass due to a heavy load on the server. In this case, you need to check the application code or use a high-capacity server.

  • There are problems with the network connection.

  • The tested server is not responding.

This error occurs if the script run time has exceeded the maximum playback time (3780 seconds). If your script takes more than this time, it is aborted with this error.

Possible reasons:

  • A large value in the Debug Time field of scenario settings. LoadNinja stops the script run each time an error occurs so that you can debug the issue. If you set a large value for the waiting period, your script may run for a long time. Set a lower value to avoid the error.

  • Your script is very large. Remove some steps from it or create a smaller script.

This error occurs if the specified validation has failed due to an invalid JavaScript function. Please correct the expression.

This error occurs if the specified JavaScript validation has failed due to a syntax error in the function, or because the validation took more than 30 seconds to complete due to a heavy load on the server or connection issues.

This error occurs if the SLA validation has failed because the step ran longer than the time specified in the validation settings. This can happen due to connection issues or a heavy load on the server.

This error occurs if the Text validation has failed because the specified text was not found on the page.

This error occurs if the Text validation has failed because the page contained text that was not supposed to be there.

This error occurs if the specified URL cannot be accessed.

Possible reasons:

  • The URL is misprinted.

  • The server is unavailable because it is either not responding or there are connection issues.

  • You have an internal application and you tried to play back your script while your proxy was disconnected.

The error occurs if LoadNinja failed to access the Chrome browser during the default timeout period.

This error indicates that the connection to a remote browser is broken. Try selecting a higher tier level for your scenario in the [Advanced] Machine configuration section of the scenario settings page.

This error indicates an issue with simulating user actions in a browser used for the test. To work around it, run your scenario again and try selecting a higher tier level for your scenario in the [Advanced] Machine configuration section of the scenario settings page.

See Also

Debug Virtual Users
Test Results

Highlight search results