A couple of things come to mind.
[ol 1]
[li]Do you have an autosequence for incremental posting running throughout the day? The reports all post totals before running to make sure everything is up to date. They may be timing out if they have to post an entire day's worth. Employee posting is exceptionally inefficient, so that may be the problem.[/li]
[li]Check your time card and job code reports. Do you have anyone who hasn't clocked out in a while, or who's shift hasn't incremented and is now spanning multiple days? Often this will be managers who don't have to clock in, and who's shift(s) aren't ending with the EOD autosequence. When you have somebody clocked in for a long time, or somebody who doesn't have to clock in, the posting has to go all the way back to the beginning of the shift and accumulate the totals. The employee posting uses a loop to do this, so if it has to go way back it takes forever, and actually slows down a little bit with each iteration of the loop.[/li]
[/ol]
Posting is global, so when you run an employee report the totals are posted for all employees. This means that if a server's report is timing out, the problem isn't necessarily with that server, it may be caused by a manager or chef with a current shift that's a few weeks long.