Messages 27401 Through 27600

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 27480

Failed to modify "MaxConnectionsPerServer" and/or "MaxConnectionsPer1_0Server" (under "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings")

When using the WinInet replay for load testing, registry settings must be adapted for multiple concurrent connections. The function that can modify the settings for the current run (not permanently) failed.

Troubleshooting

  • Open HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings in the Registry Editor, and change the Value data for "MaxConnectionsPerServer" and "MaxConnectionsPer1_0Server" to "30000".

Message Code 27485

Moreover, the "MaxConnectionsPerServer" and "MaxConnectionsPer1_0Server" WinInet registry settings are inadequate for load testing with the WinInet replay

When using the WinInet replay for load testing, registry settings must be adapted for multiple concurrent connections. The function that can modify the settings for the current run (not permanently) failed.

Troubleshooting

  • Open HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings in the Registry Editor, and change the Value data for "MaxConnectionsPerServer" and "MaxConnectionsPer1_0Server" to "30000".

    Note that doing this causes Internet Explorer to run faster than when its defaults are used (as it can open more concurrent connections). If you want to compare the browser with the WinInet replay, delete the above registry keys (using regedit/regedt32).

Note: This error message is always preceded by Message Code 27486.

Message Code 27486

WinInet connection limits could not be set (InternetSetOption for 'option' failed, Windows error code 'error code'). The Internet Explorer version may be lower than 5.0

When using the WinInet replay for load testing, registry settings must be adapted for multiple concurrent connections. The function that can modify the settings for the current run (not permanently) failed. This is likely to occur if the version of Internet Explorer installed is earlier than 5.0.

Troubleshooting

  • Upgrade the Internet Explorer to version 5.0 or later (this upgrades WinInet).

Note: This error message is always followed by Message Code 27485.

Message Code 27488

web_set_sockets_option has no effect on WinInet replay

The web_set_sockets_option script function is intended for use by the Sockets replay only, and has no effect when using the WinInet replay.

Troubleshooting

  • You can ignore this message if the usage of the web_set_sockets_option is not significant for you (e.g., TRACE_SSL_IO).
  • Switch to the Sockets replay: In VuGen or the Controller, select Run-Time Settings > Internet Protocol: Preferences, and clear the WinInet replay instead of Sockets (Windows only) check box.

Message Code 27489

InternetReadFile failed. Windows error code='error code'. 'URL'

The WinInet function used for reading the response from the server failed.

Troubleshooting

  • To identify the problem, refer to the Windows Error Code tables for WinINet, Win32, and WinSocket, and search for the value specified in the error code.

Message Code 27490

Certificate index missing or invalid

An authentication certificate is required by the server application, but a valid certificate was not specified. Possible reasons include: (i) A web_set_certificate, or web_set_certificate_ex with CertIndex argument was not specified. (ii) The index specifies the wrong certificate for the application. This can occur when running the Vuser script on a machine other than the one on which it was recorded, and the other machine has different certificates, or the same certificates in a different order.

Troubleshooting

  • If there is no preceding web_set_certificate, or web_set_certificate_ex with CertIndex argument, add such a statement to the script. For more information, refer to the Function Reference.
  • Check that the certificate at the specified index on the current machine is the same certificate as on the machine where the script runs successfully. If it is not, change the order of the certificates using import/export.

Message Code 27492

'WinInet function' failed, Windows error code='error code' 'retry details' and retry limit ('retry limit') exceeded for 'error details'

The specified WinInet function failed, and the function was issued as a retry. The retry limit was exceeded, and no more retries were attempted. The retry reasons may be identified, or they may be empty. The error details provide information such as the host (server) name and port number, or the URL.

Troubleshooting

  • To identify the problem, refer to the Microsoft Windows Error Code tables, and search for the value specified in the error code.

Message Code 27493

Client authentication certificate needed but is not available. Use web_set_certificate[_ex] to specify a certificate. 'error details'

An authentication certificate is required by the server application, but a valid certificate was not specified. The error details provide information such as the host (server) name and port number, or the URL. Possible reasons include: (i) A web_set_certificate, or web_set_certificate_ex with CertIndex argument was not specified. (ii) The index specifies the wrong certificate for the application. This can occur when running the Vuser script on a machine other than the one on which it was recorded, and the other machine has different certificates, or the same certificates in a different order.

