Hi there,I am encountring a weird problem.I had SQL SERVER 2005dev(Server) on my system and SSIS used to work fine. Now i also installed SQL SERVER 2008 dev (server) on it. And since than my SSIS 2005 editor is behaving quite erraticaly:1) I cant drag few tasks in control flow (DFT, Sequence container, Execute package) and rest of them are coming through.2) when i open Script editor of Script task, itneither opennorthrow any msg3) where as if I open Script editor of Script component( DFT) it throw an error "Cannot show visual editor for Application editorThe method or operation is not implemented (Microsoft.DataWareHouse.vIntergration)there can be many more such weird things but so far i have seen only theseI am running Windos XP sp2 and SSIS 2008 is working finethanks!! Rahul Kumar, MCTS, India, http://sqlserversolutions.blogspot.com/

WOW I checked in couple of machines here and its the same problem... Rahul Kumar, MCTS, India, http://sqlserversolutions.blogspot.com/

Anyone having sql server 2005 and sql servr 2008 on same box.... Is your SSIS 2005 working fine?????Rahul Kumar, MCTS, India, http://sqlserversolutions.blogspot.com/

a microsoft employee told me that it is possible for sql server 2005 and 2008 to peacefully co-exist in the same OS, but i haven't been able to do it.Duane Douglas, MCAD | http://www.ssisbi.com | Please mark the post(s) that answered your question.

There is no problem installing SQL-Server 2005 and 2008 on the same box. However, one of these must be at last a named instance because you cannot have unnamed (or default) instances of SQL-Server on the same box.http://effulgentlogs.blogspot.com

http://technet.microsoft.com/en-us/library/ms179511.aspxhttp://effulgentlogs.blogspot.com

Duane,... Not a great sign indeed. Maniknadan,.......... its obvious if some one will install two instances of sql server, one has to be named instance and are you sure with the link you pasted.... it points to "DATABASE MIRRORING ENDPOINT". I am all at sea with the topic of thread and the link pasted by you. Both Database engines seem to work okay, its the SSIS 2005 which is not Rahul Kumar, MCTS, India, http://sqlserversolutions.blogspot.com/

Ifyou have 2 different instances configured for mirroring with other 2 instances, you should have different end point for each of them.http://effulgentlogs.blogspot.com

Mani,how does it relate to odd behavior of SSIS 2005 after having SQL Server 2008 installed? Rahul Kumar, MCTS, India, http://sqlserversolutions.blogspot.com/

Rahul Kumar, Sorry for messed up earlier. I was replied on the DB stand point only and in case of BIDS you can't. The parallel install of 2008 had some incompatibility with the client/dev tools. This issue we faced earlier and had a seperate discussion for that.If its SSIS BIDS side, then you need to be carful and decide which version of BIDS to use. DB, Analysis and Reporting doesn't have this issues it seems. Sorry for the mess-ups and thanks for pointing out.http://effulgentlogs.blogspot.com

sorry, i meant to say ssis 2005 and ssis 2008.Duane Douglas, MCAD | http://www.ssisbi.com | Please mark the post(s) that answered your question.

Duane, so what does it leave us with.... maintain two machines separately for SSIS 2005 and SSIS 2008 I have reported it on connect...... hope we get a timely reply from Microsoft.... https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=449238 thanks, Rahul Kumar, MCTS, India, http://sqlserversolutions.blogspot.com/

Hello,I currently run both SSIS 2005 and SSIS 2008 side by side on three separate machines - one XP, one Vista 32bit, one Windows 2008 Server 64bit. Just to make sure - you are running Visual Studio 2005 to open your SSIS 2005 projects, and Visual Studio 2008 for your SSIS 2008 projects?Have you tried reinstalling the 2005 client tools? What order did you install things in?Thanks,~MattThis posting is provided "AS IS" with no warranties, and confers no rights

Ray of hope....Matt I installed SQL SERVER 2005 first and then SQL SERVER 2008.. and yeah i am using VS 2005 to open SSIS 2005 projects.Rahul Kumar, MCTS, India, http://sqlserversolutions.blogspot.com/

matt,perhaps you can shed some light on this. what is the order of installation that you used (including service packs)?Duane Douglas, MCAD | http://www.ssisbi.com | Please mark the post(s) that answered your question.

It's been awhile - I'll have to setup a new machine (which I'm doing now). On at least one of them I installed 2008 first, but I seem to remember my XP machine having 2005 to begin with. What order did you install things in? I can try to reproduce the issue.This posting is provided "AS IS" with no warranties, and confers no rights

Also, are there any specific GUIDs listed in the error message?This posting is provided "AS IS" with no warranties, and confers no rights

Matt.. My order of installation was 1) MS SQL Svr 2005 2 )MS SQL Svr 2008 for errors please see first post of the thread.Rahul Kumar, MCTS, India, http://sqlserversolutions.blogspot.com/

I just did a fresh install on a clean machine (Windows 7 RC). This is the order I installed everything in:1) SQL Server 2005- SQL Engine (named instance, SQL2005)- Integration Services- Tools2) SQL Server 2005 SP33) Visual Studio SP14) Visual Studio Update for Windows VistaAt this point I ran BIDS, created an SSIS project and package, and ran it to make sure everything worked.5) Full install of SQL Server 2008SP1 (Developer)I ran both 2008 and 2005, andthey seem to work fine.When you installed SQL Server 2008, did you perform and Upgrade, or a straight install?~MattThis posting is provided "AS IS" with no warranties, and confers no rights

thanks Matt for your suggestion... I got it working but i followed a little different path. a) install SQL SERVER 2005 b) install SQL SERVER 2008 at this point SSIS 2005 was not working c) I reapplied Service Pack 2 SQL SERVER 2005 and guess what SSIS 2005 start working fine. Thank Matt, Duane..just check out if you too can get it rightRahul Kumar, MCTS, India, http://sqlserversolutions.blogspot.com/

thanks for the tips guys. i don't remember the exact steps i took on my own because it was very long ago. nonetheless, i'll try your suggestions at some point in the future.Duane Douglas, MCAD | http://www.ssisbi.com | Please mark the post(s) that answered your question.

I installed SQL SERVER 2005 service pack 3 and that solved by problemand@