Select the product you need help with
FIX: The SQL Server service stops responding, and you receive error 1450 when you create database snapshot or run a DBCC CHECK statement on a database in SQL Server 2005 and in SQL Server 2008Article ID: 967164 - View products that this article applies to. Microsoft distributes Microsoft SQL Server 2005 or Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 or Microsoft SQL Server 2008 fix release. On This PageSYMPTOMSOn a Windows Server 2003-based server that has Microsoft SQL Server 2005 or Microsoft SQL Server 2008 installed, consider the following scenarios:
The operating system returned error 1450(Insufficient system resources exist to complete the requested service.) to SQL Server during a write at offset 0x0000159d8ae000 in file with handle 0x0000000000000AAC. This is usually a temporary condition and the SQL Server will keep retrying the operation. If the condition persists then immediate action must be taken to correct it. CAUSEThis issue occurs because the sparse file for a database snapshot file has exceeded the file size limitation in NTFS file system. When the operating system error 1450 occurs, SQL Server enters an infinite retry loop. RESOLUTIONCumulative update information for SQL Server 2005 Service Pack 2The fix for this issue was first released in Cumulative Update 14 for SQL Server 2005 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:970278 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. 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:
(http://support.microsoft.com/kb/970278/LN/
)
Cumulative update package 14 for SQL Server 2005 Service Pack 2937137
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
(http://support.microsoft.com/kb/937137/LN/
)
The
SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
Cumulative update information for SQL Server 2005 Service Pack 3The fix for this issue was first released in Cumulative Update 2 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:961930 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. 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:
(http://support.microsoft.com/kb/961930/LN/
)
Cumulative update package 2 for SQL Server 2005 Service Pack 3960598
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
(http://support.microsoft.com/kb/960598/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
Cumulative update information for the release version of SQL Server 2008The 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, click the following article number to view the article in the Microsoft Knowledge Base:963036 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:
(http://support.microsoft.com/kb/963036/
)
Cumulative update package 4 for SQL Server 2008956909
(http://support.microsoft.com/kb/956909/
)
The SQL Server 2008 builds that were released after SQL Server 2008 was releasedCumulative update information for SQL Server 2008 Service Pack 1The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 Service Pack 1. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:969099 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:
(http://support.microsoft.com/kb/969099/
)
Cumulative update package 1 for SQL Server 2008 Service Pack 1970365
(http://support.microsoft.com/kb/970365/
)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was releasedSTATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONAfter you apply this hotfix, for scenario 1, the DBCC command stops immediately when the first error 1450 is encountered. For scenario 2, the snapshot database is marked as suspect when the first error 1450 is encountered for a write to the snapshot file. Additionally, you see error messages that resemble the following in the SQL Server error log file: Date Time SPID The operating system returned error 1450(Insufficient system resources exist to complete the requested service.) to SQL Server during a write at offset 0x0000159655e000 in file 'C:\SparseFileProblem\snapshotdb.mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online. Date Time SPID Error: 17053, Severity: 16, State: 1. Date Time SPID C:\SparseFileProblem\ snapshotdb.mdf: Operating system error 1450(Insufficient system resources exist to complete the requested service.) encountered. Date Time SPID Error: 3420, Severity: 21, State: 1. Date Time SPID Database snapshot 'fillvmsnap' has failed an IO operation and is marked suspect. It must be dropped and recreated. http://msdn.microsoft.com/en-us/library/ms188796.aspx
(http://msdn.microsoft.com/en-us/library/ms188796.aspx)
More information about cumulative update package 2 for SQL Server 2005 Service Pack 3For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:961930
(http://support.microsoft.com/kb/961930/LN/
)
Cumulative update package 2 for SQL Server 2005 Service Pack 3More information about cumulative update package 14 for SQL Server 2005 Service Pack 2For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:970278
(http://support.microsoft.com/kb/970278/LN/
)
Cumulative update package 14 for SQL Server 2005 Service Pack 2More information about cumulative update package 4 for the release version of SQL Server 2008For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:963036
(http://support.microsoft.com/kb/963036/LN/
)
Cumulative update package 4 for SQL Server 2008More information about cumulative update package 1 for SQL Server 2008 Service Pack 1For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:969099
(http://support.microsoft.com/kb/969099/LN/
)
Cumulative update package 1 for SQL Server 2008 Service Pack 1REFERENCES
For more information about the list of builds that are available after SQL Server 2005 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:
960598
For more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/960598/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
937137
For more information about the list of builds that are available after the release of SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/937137/
)
List of the builds that are available after SQL Server 2005 Service Pack 2 was released
956909
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/956909/
)
The SQL Server 2008 builds that were released after SQL Server 2008 was released
935897
For more information about how to obtain SQL Server 2005 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/935897/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
913089
For more information about the new features in SQL Server 2005 SP3 and about the improvements in SQL Server 2005 SP3, visit the following Microsoft Web site:
(http://support.microsoft.com/kb/913089/
)
How to obtain the latest service pack for SQL Server 2005
http://go.microsoft.com/fwlink/?LinkId=131442
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
(http://go.microsoft.com/fwlink/?LinkId=131442)
822499
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/
)
New naming schema for Microsoft SQL Server software update packages
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
PropertiesArticle ID: 967164 - Last Review: June 16, 2009 - Revision: 4.0 APPLIES TO
|


Back to the top








