Microsoft KB Archive/938608

= You receive an error message after you install SQL Server 2005 Service Pack 2 when you try to edit a Script component that is inside an SSIS package and the SSIS package was created in an earlier version of SQL Server 2005 =

Article ID: 938608

Article Last Modified on 11/20/2007

-

APPLIES TO


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

-



SYMPTOMS
Consider the following scenario. You install Microsoft SQL Server 2005 Service Pack 2 (SP2). You open a SQL Server Integration Services (SSIS) package in SQL Server Business Intelligence Development Studio. The SSIS package was created in an earlier version of SQL Server 2005. When you try to use Microsoft Visual Studio for Applications (VSA) to edit a Script component that is inside the SSIS package, you receive the following error message:

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

--

For help, click: 

=
====================== --

Program Location:

at Microsoft.VisualBasic.Vsa.VsaItems.CreateItem(String Name, VsaItemType ItemType, VsaItemFlag ItemFlag)

at Microsoft.SqlServer.Dts.Pipeline.ScriptDesignTime.CreateDesignTimeEngine(String projectName, Boolean loadSource, ICodeGenerator codeGenerator)

at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ShowIDE

at Microsoft.DataTransformationServices.DataFlowUI.ScriptUI.propPage_DesignScript(Object sender, EventArgs args)

Additionally, you receive this error message only at design time. You can still perform the following actions:
 * You can successfully create new Script components in the data flow of the SSIS package. You can correctly edit these objects in VSA.
 * You can run the SSIS package.
 * In the control flow of the SSIS package, you can edit Script tasks that were created in earlier versions of SQL Server 2005.
 * You can successfully create new Script tasks in the control flow of the SSIS package.



CAUSE
This problem occurs because of a design change in SQL Server 2005 SP2. The Microsoft .NET Framework assembly Microsoft.SqlServer.DTSRuntimeWrap.dll was moved from the %WINDIR%\assembly\GAC_MSIL folder to the following folder:

%WINDIR%\assembly\GAC_

Note VSA requires the Microsoft.SqlServer.DTSRuntimeWrap.dll assembly.

VSA may find this assembly in the %WINDIR%\assembly\GAC_MSIL folder if an SSIS component requires the earlier version of the Microsoft.SqlServer.DTSRuntimeWrap.dll file.



RESOLUTION
To resolve this problem, follow these steps:
 * 1) Find the following files in the %WINDIR%\Microsoft.NET\Framework\v2.0.50727 folder:
 * 2) * Microsoft.SqlServer.DTSRuntimeWrap.dll
 * 3) * Microsoft.SqlServer.DTSPipelineWrap.dll
 * 4) * Microsoft.SqlServer.ManagedDTS.dll
 * 5) * Microsoft.SqlServer.PipelineHost.dll
 * 6) If you find the files, delete these files or move the files to a backup location.

After you delete these files, VSA will reference these files from the %WINDIR%\assembly\GAC_ folder.

Note We recommend that you use Windows Explorer instead of a command prompt to delete the files or move the files.



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
When you install SQL Server 2005 SP2, the installation process may not remove the DLLs that are mentioned in the &quot;Resolution&quot; section from the %WINDIR%\assembly\GAC_MSIL folder. This behavior occurs if these files are being used. Additionally, these files may exist in the %WINDIR%\Microsoft.NET\Framework\v2.0.50727 folder if one of the following conditions is true:
 * You installed a beta version of SQL Server 2005 on that computer.
 * You manually copied these files to the folder.

The presence of these files can cause the same symptoms that are mentioned in the &quot;Symptoms&quot; section. In the release version of SQL Server 2005 or in later versions of SQL Server 2005, these files will not be copied to the %WINDIR%\Microsoft.NET\Framework\v2.0.50727 folder.

