I had this error occur again during heavy usage, so I changed the client's connection type from TCP to Named Pipes, and haven't seen the problem again.

Any idea why Named...