Can't use SAVE TRANSACTION within a distributed transaction
Last Modified: 2023-07-26 06:55:26 Etc/GMT
Affected Products
Languages:
This article is available in the following languages:
Trellix CEO, Bryan Palma, explains the critical need for security that’s always learning.
As per Gartner, "XDR is an emerging technology that can offer improved threat prevention, detection and response."
Trellix announced the establishment of the Trellix Advanced Research Center to advance global threat intelligence.
Trellix Advanced Research Center analyzes threat data on ransomware, nation-states, sectors, vectors, LotL, MITRE ATT&CK techniques, and emails.
As of May 14, 2024, Knowledge Base (KB) articles will only be published and updated in our new Trellix Thrive Knowledge space.
Log in to the Thrive Portal using your OKTA credentials and start searching the new space. Legacy KB IDs are indexed and you will be able to find them easily just by typing the legacy KB ID.
Can't use SAVE TRANSACTION within a distributed transaction
Technical Articles ID:
KB90867
Last Modified: 2023-07-26 06:55:26 Etc/GMT Environment
ePolicy Orchestrator (ePO) 5.x SQL Server 2016, 2017 - all supported variants For details of ePO- and SQL-supported environments, see KB51569 - Supported platforms for ePolicy Orchestrator. Problem
Changes that you make in ePO aren't written to the SQL Server 2016 or 2017 database. Regardless of the ePO version, any changes you make within ePO aren't written to the SQL Server database. For example:
At net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2999) At net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2432) At net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:678) At net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:647) Cause
A known Microsoft SQL Server issue causes this issue. For details, see the following:
Solution
Install one of the following SQL cumulative updates:
Affected ProductsLanguages:This article is available in the following languages: |
|