Can't connect to SSIS 2005 from SSMS CTP5 - by Ayad Shammout2

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<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 315076 Comments
Status Closed Workarounds
Type Bug Repros 5
Opened 12/4/2007 10:14:49 AM
Duplicates 354931 Access Restriction Public


In SSMS CTP5, I can't connect to SSIS 2005. I'm getting the following error:

Connect to SSIS Service on machine "ServerA" failed:
 Class not registered
Sign in to post a comment.
Posted by Anbu Varadhan on 11/2/2009 at 4:03 AM
I am getting the same issue after reinstalling the SQL Server 2008 developer edition. This was working till i install the VS2008 SP1. After installing that i am getting the following error message, when i Open the SQL Editor.

TITLE: Microsoft SQL Server Management Studio

Error connecting to 'PC1\ADLIB'.


Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorCore)

For help, click:


Microsoft.SqlServer.Smo.UnSafeInternals.ManagementUtil.EnterMonitor(System.Object) (Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorCore)



Posted by TryingtoFigureOutSomething on 9/16/2009 at 11:50 AM
This seems to go against the paradigm for Microsoft tools. I should be able to connect to older versions with new tools just not the other way around. This is almost as crazy as removing the ability to administer reports from SSMS 2008.
Posted by Dwaine Wright on 7/21/2009 at 1:14 PM
Buck, even if it IS a large coding task, it is becoming increasingly painful to follow (let alone justify following) the MS upgrade path and pace if MS itself can't keep up (or is not willing to) with toolsets that handle all active versions. It's only one version back! It was much more painful from 2000 to 2005, but this is still a white elephant in the corner being protected by a 500 Lb Gorilla. Closing the issue doesn't "close the issue".
Posted by test1212 on 4/21/2009 at 6:57 AM
Buck, I would like to request that you reopen this issue - it seems unaccepptable to require the use of the old SQL2005 client tools just for this lone task. Is it a large coding task to accomodate both versions of SSIS or just something that no one thought would be needed?

Posted by test1212 on 2/13/2009 at 5:35 AM
Correct, the point was that we had to use SSMS 2005 instead of SSMS 2008. Try connecting wtih SSMS 2008 and you will get a failure.

Posted by test1212 on 9/19/2008 at 9:54 AM
Buck, our organization will be moving to SQL2008 in phases and we will have to support SSIS 2005 and 2008 simultaneously for some time as we have vender products that rely on both versions. With this current functionality, we will have to mantain both versions of Management Studio across our organization and we would greatly prefer only having to support one version if possible. Could you look into reopening this issue for those of us that have to support both versions of SSIS?

Posted by Microsoft on 3/12/2008 at 4:00 PM
Thanks for providing feedback.
We understand you're trying to connect to the 2005 IS service from SSMS 2008 CTP5. We support connections to 2005 IS service from SSMS 2005 only.

We don't however limit access to SSIS packages residing in SQL Server 2005 databases (msdb). SSMS 2008 can connect and manage SSIS packages in both SQL Server 2005 and 2008 databases.

We apologize for the inconvenience.
Posted by Microsoft on 12/7/2007 at 9:48 AM
OK - thanks for the feedback. I'll assign this to a developer.

Buck Woody, SQL Server Program Manager
Posted by Ayad Shammout2 on 12/6/2007 at 9:31 AM
Yes, we tried it from 3 different machines. If I use SSMS 2005, I can connect ok.
Posted by Ayad Shammout2 on 12/6/2007 at 9:30 AM
Yes, we tried it from 3 different machines. If I use SSMS 2005, I can connect ok.
Posted by Microsoft on 12/6/2007 at 9:19 AM
Hello Ayad -

I can't repro this here. Have you tied it on another machine?

Buck Woody, Program Manager