Video Screencast Help

sql error

Created: 05 Aug 2012 • Updated: 14 Aug 2012 | 3 comments
This issue has been solved. See solution.

The EnterpriseVault.DirectoryService object reported an error.

 The SQL database server detected a deadlock while accessing the Vault Database '%2'

 Description:

 %1

 Additional Microsoft supplied information:

 Source: %3

Number: %4

SQL State: %5

Native Error: %6

HRESULT %7

 

SQL Command:

%8

 

For more information, see Help and Support Center at http://evevent.symantec.com/rosetta/showevent.asp?EvtID=839

Getting the above error!!

What would u suggest??

Regards,

Navinkumar

Discussion Filed Under:

Comments 3 CommentsJump to latest comment

Wayne Humphrey's picture

run SQL profiler, and trace deadlocks ;)

SOLUTION
RahulG's picture

Do you log shipping enable on the SQl server , that can be one of the reason for the dead locks>

JesusWept3's picture

Honestly i've never heard of deadlocks being caused by log shipping before.
However the exact event that you posted sounds like its probably not a deadlock at all but another issue and EV is just mis-reporting it (I have seen this previously in other environments)

Deadlocks can be a pain to truly resolve, have a look at this walkthrough to implement what Wayne was suggesting:
http://www.mssqltips.com/sqlservertip/1222/sql-server-profiler-graphical-deadlock-chain/

The issue you have though is you only have a few supported options.
Most of which are making sure you aren't facing a lot of disk I/O latency and contention between databases, optimizing your indexes, running DBCC showcontig to make sure the database isn't highly fragmented etc, and just anything you can do to improve performance.

If they are true deadlocks, you will need to pass the SQL Profiler trace and a dtrace of whatever is causing it to support, as opposed to slapping on extra indexes that may not make any difference to the case at all.

When you run the profiler, it is best to get a dtrace of Directory Service and any other process that is throwing errors in the event log around that same time (for instance you might see a Storage Archive error right before each deadlock, in which case you want Directory Service and Storage Archve) along wit the correct SQL Profiler trace as well