Anyone have any experience with this error? It's not the database, must be a hardware issue.
After users started reported problems, I tried and could not connect to the database and received this error. I asked everyone to exit normally, and of course some users started killing sessions using task manager. Soon after, I was able to connect to the database in single user mode and ran "autochk full" reporting no errors. I checked the indexes and found count errors in two tables, but that's probably a result of users not able to write to the db. After a reload and letting users back in, they soon reported that the database was not responding again, but after a few moments, it started working correctly and finished out the day with no further problems. I'm thinking maybe a hard drive issue, but I am using a 6 disk array on windows 2003. The event logs do not report any problems. I asked one of my PC support guys to check cables for wear and tear. Not sure how I am going to proceed, I think I may move the database to another server. Kenny
