Views:

When the deadlock issue happens, The SQL Server Logs (serve0.log) may show error similar to the following:

00 00:40:39.950 54 <?query --(@P0 int,@P1 int)INSERT INTO saphosts (HostID, SAPState) VALUES ( @P0 , @P1 ) SELECT SCOPE_IDENTITY() AS _JTDS_GENE_R_ATED_KEYS_--?> <domain name>\<service account> NULL 218 8 2 NULL 22,007 5 0 7 sleeping 1 NULL <server name> DSM Trend Micro Inc. 2016-12-05 10:45:58.913 2016-12-05 10:44:32.247 NULL 2016-12-05 11:26:39.543

As a workaround, do the following:

  1. Stop the Deep Security Manager service on all nodes.
  2. Open the dsm.properties file located on these paths:
    • For Windows: Program Files\Trend Micro\Deep Security Manager\webclient\webapps\ROOT\WEB-INF
    • For Linux: /opt/dsm/webclient/webapps/root/web-inf/
  3. Add the following line:

    database.SqlServer.useReadCommittedSnapshot=true

  4. Restart the Deep Security Manager service.
Keywords: DeadLock issue,sql deadlock,Microsoft SQL Server deadlock problem,serve0.log deadlock,Could not obtain lock