Microsoft KB Archive/938910

= FIX: Error message when you execute a maintenance plan that contains a Rebuild Index task in SQL Server 2005 Service Pack 2: &quot;The Execute method on the task returned error code 0x8007000E (Exception of type 'System.OutOfMemoryException' was thrown)&quot; =

Article ID: 938910

Article Last Modified on 12/4/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems

-



Bug #: 50001254 (SQL Hotfix)



Microsoft distributes Microsoft SQL Server 2005 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 fix release.



SYMPTOMS
In Microsoft SQL Server 2005 Service Pack 2 (SP2), you use SQL Server Management Objects (SMO) to create a maintenance plan. The maintenance plan contains a Rebuild Index task. The task rebuilds the indexes of many tables or views. When you use the dtexec command prompt utility to execute the maintenance plan, you receive the following error message:

Error:

Code: 0xC0024104

Source: Rebuild Index Task

Description: The Execute method on the task returned error code 0x8007000E (Exception of type 'System.OutOfMemoryException' was thrown.). The Execute method must succeed, and indicate the result using an &quot;out&quot; parameter.

End Error

DTExec: The package execution returned DTSER_FAILURE (1).

Note This problem may also occur when you use other tools to execute the maintenance plan. The problem does not occur in SQL Server 2005 Service Pack 1 (SP1).



CAUSE
This problem occurs because of memory utilization after you install SQL Server 2005 SP2. When you use SMO to generate SQL scripts, the task uses lots of memory. When the operating system cannot provide sufficient memory, you experience this problem.



RESOLUTION
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 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

943656 Cumulative update package 5 for SQL Server 2005 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 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:

937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released

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.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For 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:

943656 Cumulative update package 5 for SQL Server 2005 Service Pack 2

