A: 

It seems like this issue is with the IIS and .net.

Click on Start ->Run and type in the following command if you are using .NET 2.0 framework: %Windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis -i

Detailed discussion here: http://social.msdn.microsoft.com/Forums/en-US/xmlandnetfx/thread/47f6eb6a-b062-4f4d-8b7f-b4afb1b2725d

Shoaib Shaikh
Thanks. Unfortunately, this didn't work for me. The linked discussion seems to be about the *XML parsing error* screen coming up all the time, rather than occasionally, and the more common symptoms aren't mentioned, so I guess it might be a totally different problem.
MGOwen
+1  A: 

The text you are seeing is the page header. I'm guessing both it and the xml parsing error are being caused by the output to the browser being cut off or, even more bizarrely, only a chunk from the response being relayed.

I'd start with the load balancer and see if there are any logs available. After that, I'd try disabling the IIS compression that Aristos mentioned and see if that has an affect (in IIS get properties on the "Web Sites" folder and then go to the Service tab or find out if compression was enabled / changed for that particular site).

After that, you'll probably have to resort to some kind of packet sniffer to see what is actually being sent on either side of the balancer.

Zarigani
Chose the other answer as that's what led us to the solution, but +1 because this was useful and probably correct.
MGOwen
+1  A: 

are the machines sharing the same machine key?
This along with accessing Session state could cause strange errors.

ggonsalv
We tried changing them to different session keys, that causes a worse error (the ASP.NET error message tells you to use the same machine key when load balancing)
MGOwen
+2  A: 

MGOwen I will share my experience for a similar problem that I was have.

Some time ago I have a similar problem, the pages work well, except some pages that after compress them with gZipped they have problems and not working correctly, something like yours.

I discover that the problem was because I set the Content-Length on header, and then for some reason when was going to be gZipped the Content-Length, didn't change / or was calculate false, and the result was a similar error like yours.

So check if you set the Content-Length in a way on your pages, and then use gZip filter. If yes then remove the Content-Length setting in your program.

In general speaking I say that the length have the problem on your page, and the lenght is a variable in Content-Length.

-and in your header the Content-Length exist !-

update
Also one other think that I notice, if your page send as gZip where is that in your head ? if this is the full head of your page.

Aristos
A: 

Is this thread still open? I have the almost the same exact issue.

This is what the bottom of my ASPX page reads in IEwatch after 120seconds.

<script type="text/javascript">
<!--

var Page_ValidationActive = false;
if (typeof(ValidatorOnLoad) == "function") {
ValidatorOnLoad();
}

function ValidatorOnSubmit() {

This is what it should be and shows only after I shut off Gzip on my cisco Ace LB:

<script type="text/javascript">
<!--

var Page_ValidationActive = false;
if (typeof(ValidatorOnLoad) == "function") {
ValidatorOnLoad();
}

function ValidatorOnSubmit() {
if (Page_ValidationActive) {
    return ValidatorCommonOnSubmit();
}
else {
    return true;
    }
}
        // -->
</script>
</form>
</body>
</html>

The thing is, this issue only happens in certain sitations. The aspx just runs some js validation and perform a few calls on a user depending on who they are after it has retrieved their AD attribute. Now the weird part. The issue listed above ONLY happens when the user name is more than 8 characters AND when Gzip is enabled on the LB!!

So to sum it up, I get the cutoff above when: GZIP enabled on LB users login name is more than 8 characters.

My setup: 2 LB Win2k8/64bit/IIS 7.5 Cisco ACE 4710 LB Static & Dynamic compression enabled.

mark
That's pretty strange. Maybe you should paste this into your own question (with a link back to this one).
MGOwen