ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

The Endpoint Protection Manager reports deadlocks on the COMPUTER_APPLICATION table


Article ID: 171944


Updated On:


Endpoint Protection


The Endpoint Protection Manager (SEPM) reports multiple unexpected server errors.  Log entries show deadlocks on the COMPUTER_APPLICATION table. 


2018-06-23 10:37:43.632 THREAD 122 SEVERE: Unexpected server error.
com.sygate.scm.server.metadata.MetadataException: Transaction (Process ID 83) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

sql trace:

   <process id="process177c37c38" taskpriority="0" logused="0" waitresource="PAGE: 6:4:444445 " waittime="6408" ownerId="1394469658" transactionname="UPDATE" lasttranstarted="2018-06-22T10:37:38.110" XDES="0xd7689a10" lockMode="U" schedulerid="1" kpid="2440" status="suspended" spid="83" sbid="0" ecid="4" priority="0" trancount="0" lastbatchstarted="2018-06-23T10:37:38.110" lastbatchcompleted="2018-06-22T10:37:38.097" lastattention="1900-01-01T00:00:00.097" clientapp="Microsoft JDBC Driver for SQL Server" hostname="sepm" hostpid="0" isolationlevel="read committed (2)" xactid="1394469658" currentdb="6" lockTimeout="4294967295" clientoption1="671088672" clientoption2="128056">
     <frame procname="adhoc" line="1" stmtstart="268" sqlhandle="0x02000000fca3862bd031ba0001cec1f65b0bd1f0ee820cb50000000000000000000000000000000000000000">
update COMPUTER_APPLICATION set [email protected] , [email protected] , [email protected] , [email protected] where DOMAIN_ID= @P4 AND APP_HASH= @P5 AND AGENT_ID= @P6 AND [email protected]     </frame>
     <frame procname="unknown" line="1" sqlhandle="0x0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000">
unknown     </frame>
(@P0 nvarchar(4000),@P1 nvarchar(4000),@P2 int,@P3 bigint,@P4 nvarchar(4000),@P5 nvarchar(4000),@P6 nvarchar(4000),@P7 nvarchar(4000))update COMPUTER_APPLICATION set [email protected] , [email protected] , [email protected] , [email protected] where DOMAIN_ID= @P4 AND APP_HASH= @P5 AND AGENT_ID= @P6 AND [email protected]                                                                    </inputbuf>


The SEPM fails to lock the COMPUTER_APPLICATION table properly when updating entries in the table.  This can lead to multiple SEPMs attempting to update the table at the same time. 


This issue is fixed in Symantec Endpoint Protection (14.2 MP1)  For information on how to obtain the latest build of Symantec Endpoint Protection, see Download the latest version of Symantec Endpoint Protection.

As a workaround, you can increase the interval between log uploads for this log type.  This should reduce the frequency of the deadlocks until a fix is available. 

  1. Edit (C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\etc) with this value: scm.timer.appcollection=3600
  2. Restart the Endpoint Protection Manager services. (semsrv, semwebsrv, semlaunchsrv, semapisrv)