I am working with the same products (more exactly with new builds of the same products) again and again, so I am trying to create correlation libraries for the products I am working with. Now I am back to a product using huge VIEWSTATEs (typical for programs using .Net). When I created a standard correlation rule “Search for parameters in all of the body text” with left boundary ViewState”value=” and right boundary “, it correlated just the first (and smallest) VIEWSTATE. Which somewhat correlated with my recollections of the issue. Google search provided multiple documents describing the issue – and most stated that LoadRunner is incapable to auto-correlate large VIEWSTATES ( here is an example). I also found HP document “The ASP.NET ViewState parameter” (Document ID: KM179371) with some rules attached. To my surprise one of the rules did correlated all VIEWSTATEs ! It was another kind of rules I didn’t use before: “Parameterize form field value” with Field Name __VIEWSTATE. There was a bug there too: web_set_max_html_param_len(“19228″); was placed after the request returning the parameter (so need to be moved manually). But it was the minor inconvenience comparing with necessity to manually replace multiple huge VIEWSTATEs.