SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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?

share|improve this question
Do you have anything between your browser and SP? Do you use any proxy? – Wictor Wilen MCA MCM MVP Jun 8 '11 at 15:40
No proxies or any other devices. The client system is connected to the physical ethernetwork to which the server is connected. – user2903 Jun 8 '11 at 15:43
Do you see anything "suspicious" in the ULS logs? Have you done any customizations? – Wictor Wilen MCA MCM MVP Jun 8 '11 at 15:47
IIS stopping midway could explain this, i'd expect a 500 server error though. – Colin Jun 8 '11 at 16:06
P.S could you check eventlogs etc. for outofmemoryexceptions? – Colin Jun 8 '11 at 16:08
up vote 3 down vote accepted

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.

share|improve this answer

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.

share|improve this answer
Ok so to answer: No custom code. The only thing that they have in common is that they are on VMs. No shared database server. Some have 4gbs allocated and some have 6 (both web and database). – user2903 Jun 29 '11 at 4:04
Are all the VMs running on the same physical machine? – SPDoctor Jul 14 '11 at 9:23
They are running on the same physical machine. – user2903 Jul 20 '11 at 18:34
In that case you must be running some third party antivirus product that is messing things up ;-) – SPDoctor Jul 21 '11 at 17:31
Yep most likely. – user2903 Jul 21 '11 at 17:41

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.