Transaction (Process ID 51) was deadlocked on { lock }

Guest · Post by **Guest** » Thu Apr 07, 2005 1:52 pm

.... resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

I'm getting these in our logs today, users reporting weirdness with folders missing, inability to connect, one repository's info showing in another repository, etc... but only to some users.

What do those messages mean, and what can we do to stop them?

Thanks.

Post by **jclausius** » Thu Apr 07, 2005 2:00 pm

What version of Vault server are you using? What does a good portion of the Log look like?

Guest · Post by **Guest** » Thu Apr 07, 2005 2:04 pm

version 3.0.

There are those lines, and these:

Attempt to fetch logical page (1:991304) in database 'sgvault' belongs to object 'tblcheckoutlistitems', not to object 'tbltreerevisionfolders'.

and
GetREpositoryStructure returned: FailInvalidRevision

it's these three messages all over the place for a number of developers attempting to access the system.

Post by **jclausius** » Thu Apr 07, 2005 2:10 pm

When was the last time you ran a DBCC CHECKDB command? Also, is it possible there is something up with the disks where SQL Server is keeping the Vault database.

This looks like the SQL Server detected an issue with your database - See Troubleshooting
Error 605 for trouble shooting assistance.