Home Forums Data Warehousing Integration Services IS 2008 Triggering an Excel Macro via Script Task - The Binary Code for the script is not found RE: IS 2008 Triggering an Excel Macro via Script Task - The Binary Code for the script is not found

  • February 28, 2013 at 7:28 am

    #1591976

    Debbie Edwards (2/28/2013)

    Elliott Whitlow (2/27/2013)

    I think the missing binary code is your clue. It often (usually?) means that there was a build error in your script. Open the script and check the error list. do a built explicitly and see what the output was.

    CEWII

    Somethings missing for definite but if I run it from Excel its fine. And when I run through IS thats the only error message I get. IIm not sure what you mean by build expicitly? Im guessing that means just running it via Integration services, through the script task?

    Sounds like you are trying to automate Excel from SSIS. You should know up front that Microsoft does not support this type of call from unattended server processes.

    You cannot call exactly the same script in SSIS as you developed inside Excel, unfortunately. The contexts in which the scripts run are different.

    Here is a link that may get you started.

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.