Troubleshooting

  • If there is no preceding web_set_certificate, or web_set_certificate_ex with CertIndex argument, add such a statement to the script (see the Function Reference).
  • Check that the certificate at the specified index on the current machine is the same certificate as on the machine where the script runs successfully. If it is not, change the order of the certificates using import/export.

Message Code 27494

'WinInet function' failed (Windows error code='error code 1') following an HttpSendRequest failure (Windows error code='error code 2') for 'error details'

The specified WinInet function and a retry attempt failed. The error details provide information such as the host (server) name and port number, or the URL.

Troubleshooting

  • To identify the problem, refer to the Windows Error Code tables for WinInet, Win32, or WinSocket, and search for the value specified in the error code.

Message Code 27495

InternetConnect failed. Windows error code 'error code'. 'error details'

The WinInet function used for establishing a connection to the server failed. The error details provide information such as the host (server) name and port number.

Troubleshooting

  • To identify the problem, refer to the Windows Error Code tables for WinInet, Win32, or WinSocket, and search for the value specified in the error code.

Message Code 27496

Internal Error (call customer services): 'internal error code'

Troubleshooting

  • Contact customer support and provide them with an explanation of the problem, and the error message returned.

Message Code 27497

Timed out while closing handle on behalf of 'URL'

Processing the URL exceeded the maximum time defined for it in the runtime settings ("HTTP-request connect timeout" or "HTTP-request receive timeout"). Possible reasons include: (i) The server or server application is too busy to respond within a reasonable time. (ii) There is a network or DNS problem. (iii) Problem with the client machine's operating system.

Note: The WinInet Replay does not support "Step download timeout".

Troubleshooting

  • Check that your network connection is still active (ping the server).
  • Check that the URL or the application being tested is accessible from a browser on the same machine.
  • Rerun the scenario, and concurrently try to access the URL or the application being tested from a browser on another machine. If the response time is excessive, the server or the server application probably cannot sustain such loads. Analyze the server or the server application for bottlenecks and optimize to improve performance.
  • Run the scenario on the Controller, and use the Analysis results to locate whether the bottlenecks are on the server, DNS, or the network. Optimize the system to improve performance.
  • Increase the runtime timeout settings: In VuGen or the Controller, select Run-Time Settings > Internet Protocol: Preferences, click the Options button, and increase the "HTTP-request connect timeout" or "HTTP-request receive" timeout values.

Message Code 27498

Timed out while processing 'URL'

Processing the URL exceeded the maximum time defined for it in the runtime settings ("HTTP-request connect timeout" or "HTTP-request receive timeout"). Possible reasons include: (i) The server or server application is too busy to respond within a reasonable time. (ii) There is a network or DNS problem. (iii) Problem with the client machine's operating system.
Note: The WinInet Replay does not support "Step download timeout".

Troubleshooting

  • Check the network connection. Ping the server.
  • Check that the URL or the application being tested is accessible from a browser on the same machine.
  • Rerun the scenario, and concurrently try to access the URL or the application being tested from a browser on another machine. If the response time is excessive, the server or the server application probably cannot sustain such loads. Analyze the server or the server application for bottlenecks and optimize to improve performance.
  • Run the scenario on the Controller, and use the results of the Analysis to locate where the bottlenecks are, in the server, DNS and/or network. Optimize the system to improve performance.
  • Increase the runtime timeout settings: In VuGen or the Controller, select Run-Time Settings > Internet Protocol: Preferences, click the Options button, and increase the "HTTP-request connect timeout" or "HTTP-request receive" timeout values.

Message Code 27499

Scheme in URL='URL' is not supported by the WinInet replay mechanism. Only "http:" and "https:" are supported

The WinInet Replay does not support the specified scheme (portion of a URL before "://"). For example, URLs starting with "ftp://".

Troubleshooting

  • Use the Sockets Replay: In VuGen or the Controller, select Run-Time Settings > Internet Protocol: Preferences, and clear the WinInet replay instead of Sockets (Windows only) check box.
  • If the URL is explicitly specified in the script (e.g., in web_url), comment out or remove the function referring to it.