Database deadlock

[XB]

Running a server-side job I get a popup:

 

Database error:

Transaction (Process ID 67) was deadlocked on lock resources with

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

transaction.

 

If I click on retry the console stops. However, the job still executes succesfully.

 

Any help appreciated.

 

[XB]

Eventlog:

 

Faulting application name: eXpress.exe, version: 13.0.0.1246, time stamp: 0x5570c67d
Faulting module name: mfc120.dll, version: 12.0.21005.1, time stamp: 0x524fabbd
Exception code: 0xc0000005
Fault offset: 0x0029b614
Faulting process id: 0xf1c
Faulting application start time: 0x01d13bd182cfd9e1
Faulting application path: C:\INFRA\APPS\DS21.2\Altiris\Deployment Server\eXpress.exe
Faulting module path: C:\Windows\SYSTEM32\mfc120.dll
Report Id: 8d44065b-a7c7-11e5-80f0-0050569c5cc4
Faulting package full name: 
Faulting package-relative application ID: 

[andykn101]

There's a KB article from Symantec on how to track blocked processes in SQL, it;s related to ITMS but should work with GSS: How can I view currently blocked SPIDs in SQL? http://www.symantec.com/docs/HOWTO9817

[fabio.sanches]

Hi XB,

These SQL commands can help you to prevent deadlocks:

ALLOW_SNAPSHOT_ISOLATION ON;

READ_COMMITTED_SNAPSHOT ON; ​

Please let us know if you need more help.

Regards,

[ianatkin]

As this is something that should not happen, I'd take a look at the following,

 1) Is the SQL on or off box? On-box SQL is generally preferrable for GSS where possible

 2) What is the SQL loading like, and what are the general resources looking like on the GSS box?

 3)  Do you have any custom SQL which might interferring with normal GSS DB activity

 4) How many clients do you have, and are you using SQL Express?

In short my first stab without firther details is that something is amiss here in either the scaling of the solution or the implementation.

Kind Regards,
Ian./