Hi everyone,

we've had the same issue on a 2-node cluster. On 1 node everything runs fine but as soon as everything fails to the other node we encounter this issue randomly. This cluster used to run Windows 2003 R2 SP2 and SQL 2005 SP3 x64.

We rebuilt the cluster on the same hardware this weekend using Windows 2008 R2 and SQL 2008 SP1, and are encountering the same issue with the upgraded software... Grrr....

I'm not too sure if the HBA queue depth contributes to this specific error, although it does help with I/O throughput.

Has anyone been able to resolve this issue? We're left stranded with a half-working cluster now.