Article ID: 928323 - View products that this article applies to.
Bug #: 447320 (SQLBUDT)
Bug #: 411552 (SQLBUDT)
Consider the following scenario:
This problem occurs because of the duplicate project names of the script tasks or the script components in Microsoft Visual Studio for Applications. After you copy and paste the .dtsx file, the script tasks or the script components in these two packages have the same GUID for the ID property. When you execute the parent SSIS package, SSIS may incorrectly execute one of the script tasks or the script components multiple times in duplicate. However, you expect that SSIS executes each script task or script component independently.
Note Visual Studio for Applications is used to design and compile the script tasks or the script components in SSIS.
Service pack informationTo resolve this problem, obtain the latest service pack for SQL Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/913089/ )How to obtain the latest service pack for SQL Server 2005
To work around this problem, follow these steps:
If the PreCompile property for the package that contains the problematic script task or the problematic script component is set to True, the script tasks or the script components are precompiled. In this case, you must recompile the script tasks or the script components. To do this, open the script designer, and then close the script designer. You may have to redefine the precedent constraints for the pasted script task or the pasted script component.
Similarly, to create a unique project name for the script tasks manually, click Design Script in the Script Transformation Editor dialog box, and then manually edit the Project Name property in Visual Studio for Applications.
Note You cannot create a unique project name for script components in the data flow.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Steps to reproduce the problem
For more information, visit the following Microsoft Web sites:
Article ID: 928323 - Last Review: September 17, 2011 - Revision: 2.0
Contact us for more help