Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SCript component Binary code code not found error always - SSIS2012 Expand / Collapse
Author
Message
Posted Monday, July 22, 2013 11:35 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, August 28, 2013 1:25 PM
Points: 5, Visits: 17
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")
Post #1476166
Posted Monday, July 22, 2013 12:40 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Yesterday @ 12:52 PM
Points: 13,636, Visits: 11,509
When in the script editor, try to build the script and see if an error pops up.



How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1476211
Posted Monday, July 22, 2013 12:46 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, August 28, 2013 1:25 PM
Points: 5, Visits: 17
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.

Post #1476214
Posted Monday, July 22, 2013 12:49 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Yesterday @ 12:52 PM
Points: 13,636, Visits: 11,509
What if you recreate the script and add lines of code piece by piece?



How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1476217
Posted Monday, July 22, 2013 2:48 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, August 28, 2013 1:25 PM
Points: 5, Visits: 17
Without adding any code compiling it and coming out its giving error.
Post #1476277
Posted Monday, July 22, 2013 2:52 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Yesterday @ 12:52 PM
Points: 13,636, Visits: 11,509
OK, what if you add a simple line of code, for example declaring a variable. Still got the error?



How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1476280
Posted Monday, July 22, 2013 3:12 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, August 28, 2013 1:25 PM
Points: 5, Visits: 17
On compilation of the code its not giving error or warning in VSTA. But it gives the error binary code not found on dataflow.
Post #1476288
Posted Monday, July 22, 2013 5:03 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, August 28, 2013 1:25 PM
Points: 5, Visits: 17
On compilation of the code its not giving error or warning in VSTA. But it gives the error binary code not found on dataflow.
Post #1476309
Posted Monday, July 22, 2013 10:52 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 11:13 PM
Points: 5,316, Visits: 12,347
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?



Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

When you ask a question (and please do ask a question: "My T-SQL does not work" just doesn't cut it), please provide enough information for us to understand its context.

It is better to keep your mouth shut and appear stupid than to open it and remove all doubt. (Mark Twain)
Post #1476341
Posted Wednesday, July 24, 2013 4:06 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Yesterday @ 2:42 AM
Points: 11, Visits: 261
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.
Post #1476955
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse