Performance Center Practitioners Forum
cancel

"HttpSendRequest" failed, Windows error code=12002 - Perf Center Error

SOLVED
Go to solution
Highlighted
krunal85
Trusted Contributor.

"HttpSendRequest" failed, Windows error code=12002 - Perf Center Error

Hi All,
I am doing perf testing for one of our internal web application. I can run the created script successfully in VuGen (9.52) but performance center (9.5) throws following errors:
 
Action.c(1288): Error -27492: "HttpSendRequest" failed, Windows error code=12002 and retry limit (0) exceeded for URL="https://xxx/yyy/zzz/aaa/bbb/cccc/portfolio_performance.do?", Snapshot Info
Action.c(52): Error -27492: "HttpSendRequest" failed, Windows error code=12002 and retry limit (0) exceeded for URL="https:/xxx/yyyy/zzzz/homePage.do", Snapshot Info [MSH 0 1]
There are so many errors like above which point towards diff. URLs. I am trying to reach to 30 vusers but i am seeing errors occurring sometime at 10 users or 15 or sometime 21 users. I am using 1 LG.
FYI, i am using WinInet replay engine as default win-socket throws 401 error (even with web_set_user function) because of some secured JAVA applets. I can't even turn off window's integrated Auth, as that gives exception errors.  
If anybody has faced this error, please guide me. 
Thanks,
Krunal 
13 REPLIES
Suerte13cr
Acclaimed Contributor.

Re: "HttpSendRequest" failed, Windows error code=12002 - Perf Center Error

Vugen runs script as a process, are you running your vusers as process or thread?

 

Regards,

Mario

HP LR/PC Support

If you are customer you can try posting on our internal forums for more personalized support.

LoadRunner:
http://h30499.www3.hp.com/t5/LoadRunner-Support-Customer/bd-p/loadrunner-support-customer-forum

Performance Center:
http://h30499.www3.hp.com/t5/Performance-Center-Support/bd-p/performance-center-support-customer

How to:
http://www.youtube.com/watch?v=4ChlysWupWM

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
krunal85
Trusted Contributor.

Re: "HttpSendRequest" failed, Windows error code=12002 - Perf Center Error

I selected to run the vuser as a process in RTS.

 

Thanks,

Krunal

Suerte13cr
Acclaimed Contributor.

Re: "HttpSendRequest" failed, Windows error code=12002 - Perf Center Error

Did that fix the issue? If so please mark this thread as solved.

HP LR/PC Support

If you are customer you can try posting on our internal forums for more personalized support.

LoadRunner:
http://h30499.www3.hp.com/t5/LoadRunner-Support-Customer/bd-p/loadrunner-support-customer-forum

Performance Center:
http://h30499.www3.hp.com/t5/Performance-Center-Support/bd-p/performance-center-support-customer

How to:
http://www.youtube.com/watch?v=4ChlysWupWM

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
krunal85
Trusted Contributor.

Re: "HttpSendRequest" failed, Windows error code=12002 - Perf Center Error

Thabjs for the suggestion but I already did that before you suggested. Unfortunately even with that it gives me same error.

After doing some research on this  error i came to know that this error has to do something with the  WinInet replay. Some Requests are not going to server and they get time out (windows code = 12002) before they reach to server.

 

Thanks,

Krunal

krunal85
Trusted Contributor.

Re: "HttpSendRequest" failed, Windows error code=12002 - Perf Center Error

If aybody has any kind of suggestions, they are welcome. I want to know the root cause of this error.

 

Thanks,

Krunal 

Suerte13cr
Acclaimed Contributor.

Re: "HttpSendRequest" failed, Windows error code=12002 - Perf Center Error

Hi Krunal,

 

As you mentioned this is particular to working with WinInet, and the error itself comes from WinInet API not specifically Vugen.

 

You can see in part of the replay you posted the errors come from resources during the replay where they timed out.

 

If you are forced to use WinInet then this will occur, but if you can use Sockets you may want to try that option instead or a Click and Script protocol.

 

Regards,

Mario

