7 Answers
7

I also ran into this error message when upgrading a 2007 site to 2010. A custom list had a custom edit form. There are about 150 fields in this list. It appears the error message is caused by the time it takes the DataFormWebPart to render out the content.

So SP1 added a check that if it takes > 5 seconds, throw the Exception. Now, I believe that time has been reduced to a SINGLE SECOND. So if it takes more than a second to render your content (and that's likely with 100 fields), you'll get this exception.

I have been able to work around this issue by way of InfoPath.

I am positive if you were to comment out in the markup for the DataFormWebPart, all but just 10 or so fields, you won't have any errors...Uncomment the rest, and the issue will return.

We attempted to use BCS and found that the response rate for queries over 10 records was inordinately slow versus what logic tells you should be the response rate for queries. We have since banned the use of BCS in our SharePoint environment and favor WebApi JSON for data requests. It is orders of magnitude faster and more flexible.