September 2, 2025 at 7:28 pm
Hi all, this is my first time posting on this forum, thank you all very much in advance.
I have a .dtsx package open in Visual Studio, and one of the Script Tasks are erroring with "The binary code for the script is not found. Please open the script in the designer by clicking Edit Script button and make sure it builds successfully." "... failed validation and returned validation status "VS_ISBROKEN"."
I tried to follow the instructions and open the script task and click Edit Script, where I was meet with a modal prompting me to Update to a later version of the .NET framework (see screenshot #1). Regardless on if I update the framework or click the X to ignore it, both open the script to a blank page, where it says the project was unloaded (screenshot #2). I've tried to "Reload Project" (screenshot #3) to which it prompts me again to Update the target. This time, you can briefly see the structure of the script task in the solution explorer, with the main.cs, BufferWrapper.cs, etc. being visible (screenshot #4). Although, no matter if I click to Update or the X to ignore, both return the screen to the previous screenshot, a blank script page.
If I can get some assistance on this, that would be greatly appreciated. I've looked this up extensively and tried random solutions I saw online, but none work. Reverting to a lower version number of SQL Server for the project did nothing, same error. It seems as though the Updating of the target is just not working every time.
Thank you.
September 3, 2025 at 8:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
September 5, 2025 at 4:15 pm
Sounds to me like you are using the wrong version of VS to work with that DTSX. I would try an older version of VS. I wouldn't try to upgrade anything to newer .NET (4.0 to 4.8 for example) as you may be using things not compatible in 4.8. I would also recommend you download .NET 4.0 and get it set up on your system prior to updating things. Get it running in current state and then work on upgrading to newer .NET.
Determine the VS version it was created in and use that to get it to build successfully. Once it builds successfully, THEN look at updating .NET from the older VS version and get it to build successfully. THEN migrate it to a newer VS.
I also recommend that at each successful step, you commit it to source control so you have a rollback plan if things go sideways. I would also revert all of your changes from the random solutions you saw online and get it back to a known good state before you try an older VS version as the changes you did MAY have made it incompatible with older VS.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply