SQL 2014 SSIS upgrade from SQL 2012 leaves multiple instances - by Nick_Craver

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 811931 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 12/18/2013 1:50:21 PM
Access Restriction Public


After an upgrade from SQL 2012 SP1 CU4 to SQL 2014 CTP2 with features: SQLENGINE,FULLTEXT,IS leaves us with SQL Engine Upgraded, Full Text upgraded, and 2 instances of Integration Services, 11 and 12.  We have 2 services, MsDtsServer110 and MsDtsServer120.  Connecting to any of the upgraded servers for SSIS ends up at the old SQL 2012 version (11.0.3339 in our case), not 12.0.1300 as expected.

This creates several errors when editing and saving packages, mostly relating to version.  Importing/saving/editing all error our in many ways due to the conflict.

Stopping the MsDtsServer110 service will just have it restart on connect.  Disabling the service predictably yields an error that it cannot be started: "The service cannot be started , either because it is disabled or it has no enabled devices associated with it."  We have been unable to find how to connect to the SQL 2014 instance of SSIS on the box to manage our maintenance plans.
Sign in to post a comment.
Posted by Microsoft on 1/1/2014 at 10:48 PM
Thank you very much for your feedback.
This upgrade behavior is the same as previous versions of Integration Services and is as expected. When you upgrade to SQL Server 2014 Integration Services (SSIS) on a machine that has one of these earlier versions of Integration Services installed, SQL Server 2014 Integration Services (SSIS) is installed side-by-side with the earlier version. Please refer to the following MSDN page for more information: http://msdn.microsoft.com/en-us/library/cc879336(v=sql.120).aspx.