SSIS Error – The Binary code for the script is not found

Application team reported me that one of the SSIS package is failing after recent changes. It was failing with message “Binary Code for the script is not found”

I have been asked to troubleshoot the issue. I have opened the SSIS package in SQL Server Data tools and try to run the package from SSDT. Here is the error i have received


The package was using Script Task and i have opened the script tasks to see any coding/syntax errors. I found there was missing semicolon and un compiled code. I have modified the logic in Script task and save the package.

After that i have ran the package and it is successful.



Error “The Binary code for the script is not found” usually occurs when you use Script task in SSIS and save the task with errors. Edit the script task, correct the issues and then execute the package.

Hope you enjoyed the post!


Ramasankar Molleti

LinkedIn: LinkedIn Profile

Twitter: Twitter

About Ramasankar

My name is Ramasankar Molleti, I have been working on various database and cloud systems (SQL Server, Oracle, PostgreSQL, DynamoDB, Redshift, Amazon, Azure) over 12 years, primarily focusing on Architect , Development, Administration and Business intelligence. I hold various Certifications such as Amazon Web services Solution Architect Associate, Microsoft certifications (Microsoft Certified Information Technology Professional, Microsoft Certified Technology Specialist, and Microsoft Certified Solution Associate).
This entry was posted in SSIS. Bookmark the permalink.

2 Responses to SSIS Error – The Binary code for the script is not found

  1. Aman says:

    How did you modify the logic in Script task? Is this all about semi colon?

    • Ramasankar says:

      There was a syntax error in the script task. In this case semi colon, but in general if you do save the script task with errors you do get this type of error. That is the mistake from the TFS side, they Checked in the package in source control with syntax errors. My team deployed the same in server as a SQL Agent job. Hence, the failure of the package.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s