Server Fault is a question and answer site for system and network administrators. 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'm facing a problem which I hope is a configuration thing with IIS but is right now giving a lot of trouble. Basically I have a controller that accepts a JSON and does some processing. While it generally works fine, but every now and then when the system has some load I get an error. After some painful debugging, we figured the incoming JSON gets truncated which causes the deserialzer to fail.

To narrow down the problem - we wrote a simple controller that accepts a JSON and tries to deserialize it. In case it fails it just logs it. This works fine but when I hit it using a load testing tool (JMeter) it throws the same error (truncation) for a few requests. The # of failures increased when I increase parallel connections. It starts showing with > 150 concurrent requests.

We are running IIS 7 on windows 2008 server with ASP.Net MVC 3 with more or less default configuration of IIS.

More information available in my question below

share|improve this question
I have the same problem, have not found the cause yet... – jjxtra Dec 17 '12 at 22:26
Yes - the link in the question to stackoverflow has the solution that I applied. – Guneet Sahai Dec 27 '12 at 13:17

The answer can be found on StackOverflow. It ended up being a bug with a hotfix.

share|improve this answer
This is supposedly fixed in 2008 R2 SP1 but this is not the case as I still experience this problem on that operating system. – jjxtra May 5 '13 at 17:09

Your Answer


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

Not the answer you're looking for? Browse other questions tagged or ask your own question.