Applies ToSQL Server 2016 Developer - duplicate (do not use) SQL Server 2016 Enterprise - duplicate (do not use) SQL Server 2016 Enterprise Core - duplicate (do not use) SQL Server 2016 Standard - duplicate (do not use)

Symptoms

Consider the following scenario:

  • You have an Always On Availability Group (AG) with DTC_SUPPORT = PER_DB.

  • You create a linked server which points to itself.

  • You create a transaction which accesses a database that participates in the AG by using the linked server together with any other database on the server, or even the same database without the linked server.

In this scenario, an assertion will occur, and you may receive error messages that resemble the following:

DateTime spid SpidNumber     * Expression:  ITaskProxy::FIsCurrentTaskProxy (m_owningTaskProxy)

DateTime spid SpidNumber     * SPID:   SpidNumber

DateTime spid SpidNumber     * Process ID: ProcessNumber

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Resolution

The issue is fixed in the following cumulative updates for SQL Server:

About cumulative updates for SQL Server:

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:

References

Learn about the terminology that Microsoft uses to describe software updates.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.