SCript component Binary code code not found error always - SSIS2012

Question

SCript component Binary code code not found error always - SSIS2012

skjayapal

Old Hand

Points: 345
More actions
July 22, 2013 at 11:35 am

#296657

I have spent three days on this not able to find an anserr
Added script component transform open the edit script compiled ("No errors" saved and came out i ma getting binary code not found error always")

Viewing 10 posts - 1 through 9 (of 9 total)

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

Koen Verbeeck SSC Guru Points: 259115 More actions · Answer 1

When in the script editor, try to build the script and see if an error pops up.

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

skjayapal Old Hand Points: 345 More actions · Answer 2

I build the script component and there was no error or warnings.

Then closed it and clicked ok in the script component. Still i get this error.

Koen Verbeeck SSC Guru Points: 259115 More actions · Answer 3

What if you recreate the script and add lines of code piece by piece?

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

skjayapal Old Hand Points: 345 More actions · Answer 4

Without adding any code compiling it and coming out its giving error.

Koen Verbeeck SSC Guru Points: 259115 More actions · Answer 5

OK, what if you add a simple line of code, for example declaring a variable. Still got the error?

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

skjayapal Old Hand Points: 345 More actions · Answer 6

On compilation of the code its not giving error or warning in VSTA. But it gives the error binary code not found on dataflow.

skjayapal Old Hand Points: 345 More actions · Answer 7

On compilation of the code its not giving error or warning in VSTA. But it gives the error binary code not found on dataflow.

Phil Parkin SSC Guru Points: 246988 More actions · Answer 8

skjayapal (7/22/2013)
I build the script component and there was no error or warnings.
Then closed it and clicked ok in the script component. Still i get this error.

Are you saying that you get the error on clicking OK in design mode? So the error appears without even executing the package?

It's starting to sound like you may have a problematic installation. Can you try the same thing on another machine?

The absence of evidence is not evidence of absence.
Martin Rees

You can lead a horse to water, but a pencil must be lead.
Stan Laurel

gward 98556 Mr or Mrs. 500 Points: 538 More actions · Answer 9

I think I had that error a while ago. I got the impression that somehow the .dtsx file had simply got corrupt. I started again with a fresh package, went through exactly the same steps and it worked perfectly that time. I suggest you stop trying to fix the old one, it is not worth spending days on it if it's some weird corruption that the normal interface cannot fix because it is not expecting it. If you have a backup of the package from before it got corrupt then use that as a starting point. If not and you have done a lot of work already you may be able to copy the other tasks from the original package to the new package to prevent you having to do it all again. If you simply don't want to lose the original script you might be able to open the .dtsx file in Notepad, then find and copy the text of the original script out of it.