SSIS 2017 Upgrade issue
Clash Royale CLAN TAG#URR8PPP
SSIS 2017 Upgrade issue
We are upadating the packages(packages are in package deployment model) from SSIS 2012 to SSIS 2017. There are lots of script components in all the packages. When we are upgrading the packages we are having an error
Description: CS0234 - The type or namespace name 'Dts' does not exist in the namespace 'Microsoft.SqlServer' (are you missing an assembly reference?), ScriptMain.cs, 14, 26 End Error
Configurations:
SQLserver 2017
Visual studio enterprise 2015 + SSDT 2015
We have tried different options of deleting and re-adding the assemble file in the script component. Looks like the Microsoft.Sqlserver.ManagedDts assemble file is having issues for 2017 version. When we upgrade the packages to SSIS 2016 the packages work fine.
When we try to run the SSIS 2016 packages from Sqlserver agent job in SQLSERVER 2017 it is trying to upgrade the packages to 2017 and throw up the similar error as above.
Any solutions would be appreciated.
2 Answers
2
We have a mix of straight SSIS and BIML generated packages all suffering the same issues. Again, struggling for answers
We did find a workaround, but it's far from ideal :
Now if you open the package you can build/Execute your package
I've asked the question on MSDN too, maybe you can give it a bump ;) social.msdn.microsoft.com/Forums/en-US/…
– Paul Simkin
May 1 at 11:08
I'd forgotten about this post, but just for some extra info Varigence supplied us with a pre-release of the next cut of the BIML language (around 2018-05-25) and our issues (at least the automated package build ones) had gone away
By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.
Thanks for the reply, Yes the above solution is solving the issue but as you have mentioned it's far from the ideal solution as we have hundreds of script components in our packages. We have received a similar solution from Microsoft forums but hopefully they solve this issue via an update to the SSDT.
– user3255656
Apr 30 at 13:53