Symptoms
You cannot transfer data from a table by using SQL Server Management Objects (SMO) in Microsoft SQL Server 2008 or Microsoft SQL Server 2008 R2. The issue typically occurs in the following scenarios:
-
You use the Transfer Database Task functionality in SQL Server Integration Services to copy data from a table.
Note You receive the following error message when the task does not run successfully:Error: 0xC002F325 at Transfer SQL Server Objects Task, Transfer SQL Server Objects Task: Execution failed with the following error: "Empty path name is not legal.".
-
You create an application that uses SMO in SQL Server 2008 or in SQL Server 2008 R2 to copy data from a table.
Cause
The issue occurs because of an error in the Microsoft.SqlServer.SmoExtended.dll assembly.
Resolution
Cumulative update information
SQL Server 2008 R2
The fix for this issue was first released in Cumulative Update 8. 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:
2534352 Cumulative Update package 8 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
For SQL Server 2008 Service Pack 1
The fix for this issue was first released in Cumulative Update 14 for Microsoft SQL Server 2008 Service Pack 1 (SP1). For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2527187 Cumulative Update 14 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. 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:
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.
For SQL Server 2008 Service Pack 2
The fix for this issue was first released in Cumulative Update 4 for Microsoft SQL Server 2008 Service Pack 2 (SP2). For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2527180 Cumulative Update 4 for SQL Server 2008 Service Pack 2Note 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 Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 2 hotfix to an installation of SQL Server 2008 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 "Applies to" section.
More Information
For more information about how to transfer data by using SQL Server 2008, visit the following Microsoft Developer Network (MSDN) website:
