HI,

Ive seen the error from jimmy crackcorn before, you are right it does occur when running a large time consuming function, ive found it happens because of time outs that are set in SQL server. increasing these does seem to help somewhat, however you should probobly be looking at your report first. Ive found sometimes it doesn't seem to matter how much you extend the timeout, the error still occurs, but altering the report execution or structure, fixes this issue.

finally mdacs etc should also be looked at as well.

Not a fix but hopefully a step in the right direction ?

Cheers

Adam