Select the product you need help with

FIX: Error 17883 when you run a query on a server that has many CPUs and a large amount of memory in SQL Server 2012 or in SQL Server 2008 R2

Article ID: 2801379 - View products that this article applies to.

Expand all | Collapse all

Symptoms

Consider the following scenario:

You install Microsoft SQL Server 2012 on a server that has many CPUs. For example, the server has 128 CPUs.
The server has a large amount of memory. For example, the server has 256 gigabytes (GB) of installed RAM.
You run a query in SQL Server 2012.

In this scenario, error 17883 is logged in the SQL Server error log, and the error details resemble the following:

Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 53, ECID 1, UMS Context 0x04069D90

Additionally, a mini-dump file is generated in the SQL Server log folder.

Back to the top | Give Feedback

The fix for this issue was first released in Cumulative Update 7. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:

2823247

(http://support.microsoft.com/kb/2823247/ )

Cumulative update package 7 for SQL Server 2012

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2692828

(http://support.microsoft.com/kb/2692828/ )

The SQL Server 2012 builds that were released after SQL Server 2012 was released

Cumulative Update 5 for SQL Server 2008 R2 SP2

The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 SP 2, click the following article number to view the article in the Microsoft Knowledge Base:

2797460

(http://support.microsoft.com/kb/2797460/ )

Cumulative update package 5 for SQL Server 2008 R2 Service Pack 2

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 SP 2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2730301

(http://support.microsoft.com/kb/2730301/ )

The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released

Cumulative update 2 for SQL Server 2012 Service Pack 1 (SP1)

The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2012 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

2790947

(http://support.microsoft.com/kb/2790947/ )

Cumulative update package 2 for SQL Server 2012 Service Pack 1

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 Service Pack 1 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2772858

(http://support.microsoft.com/kb/2772858/ )

The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released

Back to the top | Give Feedback