Testing .NET app using LR 11 getting binary data - Need help
Our application is Client/Server win application developed using Visual Studio 2010 .NET 4.0/WCF Framework . As advised by Protocol advisor I used HTTP/HTML protocol for recording a simple Business Scenario. My recorded Script shows lot of body binary data. Generated some of the session ids/uuids parsed in the script and left the binar data as it is.During the replay I encountered the below error: Error: Error -26612: HTTP Status-Code=500(Internal Server Error).I have worked with LR Tech support team for quite some and Tech team confirmed LR11 wont be able to support .NET 4.0.
Now we have access to LR 12 Beta version I am seeing the same behaviour like the one I mentioned above. In the protocol selection page I tried to record using .NET 4.0 I am getting LoadRunner crash message.
Any suggestions or information is appreciated. Thanks.
Regarding .NET protocol - in any case, VuGen should not crash.
We had a few issues in the beta version of such crashes which were later on solved.
I suggest using the official LR11.50 that was recently released; if the problem still occurs, please escalate to R&D and we will address this ASAP.
.NET protocol owner
You may want to try a different protocol since it captures binary Vugen cannot interpret the communication. Go with Winsock see if you can get a replay based of that.
If you are customer you can try posting on our internal forums for more personalized support.
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
I tried recording with WinSock protocol replay script was not successful. I was getting connection aborted message.
I tried different combinations of protocols single/multiple. I was able to record using .NET protocol but there is not much calls in the recorded scenario.
I have attached my simple scenario that launch the Log in window.
Binary data can also be correlated though it can be a bit tricky to correlate it. Try using a good text comparison tool for the two recordings for your business flow. There you should be able to make the difference.
Also look out for adding explicit headers just above the transaction where it throws HTTP500. You may look into the tree view and compare the request body and header to see the differences.
Hope this helps.