FIX: "SOS_Task::GetCurrent() == m_parentTask" assertion failure occurs when you run a backup and restore command in Microsoft SQL Server 2005 SP3

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

When you run a backup and restore command in SQL Server 2005 Service Pack 3 (SP3), an "SOS_Task::GetCurrent() == m_parentTask" assertion failure occurs. Additionally, a mini-dump file is generated in the SQL Server log folder. Also, the following information is logged in the SQL Server error log:
SQL Server Assertion: File: <subpmgr.cpp>, line=<number> Failed Assertion = 'SOS_Task::GetCurrent() == m_parentTask'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.

Notes
  • This issue occurs when you set the network packet size to a value that is smaller than the default size of 4096 bytes. For example, you set the network packet size to 512 bytes.
  • This issue may occur when you run the EXECUTE master.dbo.xp_delete_file extended stored procedure to delete some specific backup files.


Resolution

Cumulative update information

SQL Server 2005 Service Pack 3 (SP3)

The fix for this issue was first released in Cumulative Update 11 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:
2258854 Cumulative update package 11 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. 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:
960598 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
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.

Status

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

References

For information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:

935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems


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:
913089
How to obtain the latest service pack for SQL Server 2005
For more information about new features and improvements in SQL Server 2005 Service Pack 3, visit the following Microsoft website:
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:
822499
New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684
Description of the standard terminology that is used to describe Microsoft software updates
Свойства

Номер статьи: 2297203 — последний просмотр: 17 авг. 2010 г. — редакция: 1

Отзывы и предложения