• We are experiencing the same problem on one of our SQL Server instances. The only difference is that the server is on a VMWare box.

    Were you able to resolve your problem?