Security Error: Database error [CMM001300] when displayed detected software product
search cancel

Security Error: Database error [CMM001300] when displayed detected software product

book

Article ID: 418779

calendar_today

Updated On:

Products

CA Client Automation - IT Client Manager CA Client Automation

Issue/Introduction

When trying to see "detected software product" following error appears :

"Security Error: Database error [CMM001300]"

The same message appears when we try to view the permissions of a software product.

In TR_GUI_*.log we could see this error :

GUI       |RecImpl_Ado     |RecImpl_Ado.cpp     |002511|DETAIL | ExecuteCommandPointer sqlwparam: SELECT ace, access FROM ca_object_ace WHERE object_def_uuid = <UUID> AND object_type = 1008 AND (( security_profile_uuid IN (SELECT security_profile_uuid FROM ca_link_dis_user_sec_profile WHERE user_uuid = <UUID> ))OR security_profile_uuid = (SELECT security_profile_uuid FROM ca_link_object_owner WHERE object_uuid = <UUID> AND owner_uuid = <UUID> ))

GUI       |DbImpl_Ado      |DbImpl_Ado.cpp      |002311|NOTIFY | evalSQLInfo sqlstate: HY000 native error: 596 0x254
GUI       |DbImplAdo       |DbImpl_Ado.cpp      |002358|NOTIFY | evalSQLInfo class: 21 state: 1 server: <SQLSERVERNAME>
GUI       |CDb             |DbImpl_Ado.cpp      |002584|NOTIFY | Error Message: ADO Version 10.0 - ExecuteCommandPointer []  -COM Error: ErrorCode:-2147467259,WordErrorCode:0, Unbekannter Fehler, Cannot continue the execution because the session is in the kill state., Microsoft SQL Server Native Client 11.0, (null)

Environment

Client Automation - All Versions

Cause

On Microsoft SQL Server In C:\Program Files\Microsoft SQL Server\<SQLINSTANCE>\MSSQL\LOG\errorlog, we could see a fatal exception c0000005 at the same time :

2025-11-17 14:47:44.40 spid116     ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL16.<SQLINSTANCENAME>\MSSQL\LOG\SQLDump8818.txt
2025-11-17 14:47:44.40 spid116     SqlDumpExceptionHandler: Process 116 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2025-11-17 14:47:44.40 spid116     * *******************************************************************************
2025-11-17 14:47:44.40 spid116     *
2025-11-17 14:47:44.40 spid116     * BEGIN STACK DUMP:
2025-11-17 14:47:44.40 spid116     *   11/17/25 14:47:44 spid 116
2025-11-17 14:47:44.40 spid116     *
2025-11-17 14:47:44.40 spid116     *
2025-11-17 14:47:44.40 spid116     *   Exception Address = <frame id="00" address="0x7FFFC422F177" pdb="qds.pdb" age="2" guid="<GUID>" module="qds" rva="0x5F177" />
2025-11-17 14:47:44.40 spid116     *   Exception Code    = c0000005 EXCEPTION_ACCESS_VIOLATION
2025-11-17 14:47:44.40 spid116     *   Access Violation occurred reading address 0000000000000078

2025-11-17 14:47:44.42 Server      Error: 17310, Severity: 20, State: 1.
2025-11-17 14:47:44.42 Server      A user request from the session with SPID 116 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.

It seems problem occurs in qds.dll file.

Resolution

Restart of Microsoft SQL Server could resolved the problem :

  1. On Domain Manager stop caf :
    caf stop

  2. Reboot the Microsoft SQL Server or restart the Microsoft SQL Server service.

  3. On Domain Manager start caf :
    caf start

 

If this does not resolve the problem, open a case at Microsoft Technical Support to analyze why there is fatal exception c0000005 in sqlserver process.
Under C:\Program Files\Microsoft SQL Server\<SQLINSTANCENAME>\MSSQL\LOG, there are some sqldump*.txt and SQLDmpr.*.dmp files which could help for the analysis.

Additional Information

Possible workaround :

It seems the crash occurs in qds.dll. Maybe this is related to Query Store feature of SQL Server.

 

It is possible to disable this feature with this :

1- Open the properties of mdb database.
In Query Store, select 

"Operation Mode (Requested)" = Off

2- This will disable the Query Store feature for mdb database and maybe it could avoid the crash.