"We're sorry, but something went wrong." issue during Replay scrip

[Sumit Agarwal]

Hi All,

I am getting one issue during replay i.e. "We're sorry, but something went wrong.

A log entry has been created about this issue. Please try your request again and if the issue persists contact your help desk to inform them of the issue."

I have tried different scenarios but getting same issue with each scenario. For understanding i am writing Scenario navigation :-

1. Login -> Default page -> Favorite Tab

2. Login -> Default page -> General Tab

after login , its going to default page. after that i am selecting any tab. I am getting same issue.

Please advice me, if this issue with scripting? Or if this issue with Application.

Thanks,

Sumit Agarwal

[James Pulley]

( a )  Did you contact the Help Desk as suggested to understand the log message?

( 2 )  Yes, your test code is not correct in its representation of end user behavior if you receive this in test with your test code and not manually

( iii )  You very likely have an issue with dynamic data that needs to be addressed

( * )   http://www.perfbytes.com/dynamic-data-correlation

[Sumit Agarwal]

Hi James,

I have raise a concerned to team. Recording is working fine. During Replay we are facing issue. For each action we are getting successful response i.e. 200OK HTTP Status, But for that particular action we are getting 302 HTTP Status.

Also i have checked Response URL of Recording & Replay mode, both are different. For understand, pls find the example below:-

Recording -> Response  :- %2fgoogle%2fcompose.aspx%3ftc%3d1">here</a>.</h2>

Replay -> Response :-    %2google%2fError.htm%3faspxerrorpath%3d%2fgoogle%2fdefault.aspx">here</a>.</h2>

Response indicates a re-direct to default page again....................

Also we are going to watch sql trace as well App server logs during running a script. Please suggest on same.

[Sumit Agarwal]

(2) Not sure if this issue is due to that. Sometimes we are getting 500 error during manual navigation.

On Monday, August 4, 2014 6:15:30 PM UTC+5:30, James Pulley wrote:

[James Pulley]

302 is a temporary redirect.  This is dictated by the application design and/or installation.  Unless you have modified the default behavior of LoadRunner the 302 returned link should be followed and loaded.

Foundation skills:  HTTP Architecture

[James Pulley]

500 errors are most commonly caused by not checking for expected results and then not branching the execution of the code when an unexpected result occurs.   You will see this often paired with "continue on error" being turned on without the code checks and explicit branching mandated by electing such an option.

[Sumit Agarwal]

Hi James,

Could you suggest me some solution on same?? Can you do something during script enhancement or RTS?

[James Pulley]

Test 101.   Every Step has an expected result.  Check for it.  If you do not receive it then include code to cleanly branch to exit to a clean condition before restarting the iteration.

--
You received this message because you are subscribed to the Google Groups "LoadRunner" group.
To unsubscribe from this group and stop receiving emails from it, send an email to LR-LoadRunne...@googlegroups.com.
To post to this group, send email to LR-Loa...@googlegroups.com.
Visit this group at http://groups.google.com/group/LR-LoadRunner.
For more options, visit https://groups.google.com/d/optout.

[Sumit Agarwal]

Hi James,

I checked Error Logs, I am getting this message in logs :-

System.Web.UI.ViewStateException: Invalid viewstate. Client IP: 142.10.123.78 Port: 1389 User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows; Trident/4.0) ViewState: wv1vk4l289lil8ovXkqTH3DuQCSbSfOrAoLP9UCC29vox0UQF0hDfkZHqHeOGoUkQofq+hTq9CGPebHdbnfPZEqNN5zixb5/jB5xr/z7ohwI+tQJPiuzjfGFo2ATPLdwSj/S+N4ibnir3wZY22bBg6BE/HXV6gFgBY+yENsRXpHKgASUhdiMWWRff+GjsNUmroGaMkFa9DhHBTUGCa52t5KCYE4H8uyf43u8HCjLlZFCFKwj4KHHTiN9ltFHVzHw+bY6C9ulFI+URHB0bce3jykHcebooiGkWwt1wpZxhmPkpRkchyXSUn1g9PFi6Z63t9MmAyay0kNWFdtcukRHqHCNRtU23AaRzeb8RijfyTPCaFTmdNxYHl0Y/o7yiLVV6zefjvwzf99AmVhNslY4N8nAEtDLnzzRrDiw5/+UjJ2GaR2qxp/e7KMZbolOh2wGwqtv6njy9y8qvbZa9fjcUCHxtco5Fm9Tx8yuYsROAXDbJ7efy3PcBfWTpR/AtOICrhP/0/HZcDwTd9bFdtqtQSQkOHHKD0JhT8VlJT9r4TT/U+I2adStMVrmyyHfXHit0Jpt3KQA3w6HJA8LVDyoiNegNEsp+HNt/v4HG/MDvkpK8Bxv7M/ef/wVner4Wy2fqG7vQggqRUtDXPBsIy5sTUbB2gyD6zfnCkJEf2QmlBaPhWmdBs3HEva+u7TKhJICtaXCjC3BhDBLMVFPdci1I7BEBRo/mY2p4icIRNSpjXjp/T37Mq3oRuQzUshDqNu63YNtRbLeY+kH2ex7ifPXP5pHpbckKF25Aih1tmgXviYqTM4+ZHRpDa0IrPgL2rILZWWimHPhOz6zJV27B7s3GyroiIQvZDUAvQWi5UPVmSJgF6Fqdekt05NdZwjdbXak...

[HttpException (0x80004005): Validation of viewstate MAC failed. If this application is hosted by a Web Farm or cluster, ensure that <machineKey> configuration specifies the same validationKey and validation algorithm. AutoGenerate cannot be used in a cluster.


I also checked, we are getting 200 OK for each request.

[James Pulley]

You missed a correlation.  Do not "reply all" to messages

http://www.perfbytes.com/dynamic-data-correlation