Explanation of error codes in LoadRunner

Sckoutofmemory 7 Low Memory

Sckinvalidpropertyvalue 380 Property value is not valid

Sckgetnotsupported 394 property is not readable

Sckgetnotsupported 383 property is read-only

Sckbadstate 40006 The requested transaction or the error protocol of the request itself or the wrong connection status

Sckinvalidarg 40014 The parameter format passed to the function is indeterminate, or is not within the specified range

Scksuccess 40017 Success

sckunsupported 40018 types of variables not supported

SCKINVALIDOP 40020 Invalid operation in the current state

Sckoutofrange 40021 parameter out of bounds

Sckwrongprotocol 40026 The requested transaction or the error protocol of the request itself

sckopcanceled 10004 Cancel Operation

Sckinvalidargument 10014 The requested address is a broadcast address, but the tag is not set

Sckwouldblock 10035 socket is not a block, and the specified operation will make it block

Sckinprogress 10036 Manufacturing block of Winsock operation in progress

Sckalreadycomplete 10037 Complete the operation. Operations without making blocks

Scknotsocket 10038 Descriptor is not a socket

Sckmsgtoobig 10040 data is too large to fit the requirements of the buffer, so it is truncated

Sckportnotsupported 10043 does not support the specified port

Sckaddressinuse 10048 address in use

Sckaddressnotavailable 10049来 non-available address from Local machine

scknetworksubsystemfailed 10050 Network Subsystem failed

Scknetworkunreachable 10051 is not currently reachable from the host network

Scknetreset 10052 Connection timed out when setting so_keepalive

Sckconnectaborted 10053 aborted due to timeout or other failure

Sckconnectionreset 10054 Reset connection via remote

Scknobufferspace 10055 No cache space available

sckalreadyconnected 10056 connected sockets

Scknotconnected 10057 Not connected sockets

Scksockedshutdown 10058 closed Socket

Scktimedout 10060 Socket Timeout

Sckconnectionrefused 10061 forcibly rejecting a connection

scknotinitialized 10093 Socket not initialized

Sckhostnotfound 11001 Authorization Answer: Host not found

Sckhostnotfoundtryagain 11002 Non-authoritative answer: Host not found, retry

Scknonrecoverableerror 11003 Unrecoverable Error

Scknodata 11004 Invalid name, no data record for the requested type

27791 Possible causes:

A, the application service dies.

(Small User: A problem on the program.) Issues with the database on the program)

B, application services are not dead

(Application service parameter setting problem)

Example: In many client connections WebLogic The application server is rejected, and there is no error on the server side, it is possible that the Acceptbacklog attribute value of the server element in the WebLogic is set too low. If you receive a connection refused message when you connect, the value should be increased by 25% each time

C, the connection of the database

(1, the performance parameters of the application service may be too small 2, the maximum number of database startup connections (related to hardware memory))

1.lr_think_time is not enabled by default. So we're doing the testing or enabling it in the replay. The specific operation is: vugen--"vuser---" runtime-settings-----"thinktime-----" Select Replay ThinkTime, other settings according to actual needs.

For a detailed introduction and usage of ThinkTime, see: http://www.testage.net/html/19/n-155019.html

2. Set the rendezvous time.

In the controller, SCENARIOC menu-----"Rendezvous into the current script to see the individual collection points, select one, and then click" Policy "to enter, you can set the collection point properties, rendezvous default is 30 seconds, Can be reset to its desired value.

3.Step Download Timeout (sec) settings.

This default is 120 seconds, but often we want to set a larger, specific setting method: vugen--"VUser---" runtime-settings----"Preferences------" option, will step download The timeout (SEC) default value of 120s is changed to the desired value, followed by a change of Http-reguest Connnect Timeout (sec) and Http-reguest receive timeout (sec) to the corresponding value.

4. Modify the number of native TCP connections.

Since the default number of TCP connections for personal PCs is only 15 (XP), we will encounter TCP connection limits when impersonating multiple virtual users, resulting in an error. Modified method: Run Patch.exe under Windows

Enter C, and then enter the TCP/IP connection number you want (typically 500~2000) enter confirm

Enter Y to confirm the return.

The countdown ends in 15 seconds.

Then run the next Patch.exe to see if the number of connections from the original 10 changed to their own values.

patch.exe:http://www.touchboy.cn/2007/05/% ...%e6%8e%a5%e6%95%b0/

6. Analysis and resolution of wsa_io_pending in LR

Message Code 27740

Overlapped Transmission of request to '%1 ' for URL ' url ' failed.

The transmission of data to the server failed. It could be a network, router, or server problem. The word Overlapped refers to the LoadRunner sends data in order to get a Web Page breakdown.

Troubleshooting

ADD The following statement to the beginning of the script to disable the breakdown of the ' first Buffer ' into server and Network Time:web_set_sockets_option ("Overlapped_send", "0");

Web_set_sockets_option ("Overlapped_send", "0");

7. About error-27791:error-27790:error-27740: the wrong solution:

The error is as follows:

ACTION.C (198): Error-27791:server "www.zcpx.cn" have shut down the connection prematurely

ACTION.C (198): error-27790:failed to read data from server "www.zcpx.cn": [10053] Software caused connection

Abort

ACTION.C (198): error-27740:overlapped Transmission of request to ' www.zcpx.cn ' for URL

"Http://www.zcpx.cn/userEntry.do" failed:wsa_io_pending

Workaround:

Add Web_set_sockets_option ("OVERLAPPED", "0") to the front of the script;

A workaround for error code 27796 in 8.LR

Problem:

A problem has been encountered in which multiple users using the HTTP protocol send requests to the server during a performance test. The duration is set and the error is: 27796, Failed to connect to server ' hostname ';p ort_ld ': ' Reason '. 10048.

Analysis

Because the load generator is performing so well, the packets are particularly fast and the server responds particularly quickly, causing the port of the load generator's machine to be fully occupied before the timeout is reached. When all is full, the above error will occur. You can see that many ports are open by executing the netstat–na command. Therefore, the time out of TCP is adjusted. That is, when the last port has not been used, there is already a port in front of it being released.

A successful solution:

In the load generator's registry hkey_local_machine\system\currentcontrolset\services\tcpip\parameters, there are two key values:

TcpTimedWaitDelay

MaxUserPort

1, here the TcpTimedWaitDelay default value should be 30s, so here, turn this value to 5s (adjust as needed).

2, you can also turn the MaxUserPort (if this value is not the maximum value).

Repeated verification, problem solving

Explanation of error codes in LoadRunner