Hi all,
I have a package with a number of script components. All are set "PreCompile=True".
Within a Sequence Container I have a set of five script tasks each followed by an Execute Process Task. Each pair is linked but the five pairs are independent (hope this makes sense).
The first pair executed successfully but the other four all failed with the "Script files failed to load" error.
Anyone have a clue why this might happen or what I might change to solve the problem?
The package is scheduled under SS Agent so I'm currently thinking of taking these steps out of SSIS and putting them into the job. Not ideal but at least I can have some confidence that it will work.
Any suggestions would be very welcome.
Cheers,
Andrew
Go into the script tasks, click "Design Script...", when VBA opens close it down again.
This will *hopefully* recompile the binary code and the problem *should* go away.
If not, there may be something else going on here.
-Jamie
|||Hmmm,
Thanks for the suggestion. I'll give it a try but I suspect it may be a "something else". If I copy the dtsx package to another machine and run it through dtexec the problem doesn't occur.
It's probably more of a concern if this does work as it suggests that within a package there's no guarantee that a given script component is compiled when the package is deployed.
Andrew
|||Did you ever get a resolution to this problem?
I am having a similiar issue. I am executing several SSIS packages from within a SSIS package Script file (PreCompileScriptIntoBinaryCode=True) based on package names in a table.
What makes my problem similiar is, it is always the 3rd package called that fails with this error. These packages also have Script files (PreCompileScriptIntoBinaryCode=True).
This happens not only when called from Sql Server Agent, but also when run from within BIDS.
|||Anyone figure this out? My script task is failing only when run under SQL Server Agent as a scheduled job.|||I don't have a resolution but it hasn't happened lately.
Sorry not to be more helpful.
I'm not sure what's going to happen when the package needs changing.
Andrew
|||In my case, it seemed that I had a stop for debugging within my script. When the package was running on the server it was failing with this error message, no problems when running on the client. So check you don't have any breaks within your script and it may do the trick!.
Panos.
|||For what it's worth, I had the exact problem. Only failing under Sql Agent with "Script files failed to load".
I took Jamie's advice above, opened my script tasks and I clicked save. Redeployed the package and it worked.
I am running on 64-bit itaniums w/sp1. Also, I am running the job under the 'sa' account.
|||I had the same problem and followed Jamie suggestion. It worked!!
I had copied sever scripts to my package and had not opened and saved to auto-recompile.
Thanks Jamie!
No comments:
Post a Comment