So are we; we found retrospectively that when our IT people upgraded to version 10 (quite seamlessly to the rest of us), our server performance degraded very quickly, and we began noticing the type of error that you've mentioned. Whilst I'm still not 100% convinced that was what the problem was, we stopped getting the errors when we rolled back the server to version 9....