Kirjaudu sisään Microsoft-tilillä
Kirjaudu sisään tai luo tili.
Hei,
Käytä toista tiliä.
Sinulla on useita tilejä
Valitse tili, jolla haluat kirjautua sisään.
englanti
Olemme pahoillamme. Tämä artikkeli ei ole saatavilla tällä kielellä.

Symptoms

Assume that you have an instance of Microsoft SQL Server 2014, 2016 or 2017 that has buffer pool extension (BPE) enabled. If you experience an I/O error that occurs on the BPE file, BPE may be disabled, and a buffer time-out error that resembles the following is logged:

L2 buffer pool write error…
Buffer pool extension has been disabled successfully. Deleting buffer pool extension "file_path".
A time-out occurred while waiting for buffer latch -- type 4...
Error: 845, Severity: 17, State: 1.
Time-out occurred while waiting for buffer latch type 4 for page (page_id)...
Error: 5901, Severity: 16, State: 1.
One or more recovery units belonging to database 'database_name' failed to generate a checkpoint. This is typically caused by lack of system resources such as disk or memory, or in some cases due to database corruption. Examine previous entries in the error log for more detailed information on this failure.
A time-out occurred while waiting for buffer latch -- type 3…

When this issue occurs, some orphaned buffer latches remain, and any operation such as DBCC CHECKDB, CHECKPOINTING, or BACKUP LOG fail.

Note If you update to Cumulative Update 1 for SQL Server 2014 Service Pack 1, the error still cannot be resolved.

Resolution

Cumulative update information:

This issue is fixed in the following updates for SQL Server:

       Cumulative Update 14 for SQL Server 2017

       Cumulative Update 5 for SQL Server 2016 Service Pack2

       Cumulative Update 1 for SQL Server 2014 Service Pack 3

       Cumulative Update 15 for SQL Server 2014 Service Pack 2

Each new cumulative update for SQL Server contains all the hotfixes and security fixes that were in the previous build. We recommend that you install the latest build for your version of SQL Server: 

Latest cumulative update for SQL Server 2017

Latest cumulative update for SQL Server 2016

The latest cumulative updates for SQL Server 2014

On-demand hotfix information:

This issue is fixed in the following on-demand hotfix update for SQL Server:

       On-demand hotfix update for SQL Server 2016 SP2 CU4  

Status

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

References

Learn about the terminology Microsoft uses to describe software updates.

Tarvitsetko lisäohjeita?

Haluatko lisää vaihtoehtoja?

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.

Oliko näistä tiedoista hyötyä?

Mikä vaikutti kokemukseesi?
Kun valitset Lähetä, palautettasi käytetään Microsoftin tuotteiden ja palveluiden parantamiseen. IT-järjestelmänvalvojasi voi kerätä nämä tiedot. Tietosuojatiedot.

Kiitos palautteesta!

×