Jeff, thanks for the answer. Tony from PowerDNN has jumped in with more details and I appreciate that. I have also posted another image with various errors. Note that the image is huge so it will take a while to load. Hopefully between what I show and the added information from Tony, there's an answer out there.

Paul, the hosting company is PowerDNN, as you've probably seen in other messages. I'm using shared hosting, but an unsure what edition of SQL (Tony can answer that.) The DB size is 26.1MB. I'm not sure on the server specs; again, Tony could provide more insight.

I would be tracing the sql in question for that call, and checking to see that, for some reason, the Sql result sets are coming back incorrect.  As Mitch says, the errors look like failures to read the record set - probably due to missing or incorrectly-named columns.  It may be load based, date-based : anything can cause an intermittent error.  I have never heard of Sql server bringing back corrupted result sets but everything is possible.

If there is no customisation of the module, then I see no harm in re-running all of the sqldataprovider files from the install package again.  This would take 10 minutes and assure you that modification of the stored procedures is not the cause.

Another thought : if it is load related, would page-level caching solution help?