Article ID: 931846 - Last Review: November 20, 2007 - Revision: 3.2 You may be unable to execute SQL Server 2005 Integration Services packages that contain script tasks or script componentsOn This PageSYMPTOMSIn Microsoft SQL Server 2005, you may be unable to execute SQL Server 2005 Integration Services (SSIS) packages that contain script tasks or script components. Additionally, the scripts may not function correctly when you try to edit the scripts. This issue may occur on computers that are running one of the following operating systems:
For example, this issue occurs if the following conditions are true:
When this problem occurs, you may experience the following symptoms:
CAUSEThis problem occurs because of a recent change in the common language runtime (CLR) workstation runtime (Mscorwks.dll) for builds of the Microsoft .NET Framework 2.0 later than 2.0.50727.832. The change introduces a binary-compatibility problem for the Microsoft Visual Basic runtime engine (Vsavb7rt.dll) that VSA and SSIS use. The problem prevents assemblies from generating correctly during the macro compilation operation. This problem causes existing packages that contain compiled scripts not to execute. Certain design-time operations of VSA are also affected. For example, the compiler may be unable to generate Common Intermediate Language (CIL) when you use VSA at design time. RESOLUTIONTo resolve this problem, use one of the following methods based on your need. Note The following methods describe hotfixes that you can apply on the computer that is running SSIS. Notice that each of these hotfixes provides the same functionality. The only difference is that each hotfix is packaged according a particular version of SQL Server 2005. Method 1Note We recommend that you use this method to resolve this problem.Install SQL Server 2005 Service Pack 2 (SP2). For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: 913089
(http://support.microsoft.com/kb/913089/
)
How to obtain the latest service pack for SQL Server 2005
Method 2Note Use this method if the following conditions are true:
932555
(http://support.microsoft.com/kb/932555/
)
FIX: A script task or a script component may not run correctly when you run an SSIS package in SQL Server 2005 build 2047
Method 3Note Use this method if the following conditions are true:
931593
(http://support.microsoft.com/kb/931593/
)
FIX: A script task or a script component may not run correctly when you run an SSIS package in SQL Server 2005 build 2153 and later builds
Method 4Note Use this method if the following conditions are true:
932556
(http://support.microsoft.com/kb/932556/
)
FIX: A script task or a script component may not run correctly when you run an SSIS package in SQL Server 2005 build 1500 and later builds
Method 5Note Use this method if the following conditions are true:
932557
(http://support.microsoft.com/kb/932557/
)
FIX: A script task or a script component may not run correctly when you run an SSIS package in SQL Server 2005 build 1399
After you use any of these methods, you may continue to experience any of the problems that are described in the following Microsoft Knowledge Base article: 928208
(http://support.microsoft.com/kb/928208/
)
FIX: Custom applications that use the Visual Studio for Applications Visual Basic Runtime may be unable to compile macros or to run macros
In this case, apply the hotfix that is described in Microsoft Knowledge Base article 928208 if the version of the .NET Framework 2.0 is earlier than build 2.0.50727.832.STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONSome cases may occur on different operating systems and hardware platforms after the .NET Framework 2.0 hotfixes are installed. The following are descriptions of these cases together with information about how the hotfixes that are described here will ease any potential problems. Description 1All computers that meet the following specifications continue to operate without being affected:
Description 2Any SSIS package that does not contain a script task or a script component is executed correctly.Description 3Any SSIS package that does contain a script task or a script component continues to execute correctly if you have chosen not to precompile the code.Note This scenario is impossible on 64-bit platforms. On 64-bit platforms, there is no compiler tool to compile the code on a JIT basis. Description 4By default, the .NET Framework 2.0 hotfixes are installed together with the operating system on any computer that is running Windows Vista. You can resolve this issue by installing the hotfixes that are mentioned in this article.Description 5On 64-bit platforms, any SSIS package that contains a script task or a script component cannot be executed. You can resolve this issue by installing the hotfixes that are mentioned in this article. The only workaround is to manually recompile all scripts on a computer that has the .NET Framework 2.0 hotfixes installed. This procedure guarantees that the CIL code is both generated and consumed by the same version of the VSA. Therefore, there is no binary incompatibility.Description 6On all computers that are running a Windows operating system other than Windows Vista, the SSIS infrastructure tries to recompile a script that is not executed. This is true even if the .NET Framework 2.0 hotfixes are not installed. In most cases, the SSIS package continues to run without manual intervention. You may notice a very small decrease in performance because of the overhead of recompilation. The decrease is less than 1 percent. When the SSIS hotfix or SQL Server 2005 SP2 is installed, the package follows an additional step in resolving the binary incompatibility if there is a continued failure to execute the CIL code. However, the package log file and the console may contain one of the following warning messages or one of the following error messages about the failure.Warning message 1Warning message 2Warning message 3Error message 1Script could not be recompiled or run: {0}. For more information, see the Microsoft Knowledge Base article, KB931846 (http://go.microsoft.com/fwlink/?LinkId=81885) Error message 2Precompiled script failed to load. The computer that is running the Script Component does not have a compiler capable of recompiling the script. To recompile the script, see the Microsoft Knowledge Base article, KB931846 (http://go.microsoft.com/fwlink/?LinkId=81885) Error message 3Precompiled script failed to load. The computer that is running the Script Task does not have a compiler capable of recompiling the script. To recompile the script, see the Microsoft Knowledge Base article, KB931846 (http://go.microsoft.com/fwlink/?LinkId=81885) Overview of the interaction between SSIS and VSASSIS lets developers use multiple script tasks and script transforms in SSIS packages to enable custom workflow and transformation logic. The underlying technology that is used in these components is VSA. When a developer uses a script at design time, the VSA IDE starts, and the developer can program custom Visual Basic 2005 code. When the IDE is closed, the Visual Basic code is automatically precompiled to the CIL code format.Note CIL was previously known as Microsoft intermediate language (MSIL). Both the Visual Basic source code and the CIL code are saved in the package structure together with the other package details. When the package is executed, either during debugging or in deployed scenarios, any CIL code that is in the package is sent to the VSA engine and then executed. Note This interaction is transparent. Typically, you would not be aware of this protocol. You can also decide not to precompile the CIL code on a per-script basis. In this case, the Visual Basic source code is saved only in the package and is not saved in the CIL code. At run time, VSA dynamically compiles any source code that was not saved in the CIL code. Then, VSA executes the ensuing CIL code by using the method that was described earlier. However, certain compilation components of VSA have never been supported on 64-bit computers. Therefore, the automatic compilation step fails in those 64-bit deployments. The only way to work around this problem is to make sure that you always precompile scripts that are intended for 64-bit deployments. For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base: 822499
(http://support.microsoft.com/kb/822499/
)
New naming schema for Microsoft SQL Server software update packages
For more information about the terminology that Microsoft uses when it corrects software after the software is released, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
APPLIES TO
| Article Translations
|
| United States | Change | | | All Microsoft Sites |
Back to the top
|
