Friday, June 15, 2012 4:19 PM
My problem is same as a previous post. I copy the description below, but the difference is I upgrade to window 7(from XP) and SQL server 2012(from 2008) at my local. Server is still SQL server 2008. All the previous solution is VS 2008 and upgraded using VS conversion wizard. Please advise.
Copy from previous post:
"I have a package with a number of Script Tasks. For some reason I am not able to edit any of the scripts.
For example, I do the following:
1) Right-click on a script task in the package and choose Edit. The Script Task Editor dialog appears.
2) I then select 'Script' from the left hand list (General, Script, Expressions) and click the 'Design Script...' button.
3) The Script Task Editor dialog disappears and nothing happens. The script editor window where I would edit the script doesn't appear.
Ordinarily the Script Task Editor stays up and the Script Editor appears but this isn't happening. Has anyone encountered this before? "
Friday, June 15, 2012 5:47 PM
I am not sure if I understand. But it sounds like the packages did not make it through the upgrade process to 2012. Or maybe you are trying to open them on a machine without SQL Server Data tools.
Tuesday, June 19, 2012 4:11 PM
I do have SQL Server Data tools under All Programs->MicroSoft SQL Server 2012. My question is after upgraded, I can not "edit script" of a script task in Visual Studio SSIS solution. In addition, when I drag and drop a new script task and edit the script task. Nothing show up in the pop-up window. It usually shows a text editor with default VB or C# start-up code.
Hope it is clear to you. Thanks,
Tuesday, June 19, 2012 10:21 PMModerator
what error you recieve when you want to edit script?
the usual problem is that Visual Studio cannot find appropriate VSTA to load for editing script, this link explained such problem and solution exactly:
- Marked As Answer by bzhang Wednesday, June 20, 2012 10:07 PM
Wednesday, June 20, 2012 10:07 PM
Thanks for providing the userful source. I did not get any error message but I will try the suggested solution. Probably the easiest way is re-install Visual Studio.