August 28, 2008 at 6:57 am
I found a couple of Connect articles on this that were closed with no real resolution. The one that really gets me is Buck Woodys' comments in this one:
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=315076
Reading his response, the first paragraph states that only SSMS 2005 can connect to a SSIS 2005 service. Yet the second paragraph contradicts that, saying SSMS 2008 can connect and manage SSIS packages in both 2005 and 2008 databases (msdb). In order to do that, you need to connect to the service and that is the contradiction. I have a few 2005 servers with packages in msdb and can't use SSMS 2008 :w00t:
In any case, I can’t find a workaround so I need some help. We have converted our desktops (the DBAs) to 2008, so I had to reinstall the 2005 client tools to export packages so they could be edited.
MG
"There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies."
Tony Hoare
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
September 4, 2008 at 2:51 pm
We are having the same issue here. When trying to connect to a SQL 2005 SSIS instance via SQL 2008 SSMS, the following error occurs. I have not been able to find any resolution for this:
TITLE: Connect to Server
------------------------------
Cannot connect to .
------------------------------
ADDITIONAL INFORMATION:
Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
------------------------------
Connect to SSIS Service on machine " " failed:
Class not registered
.
------------------------------
Connect to SSIS Service on machine " " failed:
Class not registered
.
------------------------------
BUTTONS:
OK
------------------------------
September 4, 2008 at 2:58 pm
Sorry - I meant to post this when I got it:
From Buck Woody:
No, the SSIS team has a different connection method that doesn’t allow us to connect with SSMS. I apologize if my Connect response was misleading. Sometimes when we try to explain an issue we make it a little less clear
So you can't connect to SSIS 2008 from SSMS 2005. You will need to maintain both SSMS 2005 and 2008
MG
"There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies."
Tony Hoare
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
September 11, 2008 at 5:01 pm
So, I'm still unclear on this. We've determined that you can't connect to 2008 SSIS from 2005 SMS (not a big surprise) but can you connect to 2005 SSIS from 2008 SMS?
According to Buck Woody as noted above:
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.
However, I still get the error....
September 18, 2008 at 7:05 am
SSMS 2005 can NOT connect to SSIS 2008
SSMS 2008 can NOT connect to SSIS 2005
Thus the need to maintain both sets of client tools
MG
"There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies."
Tony Hoare
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
September 18, 2008 at 6:58 pm
Thanks for the clarification - sometimes it's better to just say what you mean instead of explain what you mean 😉
I had come to this conclusion after having converted about 6 different SSIS packages and loading them up in VS2008 sp1, only to have to revert to VS2005 and SSMS 2005 again until Microsoft gets this worked out. It really seems like the internal departments at Microsoft don't communicate well or, at least, don't coordinate feature support.
April 13, 2009 at 1:57 pm
Looks like this problem has been reopened this year. I had hoped this would be fixed with the SSMS update in SP1, but no such luck...
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=412929
Thanks,
Jeff M. Belina
Sr. Database Developer/DBA
July 9, 2009 at 7:47 am
WHEN MICROSOFT WHEN!!!:w00t: In my mind this was a huge mistake due to the efforts we all must now face with regards to reverting back to SSIS2005. I say we complete a charge back form and sent it right back to Microsoft
July 9, 2009 at 7:48 am
WHEN MICROSOFT WHEN!!!:w00t: In my mind this was a huge mistake due to the efforts we all must now face with regards to reverting back to SSIS2005. I say we complete a charge back form and sent it right back to Microsoft
July 9, 2009 at 7:48 am
WHEN MICROSOFT WHEN!!!:w00t: In my mind this was a huge mistake due to the efforts we all must now face with regards to reverting back to SSIS2005. I say we complete a charge back form and sent it right back to Microsoft
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply