Load Runner Tips- Load runner errors, vugrn errors, controller errors, commen errors in LR, Performance testing errors, load testing errors, stress testing errors, soak testing errors, endurances testing errors.



Load Runner Errors


Error: "License cannot be save in your installation directory. (Error code = -4) It will be used only for this session."
Resolution:
  • Make sure that you have admin privilege to the Controller machine. If you are accessing the Controller machine via the network, make sure that you have read/write access to the network drive.
Error: "Memory violation error "in Load Runner
Resolution:
  • This error is caused because of below issue:
  • C pointer errors,C programming invalid declarations.
  • Memory full.
  • Not enough Memory for what you need to place in a defined space.
  • Memory not yet allocated before attempting to use it.
  • Memory allocated but not de- allocated.
  • Trying to copy a non pointer version of a data type to a pointer defined version of a data type, such as copying a character array to a pointer to a character array.
  • Generally unless you have a hardware issue this is a developer error.
Error: “HTTP Satuts-Code=500 (Internal Server Error)” in Load Runner
Resolution:
  • Check the request body and verify if you are passing correct values in request body or URL.
  • Check where application is reachable by opening application in web browser or ping from Command prompt.
  • Check if request is not getting time out.
  • Check in response the detail error message like ‘Out of Memory’, ‘Request timeout’ or server is not able to process your request.
  • Check if you can reproduce same error in application manually, if you can than there is problem in application, else check your request you are passing incorrect data in request body.
HTTP Response Messages
HTTP servers respond to client requests in the form of a response message. This message contains a status line, response headers, and meta-information about the resource (information about the resource itself, not about the information that is contained in the resource). Each HTTP status line contains the HTTP version number, a status code, and a description. For example, "HTTP/1.0 200 OK" is a typical status line returned in a response message from an HTTP server. The following table contains status codes and their meanings.

HTTP Status Codes Status Code Meaning
  • 200 OK
  • 201 Created
  • 202 Accepted
  • 203 Non-Authoritative Information
  • 204 No Content
  • 205 Reset Content
  • 206 Partial Content
  • 251 Fin (i-mail capture)
  • 252 Rec (i-mail capture)
  • 255 Empty (i-mail capture)
  • 300 Multiple Choices
  • 301Moved Permanently
  • 302 Moved Temporarily
  • 303 See Other
  • 304 Not Modified
  • 305 Use Proxy
  • 307 Temporary Redirect
  • 400 Bad Request
  • 401 Unauthorized
  • 402 Payment Required
  • 403 Forbidden
  • 404 Not Found
  • 405 Method Not Allowed
  • 406 Not Acceptable
  • 407 Proxy Authentication Required
  • 408 Request Timeout
  • 409 Conflict
  • 410 Gone
  • 411 Length Required
  • 412 Precondition Failed
  • 413 Request Entity Too Large
  • 414 Request URL Too Large
  • 415 Unsupported Media Type
  • 416 Requested Range Not Satisfiable
  • 417 Expectation Failed
  • 451 ID Error (i-mail capture)
  • 500 Internal Server Error
  • 501 Not Implemented
  • 502 Bad Gateway
  • 503 Service Unavailable
  • 504 Gateway Timeout
  • 505 HTTP Version Not Supported
  • 552 POST Error (i-mail capture)
  • 553 GET Error (i-mail capture)
  • 554 Unordered (i-mail capture)
  • 561 UE POST Error (i-mail capture)