Messages 27601 Through 27800

Message Code 27747

Out of memory

There is not enough memory available.

Troubleshooting

• Close other applications running on the same machine.
• Reduce the number of virtual users on the current machine.

Message Code 27752

Illegal 'parameter': 'parameter' -- use FAST, GRACEFUL or ABRUPT.

An invalid shutdown mode was used for web_set_sockets_option.

Troubleshooting

• Correct the second parameter in web_set_sockets_option("SHUTDOWN_MODE") with "FAST", "GRACEFUL" or "ABRUPT" as second parameter.

Message Code 27753

'option' takes an integer value.

An invalid integer value was used for web_set_sockets_option.

Troubleshooting

• Check web_set_sockets_option parameters.
• Refer to the Function Reference for valid parameters for the web_set_sockets_option.

Message Code 27755

Cannot parse IP address 'IP address value'.

An invalid Internet address was used in web_set_sockets_option (for example, a portion of an "a.b.c.d" address exceeds 255 characters)

Troubleshooting

• Check the IP address and correct it.

Message Code 27757

Unknown SSL version 'version name': use one of '2', '3', '2&3', 'TLS'.

An unsupported version was specified for the SSL_VERSION argument in web_set_sockets_option.

Troubleshooting

• Use one of the values '2', '3', '2&3', 'TLS'.
• Refer to the Function Reference for web_set_sockets_option syntax information.

Message Code 27759

Unknown option: 'option'.

An unsupported option was specified for web_set_sockets_option.

Troubleshooting

• Refer to the Function Reference for web_set_sockets_option syntax information.
• Add a web_set_sockets_option function with the "HELP" option. Specify an empty string for its value, in order to send information about the available options to the Replay log.

Message Code 27760

'user specified value'_ld is an illegal value for MaxConnections. Please choose a number between 'minimum value'_ld and 'maximum value'_ld.

Troubleshooting

• Choose a number between the minimum and maximum number of connections per host.

Message Code 27770

Full path length 'length'_ld for Key File exceeds 'maximum length'_ld.

The maximum size for the key file was exceeded.

Troubleshooting

• Move the key file to the script directory.
• Use a relative path.

Message Code 27771

Full path length 'length'_ld for Certificate File exceeds 'maximum length'_ld.

The maximum size for the certificate file was exceeded.

Troubleshooting

• Move the certificate file to the script directory.
• Use relative path.

Message Code 27772

Unsupported certificate file type 'certificate file type', only PEM and ASN1 currently supported.

A certificate file type other than PEM or ASN1 was specified in web_set_certificate_ex.

Troubleshooting

• Use PEM or ASN1 certificate format.
• Use the OpenSSL tool to convert pkcs12 certificates to PEM certificates.
• Use the WinInet replay mode. In Runtime Settings > Internet Protocol:Preferences node, check the WinInet replay instead of Sockets (Windows only) option in the Advanced section.

Message Code 27773

No certificate file type.

A certificate file type was not specified in web_set_certificate_ex.

Troubleshooting

• Specify a certificate file type by adding the "CertFormat=X" to web_set_certificate_ex. X can be "PEM" or "ANS1".
• Refer to the Function Reference for web_set_certificate_ex syntax information.

Message Code 27775

SSL server 'server name' requires client certificate. Use web_set_certificate_ex to specify a certificate.

A client certificate was not specified.

Troubleshooting

• Use web_set_certificate_ex to specify a certificate.

Message Code 27779

Timeout ('timeout value'_ld seconds) exceeded while attempting to establish connection to host 'host name'

A connect request failed because the host machine did not respond correctly within the time limit.

Troubleshooting

• If you used an IP address for the destination, verify that it is a valid IP address.
• If you used a hostname, check that it was resolved to the correct address.
• If you have a router configured, check that the router is running (check by pinging it, and then ping an address on the other side of it). Send a 'traceroute' command to the destination address to check that all the routers are functional.
• Check your subnet mask. If you don't have the proper subnet mask, your network system may treat a local address as a remote address (so it forwards addresses on the local subnet to the router, rather than broadcasting an ARP request locally), or visa versa.
• Increase the HTTP-request connect timeout in Runtime Settings > Internet Protocol > Preferences > Options.

Message Code 27782

Timeout ('timeout value'_ld seconds) exceeded while waiting to receive data for URL 'URL address'.

A timeout occurred while trying to reach the specified URL.

Troubleshooting

• Ping the remote host to which you were connected. If it does not respond, it may be off-line or there may be a network problem.
• Verify that the server application you are trying to access is running.
• Increase the HTTP-request receive timeout in Runtime Settings > Internet Protocol:Preferences > Options.

Message Code 27783

FTP server 'hostname/IP' returned error code 'returned code_ld' : 'server reply'

The server returned a permanent negative completion reply. This indicates that the command was not accepted and the requested action did not take place. The user-process is discouraged from repeating the exact request (in the same sequence).

Troubleshooting

• Check the server status code against FTP RFC.

Message Code 27786

Unable to find address of passive FTP port in server response: 'server response'.

A problem was encountered while parsing the server reply for passive ports.

Troubleshooting

• Check the server reply and try to solve the problem accordingly.

Message Code 27787

Missing passive socket 'server response'

Failed to enter passive mode. The server returned an FTP status other than 227.

Troubleshooting

• Check the server reply and try to solve the problem accordingly.

Message Code 27788

Failed to read data from server 'server name' .

An attempt to receive data has failed.

Troubleshooting

• Ping the remote host to which you were connected. If it does not respond, it may be offline or there may be a network problem along its path.
• Increase the socket buffer size using the TCP_BUFFER_SIZE option in web_set_sockets_option.

Message Code 27789

Server 'server name' has shut down the connection prematurely

The server shut down the connection unexpectedly, possibly in the middle of a response.

Troubleshooting

• Ping the remote host to which you were connected. If it does not respond, it may be offline or there may be a network problem. Try again later.
• Ping a local host to verify that your local network is still functioning.
• Ping your local router address.
• Ping a host on the same subnet as the remote host to which you were connected (if you know of one). This will verify that the destination network is functional.
• Send a "traceroute" command to the remote host. This will not reveal the problem unless you know the router addresses at the remote end, but it may help you determine if the problem is somewhere along the network path.

Message Code 27791

Failed to connect to server 'hostname';port_ld': 'reason'.

Unable to connect to the specified server and port.

Troubleshooting

• Try to address the reason provided for the connection failure.
• Try to access the application with a browser from the injector machine and from another machine (such as the recording machine).
• Check that you accurately specified the correct host name and port.
• Ping the host/port.
• Check if the server application you are trying to access is running.
• If you used a hostname, check if it was resolved to the correct address.
• Check if the server application is listening to the right port.

Message Code 27796

Could not resolve address of host 'hostname'

The remote address of the host could not be resolved. Possible reasons include: (i) The host name is misspelled or incorrect. (ii) The DNS (Domain Name System) server is down, incorrectly configured, or, for a new/changed host name, not up-to-date. (ii) There is a network problem in the connection to the DNS server.

Troubleshooting

• Try to access the application with a browser from the host machine and from another machine (e.g. the recording machine).
• Check that you accurately specified the correct host name and port.
• Ping the host/port.
• Check the DNS server configuration on the recording machine and the injector machine.
• If you are using a name server(s), check whether the server host(s) are up (e.g. try to ping the server(s)).
• Try to resolve another hostname that you know should work, to check that the name resolution server application is running.
• Replace the host name with the IP address.