Question

I have an issue with several SharePoint 2010 installations that have "corrupt" HTML on their web pages (how to explain). It' like the site stops sending HTML data midway through the transfer of the HTML data. Images come out corrupt. HTML and images don't fully load in the browser. It's not the source files of the server.

If SharePoint runs out of memory on the web front end can it cause this problem? Can an out of memory exception in IIS cause SharePoint to terminate during the transfer of HTML and image data to the browser?

Was it helpful?

Solution

Symantec End Point Protection.

It seems that Symantec for Windows 2008 isn't all it's cracked up to be. People have been reporting problems with getting access to servers, bad data etc. While I'm not 100% positive that it's the problem, now that I have removed the software I am no longer experiencing the problems.

OTHER TIPS

To answer the question, the expected behaviour of SharePoint under memory stress is that page response times would increase dramatically as Windows tries to thrash memory pages to disk. Sending garbage back to the client is not what you would expect.

These problems suggest something wrong with the server, but you talk about having this problem with several installations, presumably on different hardware. Do you have custom code? What do these installations have in common? Do they share a database server? I'm afraid that there isn't enough information to start to narrow down what the problem might be.

Licensed under: CC-BY-SA with attribution
Not affiliated with sharepoint.stackexchange
scroll top