Article ID: 2478032 - Last Review: March 21, 2011 - Revision: 3.0

FIX: 0xC002F325 error when you run two SSIS 2008 packages at the same time in SQL Server 2008 Integration Services or in SQL Server 2008 R2 Integration Services

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
Microsoft distributes Microsoft SQL Server 2008 and Microsoft SQL Server 2008 R2 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 2008 or SQL Server 2008 R2 fix release.

On This Page

Expand all | Collapse all

SYMPTOMS

Consider the following scenario:
  • You install Microsoft SQL Server 2008 Integration Services (SSIS 2008) or Microsoft SQL Server 2008 R2 Integration Services (SSIS 2008 R2) on a computer.
  • You create two SSIS 2008 packages by using Microsoft Business Intelligence Development Studio (BIDS).
  • You add a Transfer SQL Server Object Task control to each package.
  • You run these two SSIS 2008 packages at the same time. For example, you run SQL Server Agent jobs that run these two SSIS 2008 packages at the same time.
In this scenario, one of the two packages may fail to run. Additionally, you receive the following error message:
Code: 0xC002F325 Source: Transfer SQL Server Objects Task Transfer SQL Server Objects Task Description: Execution failed with the following error: "The process cannot access the file 'drive:\Windows\system32\config\systemprofile\AppData\Local\Microsoft\SQL Server\Smo\TransferMetadata1812601901.xml' because it is being used by another process.".

Back to the top

CAUSE

This issue occurs because SQL Server Management Objects (SMO) incorrectly generates temporary files that have the same names for the concurrent jobs. Additionally, the Transfer SQL Server Object Task control uses SMO for transfer operations in the database.
Back to the top

RESOLUTION

Cumulative update information

SQL Server 2008 Service Pack 2

The fix for this issue was first released in Cumulative Update 3 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:
2498535  (http://support.microsoft.com/kb/2498535/LN/ ) Cumulative update package 3 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. 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:
2402659  (http://support.microsoft.com/kb/2402659/LN/ ) 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.

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 6. 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:
2489376  (http://support.microsoft.com/kb/2489376/ ) Cumulative Update package 6 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  (http://support.microsoft.com/kb/981356/ ) The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

The fix for this issue was first released in Cumulative Update 12 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:
2467236  (http://support.microsoft.com/kb/2467236/LN/ ) Cumulative update package 12 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  (http://support.microsoft.com/kb/970365/LN/ ) 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.
Back to the top

WORKAROUND

To work around this issue, run the SSIS packages at different times.
Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top
APPLIES TO
  • Microsoft SQL Server 2008 Integration Services
Back to the top
Keywords: 
kbqfe kbfix kbexpertiseadvanced kbsurveynew KB2478032
Back to the top