August 11, 2015 at 2:19 pm
I have a job that runs an SSIS package. The job seems to be able to run through the package successfully, but at the end it errors out saying "The binary code for the script is not found. ...". The script referred to is at the beginning part (not the very first step) and should already be run.
The thing is, I can manually run this package on the server or visual studio without any problem. Also this job has been run on a regular basis without any issues on our old SQL 2008. I'm migrating this to Amazon Cloud SQL 2014.
Together with this package are other two very similar ones. They all work fine. I just can't figure out what can be wrong with this one.
Thanks for your input!
August 11, 2015 at 2:31 pm
Michelle-138172 (8/11/2015)
I have a job that runs an SSIS package. The job seems to be able to run through the package successfully, but at the end it errors out saying "The binary code for the script is not found. ...". The script referred to is at the beginning part (not the very first step) and should already be run.The thing is, I can manually run this package on the server or visual studio without any problem. Also this job has been run on a regular basis without any issues on our old SQL 2008. I'm migrating this to Amazon Cloud SQL 2014.
Together with this package are other two very similar ones. They all work fine. I just can't figure out what can be wrong with this one.
Thanks for your input!
Please stop posting the same question multiple times.
"The binary code for the script is not found. ..." errors can usually be solved by re-compiling the script task code and then saving without making any changes.
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
August 11, 2015 at 3:03 pm
Sorry about the repeated posts. Not sure where would be the best place to put it.
I tried everything possible, including recompiling. Nothing works.
The thing is, the job can run the whole package fine, including that script, but it just fails when it is supposed to end. It shouldn't be looking at that script again.
This package has been working for years on other servers. The only thing changed was the server name and file locations.
August 12, 2015 at 10:58 am
OK, I finally got this to work, thanks to jan.lausch
in this post: http://www.sqlservercentral.com/Forums/Topic1700561-2799-1.aspx
The problem is apparently a hidden broken reference which worked in 2008 but not in 2014.
I have another package that has an exact same task and is working. So I compared the two, the only difference was an extra line in my bad package:
using System.Drawing;
I took it out, then, it worked!
It still baffles me that why it would run successfully as a package on the server, but fail as a job even though the package still got executed successfully sometimes.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply