Microsoft KB Archive/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 =

Article ID: 932555

Article Last Modified on 11/20/2007

-

APPLIES TO


 * 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 Edition
 * Microsoft SQL Server 2005 Enterprise X64 Edition
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Developer Edition

-



BUG #: 50000492 (SQL Hotfix)



Important This article applies to SQL Server 2005 Service Pack 1 build 2047. For later builds of SQL Server 2005 Service Pack 1, see 931593.



SYMPTOMS
When you run a Microsoft SQL Server Integration Services (SSIS) package that contains a Visual Studio for Applications (VSA) script task or a script component in Microsoft SQL Server 2005, the script task or the script component may not run correctly or may not work as expected at design time.

Additionally, new or existing scripts in an SSIS package may not start correctly or run correctly. Additionally, the scripts may shut down unexpectedly.

When this problem occurs, you may receive one or more of the following error messages:

Error message 1
The task is configured to pre-compile the script, but binary code is not found. Please visit the IDE in Script Task Editor by clicking Design Script button to cause binary code to be generated.

Error message 2
The script component is configured to pre-compile the script, but binary code is not found. Please visit the IDE in Script Component Editor by clicking Design Script button to cause binary code to be generated.

Error message 3
The task cannot execute in 64-bit environment because the script is not pre-compiled. Please turn on the option to pre-compile the script in the task editor.



CAUSE
This problem occurs because of a recent change in the common language runtime (CLR) workstation runtime for builds of the Microsoft .NET Framework 2.0. The CLR workstation runtime is named Mscorwks.dll. The change introduces a compatibility problem for the Microsoft Visual Basic runtime engine that VSA uses. The Visual Basic runtime engine is named Vsavb7rt.dll. The problem prevents assemblies from being created correctly during the macro compilation operation. Because of this problem, existing packages that contain compiled scripts do not run.



RESOLUTION
Important This article applies to SQL Server 2005 Service Pack 1 build 2047. For later builds of SQL Server 2005 Service Pack 1, see 931593.

The following file is available for download from the Microsoft Download Center:

Download the hotfix package now.

Release Date: April 2, 2007

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to obtain Microsoft support files from online services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Prerequisites
You must have SQL Server 2005 Service Pack 1 (SP1) installed to apply this hotfix. For more information about how to obtain SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

913089 How to obtain the latest service pack for SQL Server 2005

Restart information
You may have to restart the computer after you apply this hotfix.

File information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

SQL Server 2005 Tools, Itanium architecture version


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
For more information about this problem, click the following article number to view the article in the Microsoft Knowledge Base:

931846 You may be unable to execute SQL Server 2005 Integration Services packages that contain script tasks or script components

Keywords: kbqfe kbpubtypekc atdownload kbexpertiseadvanced kbsql2005ssis KB932555

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.