Select the product you need help with

SQL Server may report an 18272 error during restore operations

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

Symptoms

While you are restoring a transaction log for a Microsoft SQL Server 2005, a Microsoft SQL Server 2008, or a Microsoft SQL Server 2008 R2 database, you may receive an error that resembles the following in the SQL Server Errorlog file:

Error: 18272, Severity: 16, State: 1.

During restore restart, an I/O error occurred on checkpoint file 'X:\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\CHECK.CKP' (operating system error 1784(The supplied user buffer is not valid for the requested operation.)). The statement is proceeding but cannot be restarted. Ensure that a valid storage location exists for the checkpoint file.

Back to the top | Give Feedback

Cause

This error has a limited impact and does not prevent a restore operation from succeeding. This error message occurs when a restore is interrupted, and the checkpoint file that is used to restart a restore is not written, or the checkpoint file is not written correctly. If you receive this error, it means that, if for some reason the restore operation is interrupted in the middle of the process, you have to restart it from the beginning of the backup file rather than the checkpoint file.

Back to the top | Give Feedback

Resolution

Cumulative update information

SQL Server 2005

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

983329 Cumulative update package 10 for SQL Server 2005 Service Pack 3

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 2005 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:

960598 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released

SQL Server 2008 Service Pack 1

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

2083921 cumulative update 9 for SQL Server 2008 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 2008 fix release. Microsoft recommends 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:

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

Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2008 Service Pack 2

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

2289254 Cumulative update 1 for SQL Server 2008 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 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:

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

SQL Server 2008 R2

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

2345451 Cumulative Update package 4 for SQL Server 2008 R2

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 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:

981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

Workaround

The error message usually occurs when you are restoring from multiple backup files, a process that is sometimes referred to as a "striped restore." To avoid the error, do not specify multiple backup files in your restore operation.

Back to the top | Give Feedback

More Information

The problem is frequently reported by customers who use third-party backup software tools to back up their SQL Server databases. These tools facilitate backup and restore operations across multiple files.

Additional references: