August 11, 2015 at 2:21 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:27 pm
Please stop posting the same question multiple times.
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 2:43 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!
Read what the error message says, "The binary code for the script is not found. ..." means your script task didn't compile! Further on Alvin's post, don't cross post, not in anybodies favour.
😎
August 11, 2015 at 2:49 pm
Eirikur Eiriksson (8/11/2015)
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!
Read what the error message says, "The binary code for the script is not found. ..." means your script task didn't compile! Further on Alvin's post, don't cross post, not in anybodies favour.
😎
I posted my answer in the other post.
This is what happens when there's multiples posts.
PLEASE CONSIDER THIS POST CLOSED
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 12, 2015 at 10:56 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 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply