SSIS 2005 Script Task - Binary Code for the script not found.

Question

SSIS 2005 Script Task - Binary Code for the script not found.

adicunningham

SSC Veteran

Points: 219
More actions
September 8, 2010 at 8:51 am

#240102

Hi,
I have an SSIS package developed for SQL Server 2005 which has a script task that references a custom assembly which allows me call a WCF Service. This works fine in SQL Server 2005 (dev and production).
However, when I deploy this same package and assembly to SSIS 2008 I get the following error when I run the package:
The binary code for the script is not found. Please open the script in the designer by clicking Edit Script button and make sure it builds successfully.
I can however run the package via VS2005 on a machine with SQL Server 2008 installed and it works perfectly fine, just not when deployed.
My deployment of the package is as follows:
- Install custom assembly to the GAC
- Copy custom assembly to Microsoft.NET\Framework\v2.xxx folder
- Update DTExec.config with WCF configuration.
As I mentioned this package and deployment works fine on SQL Server 2005 but not on 2008. I need to 2005 package to run on 2008 as much of SQL Servers we use are being upgraded....but not all.
Any help would be appreciated.
Regards,
Adrian.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Todd McDermid Default port Points: 1416 More actions · Answer 1

Is this 2008 server the same bitness as your 2005 servers?

If your 2008 server is 64-bit, the precompile option must be set ON for it to execute - see the "Optimization" section here.

Todd McDermid - SQL Server MVP, MCTS (SQL 08 BI), MCSD.Net
My Blog - Dimension Merge SCD Component for SSIS - SSIS Community Tasks and Components

adicunningham SSC Veteran Points: 219 More actions · Answer 2

Hi,

Yes, the SQL Server 2008 instance is the same bitness. I've also, tried rebuilding the package with PreCompile ON and OFF, but so far nothing i have tried will work.

Adrian.

adicunningham SSC Veteran Points: 219 More actions · Answer 3

From what I can tell this problem is being caused by the System.ServiceModel.dll. In the 2005 package I manually edited the code to add the reference to the ServiceModel dll as follows:

<Reference

Name = "System.ServiceModel"

AssemblyName = "System.ServiceModel"

/>

This allowed the SSIS packaged to pick up the WCF DLL from the GAC and run when deployed. However, if I remove this reference, leave in my custom reference and comment out calls to WCF and deploy to SQL Server 2008 the "Binary Script not found" error goes away, but obviously the task doesn't work.