March 24, 2016 at 7:57 am
I'm trying to upgrade a SSIS 2008 package to SSIS 2012. In Data Tools, the package has a big red X on the script task, complains about not having the binary code for it, and when I try to rebuild the script finally errors out with the message "Unable to open module file 'C:\Users\UserName\AppData\Local\Temp\Vsta\SSIS_ST110\Vstald5fsQhaF0OZ6cf52jW4dQ\Vsta6sw0__qQr1E__yeLUPbzRyzA\VariableSupport.vb'"
When I open the package in BIDS (the pre-updated version), there are no errors. I open the script task and see VariableSupport.vb on the right, underneath the script task with a small yellow warning on it, but there are no errors in the error list. Only the warning "The referenced component 'Microsoft.SqlServer.ManagedDTS' could not be found."
When I click the VariableSupport.vb and hit "open," I get the error "The item 'VariableSupport.vb' does not exist in the project directory. It may have been moved, renamed or deleted."
The Dev I've asked for help is not quite listening to the problem. He said he could open the script task fine but didn't actually look for any errors or warnings. So now I'm posting here. Does anyone know how to fix this problem?
March 24, 2016 at 8:24 am
On 64-bit Operating System, you can find the file Microsoft.SQLServer.ManagedDTS.dll in the following path:
C:\Program Files (x86)\Microsoft SQL Server\110\SDK\Assemblies
On 32-bit Operating System, you can find the file Microsoft.SQLServer.ManagedDTS.dll in the following path:
C:\Program Files\Microsoft SQL Server\110\SDK\Assemblies
I had a similar problem and had to update the references and change the target framework version to .net 4 to get it to work.
March 24, 2016 at 8:29 am
PB_BI (3/24/2016)
On 64-bit Operating System, you can find the file Microsoft.SQLServer.ManagedDTS.dll in the following path:C:\Program Files (x86)\Microsoft SQL Server\110\SDK\Assemblies
On 32-bit Operating System, you can find the file Microsoft.SQLServer.ManagedDTS.dll in the following path:
C:\Program Files\Microsoft SQL Server\110\SDK\Assemblies
I had a similar problem and had to update the references and change the target framework version to .net 4 to get it to work.
Thanks. I found an article on that shortly after posting, and updated the reference in BIDS. But it didn't resolve my inability to build the Script Task.
I'm thinking at this point the only way to fix it is to find someone in the office who has a copy of the .vb file and can copy it for me to add to my machine and re-add to TFS.
At least, I hope that works. If no one else has a copy of the file... I'm at a loss as to what I can do to fix the problem.
March 24, 2016 at 8:30 am
Hrm... If I delete the .vb reference in the Script Task, will it rebuild when I rebuild the task itself?
Or am I just asking for a world of trouble if I do that?
March 24, 2016 at 8:37 am
Brandie Tarvin (3/24/2016)
Hrm... If I delete the .vb reference in the Script Task, will it rebuild when I rebuild the task itself?Or am I just asking for a world of trouble if I do that?
To be honest I don't know. If it isn't finding the reference anyway then removing it will most probably be moot. Just create a copy of the package and try it there.
Have you tried just copying the code out of the task and putting it in a new one?
March 24, 2016 at 8:46 am
PB_BI (3/24/2016)
Brandie Tarvin (3/24/2016)
Hrm... If I delete the .vb reference in the Script Task, will it rebuild when I rebuild the task itself?Or am I just asking for a world of trouble if I do that?
To be honest I don't know. If it isn't finding the reference anyway then removing it will most probably be moot. Just create a copy of the package and try it there.
Probably safest.
Have you tried just copying the code out of the task and putting it in a new one?
I have not. And now I will. Thank you for the suggestion.
March 24, 2016 at 11:24 am
Brandie Tarvin (3/24/2016)
PB_BI (3/24/2016)
Have you tried just copying the code out of the task and putting it in a new one?
I have not. And now I will. Thank you for the suggestion.
HA. That appears to have done the trick. Thanks.
March 24, 2016 at 12:15 pm
Brandie Tarvin (3/24/2016)
Brandie Tarvin (3/24/2016)
PB_BI (3/24/2016)
Have you tried just copying the code out of the task and putting it in a new one?
I have not. And now I will. Thank you for the suggestion.
HA. That appears to have done the trick. Thanks.
The SSIS upgrade wizard in all it's glory! Glad I could help.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy