For me this happened when I installed SSMS 2017 on my machine using VS 2010 to build SSIS packages for a SQL 2012 server. I believe the issue came out of some conflict caused by that installation. Good news is that once I repaired my SQL Server 2012 (management tools only) the issue went away. Hope that helps someone.