HP LR/PC Support

If you are customer you can try posting on our internal forums for more personalized support.

LoadRunner:
http://h30499.www3.hp.com/t5/LoadRunner-Support-Customer/bd-p/loadrunner-support-customer-forum

Performance Center:
http://h30499.www3.hp.com/t5/Performance-Center-Support/bd-p/performance-center-support-customer

How to:
http://www.youtube.com/watch?v=4ChlysWupWM

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
krunal85
Trusted Contributor.
Solution

Re: "HttpSendRequest" failed, Windows error code=12002 - Perf Center Error

Thanks for the Reply.

 

Finally i came to conclusion that HttpSendRequest time out only occurres when any transaction takes more than 30 sec to connect to server. This default 30 sec time is because of the use of WinInet Replay engine. Thus this error pops up when you are running script with winInet replay and transactions are taking more than 30 sec. Only thing to get rid of this error is to  fine tune the whole system and check the backend and servers to see any request que has formed up. 

 

Another option is to use web_set_max_retries ("X") to increase the limit of 30 sec. I wouldn't recommend that.

 

Thanks,

Krunal

Sivaprakash_C
Regular Contributor.

Re: "HttpSendRequest" failed, Windows error code=12002 - Perf Center Error

Me too faced the same issue, what Krunal suggesting is the reason. 

I am able to resolve the issue using the below steps,

1. Disable "Use WinInet replay instead of Sockets (Windows only)" option from RTS - Internet Protocol - Preferences - Advanced

2. Set the SSL version using the below function in your script

   web_set_sockets_option("SSL_VERSION", "TLS1.2");

amitkr
Frequent Contributor.

Re: "HttpSendRequest" failed, Windows error code=12002 - Perf Center Error

Hi,

I am also getting the same error - "HttpSendRequest" failed, Windows error code=12002 while replaying in Winlet mode

  • Since Socket option is not recprding , need to use Winlet
  • finetunning the sever to have response time < 30 sec is not  possible as of now
  • web_set_max_retrioes("X"), also may not serve the purpose as just retries. If server response remains > 30 sec , it would keep on failing.

Could anyone suggest how to configure the script / winlet mode to wait for more than 30 sec pls ?

amitkr
Frequent Contributor.

Re: "HttpSendRequest" failed, Windows error code=12002 - Perf Center Error

Hi Sivapctech,

could you pls elaborate on this..

I have recorded the script using winlet mode so can i still disable the "Use WinInet replay instead of Sockets (Windows only)" option and replay the script using web_set_sockets_option("SSL_VERSION", "TLS1.2"); ?

Thanks in anticipation!!

Shark1
New Member.

Re: "HttpSendRequest" failed, Windows error code=12002 - Perf Center Error

Thanks Siva .. It works...

dNAfication
Respected Contributor.

Re: "HttpSendRequest" failed, Windows error code=12002 - Perf Center Error

Guys, I have same problem as @amitkr

  • need to replay in winInet (socket not an option)
  • finetunning the sever to have response time < 30 sec is not  possible as of now
  • web_set_max_retrioes("X"), also may not serve the purpose as just retries. If server response remains > 30 sec , it would keep on failing.

Could anyone suggest how to configure the winlet timout to more than 30 sec pls ?

DebrajAdhikari
Frequent Visitor.

Re: "HttpSendRequest" failed, Windows error code=12002 - Perf Center Error

I was also getting the same error "HttpSendRequest" failed, Windows error code=12002 while running script in WinInet Replay Engine replay mode. Using web_set_max_retries(); did not help.

I was using WinInet mode because i was getting HTTP 401 Authentication error while replaying the script.

To resolve the issue, i reverted back to Socket mode and made the following changes in the run time settings:

1. Proxy -> Authentication -> Provide username and password for proxy (No Proxy setting was selected)

2. Preferences -> Advanced -> Uncheck Wininet replay instead of sockets

3. Preferences -> Authentication -> Check Use the native Windows NTLM implementation

4. Preferences -> Authentication -> Check Enable Integrated Authentication