Messages 26581 Through 26660

Note: If an error code within the above range does not appear in this list, it is considered an Internal Error, for which no specific user troubleshooting guidelines are available.

Message Code 26581

Error after reading 'bytes' bytes from submitted/uploaded file 'file path'

There was a problem reading a file to be submitted (uploaded). The file is specified by the "BodyFilePath=" argument of the web_custom_request function.

Troubleshooting

  • Try running the script again.
  • Check that the file is not corrupted.
  • Check that the file is accessible. If it is a network file, check your network connections.

Message Code 26582

Could not open submitted/uploaded file 'file path': errno='operating system error number', strerror='error description'

There was a problem opening a file to be submitted (uploaded). The file is specified by the "BodyFilePath=" argument of the web_custom_request function. The most likely cause is "File not found". Possible reasons: (i) The file name is misspelled. (ii) The files to be submitted aren't located directly under the Vuser directory. This may cause the script to fail when copying or moving to another machine or operating system (e.g., a "\" for a directory name under Windows should be replaced with a "/" for Unix). (iii) The file was deleted. (iv) The drive letter (e.g., "G:") may refer to different net locations on different machines. (v) Permissions problem.

Troubleshooting

  • Try to resolve the problem specified in the "error description". For example, if the file is not found, check that the file name is correct, the file has been copied with the script, and that the file exists on the recording and replay machine.
  • Copy the file to be submitted to the directory directly beneath the Vuser directory (not a subdirectory). Specify a simple name for the file (i.e., without drive/host/directory).
  • Check your file permissions. In a Windows operating system, an "errno" system variable of 13 means "Permission denied".

Message Code 26583

Could not obtain information about submitted/uploaded file 'file path': 'system function name' rc='return code', errno='operating system error number', strerror='error description'

There was a problem obtaining information about a file to be submitted (uploaded). The file is specified by the "BodyFilePath=" argument of the web_custom_request function. The most likely cause is "File not found". Possible reasons: (i) The file name is misspelled. (ii) The files to be submitted aren't located directly under the Vuser directory. This may cause the script to fail when copying or moving to another machine or operating system (e.g., a "\" for a directory name under Windows should be replaced with a "/" for Unix). (iii) The file was deleted. (iv) The drive letter (e.g., "G:") may refer to different net locations on different machines. (v) Permissions problem.

Troubleshooting

  • Try to resolve the problem specified in the "error description". For example, if the file is not found, check that the file name is correct, the file has been copied with the script, and that the file exists on the recording and replay machine.
  • Copy the file to be submitted to the directory directly beneath the Vuser directory (not a subdirectory). Specify a simple name for the file (i.e., without drive/host/directory).
  • Check your file permissions. In a Windows operating system, an "errno" system variable of 13 means "Permission denied".

Message Code 26590

Warning: The web_remove/revert_auto_header for 'header' had no effect

The web_remove_auto_header/web_revert_auto_header failed to stop Vusers from adding the specified header.

Possible causes:

  • There was no preceding web_add_auto_header.
  • A previous web_remove_auto_header or web_revert_auto_header already had the effect requested by the current function call.
  • For implicitly generated headers, there was no previous web_add_auto_header, web_remove_auto_header or web_revert_auto_header that changed the implicit generation status.

Troubleshooting

  • Check whether this is the header you intended to remove.
  • Look for a preceding web_add_auto_header, web_remove_auto_header or web_revert_auto_header function specifying the same header type. You can safely delete the current call.

Message Code 26591

'header' header not allowed in web_add_auto_header

The header cannot be specified using the web_add_auto_header function.

Troubleshooting

  • Use another function instead. If the header that produces this message is "Cookie", use web_add_cookie.

Message Code 26592

A header of the same name has been added already. This header is added anyway.

A header of the same type (possibly, with a different value) has been added before web_add_header for the same "action" function. The header is added without superseding the previous specification. For most header types, the server is likely to use the first specification and ignore the others.

Troubleshooting

  • Check that you intended for the same header type to appear more than once in the same request. If you did not, delete the unnecessary web_add_header.

Message Code 26593

The header being added may cause unpredictable results when applied to all ensuing URLs. It is added anyway

The header specified in web_add_header usually applies to a specific request. If the same header is applied to other requests, the results may be unpredictable. For example, when a request having a non-empty body is redirected to another URL, the redirection is always performed without specifying a body. Applying the same Content-Length header in the redirected request will cause the server to wait indefinitely for the body of the redirected request to arrive. Thus, the specified header will be applied only to the first ("primary") request and not to any derived requests.

Similar considerations apply to the following headers: "Authorization", "Content-Encoding", "Content-Length", "Content-Location", "Content-MD5", "Content-Range", "Content-Type", "Host", "If-Match", "If-Modified-Since", "If-None-Match", "If-Range", "If-Unmodified-Since", "Proxy-Authorization", "Referer", "Transfer-Encoding".

Troubleshooting

  • Make sure that you want to add this type of header. If you want the specified header to apply to all requests, use web_add_auto_header (preferably with a corresponding web_revert_auto_header or web_remove_auto_header afterwards to disable adding this "risky" header).

Message Code 26594

The header being added may cause unpredictable results if applied to ALL the URLs generated on behalf of the next script function. It will apply to the primary URL only.

The header specified in web_add_header usually applies to a specific request. If the same header is applied to other requests, the results may be unpredictable. For example, when a request having a non-empty body is redirected to another URL, the redirection is always performed without specifying a body. Applying the same Content-Length header in the redirected request will cause the server to wait indefinitely for the body of the redirected request to arrive. Thus, the specified header will be applied only to the first ("primary") request and not to any derived requests.

Similar considerations apply to the following headers: "Authorization", "Content-Encoding", "Content-Length", "Content-Location", "Content-MD5", "Content-Range", "Content-Type", "Host", "If-Match", "If?Modified-Since", "If-None-Match", "If-Range", "If-Unmodified-Since", "Proxy-Authorization", "Referer", "Transfer-Encoding".

Troubleshooting

  • Check that you want to add this type of header. In the event that you want the specified header to apply to all requests, use web_add_auto_header (preferably with a corresponding web_revert_auto_header or web_remove_auto_header afterwards to disable adding this "risky" header).

Message Code 26595

An unrecognized header is being added

A web_add_header or web_add_auto_header function specifies an unrecognized header (i.e., a header that is not defined in the HTTP/1.1 specs). Possible causes: (i) Spelling error. (ii) The header is an application-defined header.

Troubleshooting

  • If this is a spelling error, correct it.
  • If this is an application-defined header, ignore this message.
  • If this is a valid HTTP-defined header unrecognized by the Web Replay, contact customer support and ignore this message.

Message Code 26596

Added header value contains a newline character (\n)

The newline character ('\n') cannot be used in a header. Note that the web_add_header and web_add_auto_header functions only support adding one header at a time.

Troubleshooting

  • Remove the offending newline character ('\n') from the script.
  • To add additional headers, use a separate web_add_header or web_add_auto_header call for each header.

Message Code 26597

Added header value is NULL, empty or contains white spaces only. It is added anyway

A header was added with a name but no value. Headers should contain at least one (non-space) value.

Troubleshooting

  • Add a non-space value to the header.
  • Generate headers using the web_remove_auto_header or web_revert_auto_header functions.
  • Remove the web_add_header or web_add_auto_header call.

Message Code 26598

Not enough memory ('requested memory size in bytes') for 'object'

Insufficient memory for the specified object.

Troubleshooting

Back to top