July 6, 2010 at 8:37 am
Hi
We have recently done a migration from SQL Server 2000 on 32-bit machine (Server A) to SQL Server 2005 on 64-bit machine (Server B). We have installed Oracle clients 32-bit and 64-bit on the server B. And we have migrated the DTS packages as legacy packages and installed DTS Designer tools on Server B. Then we could open the DTS packages and edit them on Server B, but couldn’t save the edited DTS package.
We thought there was some problem with the DTS Designer components and uninstalled and reinstalled them. But now we couldn’t even open the DTS package. We are getting the following error.
This package cannot be edited.
SQL Server 2000 DTS Designer components are required to edit DTS packages. Install the special Web download, "SQL Server 2000 DTS Designer Components" to use this feature.
If the "SQL Server 2000 DTS Designer Components" download is already installed, there might be a problem with the compatibility of icons persisted in this DTS package. See the following KB article for more details: http://support.microsoft.com/kb/917406 (Microsoft.SqlServer.DtsObjectExplorerUI)
Could anyone please help me with this?
Thank You,
Best Regards,
SQL Buddy
July 6, 2010 at 9:05 am
Hi,
We had exactly the same issue with our migrated DTS packages. The fix described in Method 1 of KB917406 resolved the issue for us.
Good luck,
Cath
July 6, 2010 at 12:02 pm
Hi Cath,
Thanks a lot for your reply. We tried that solution. But of no help.
Thank You,
Best Regards,
SQL Buddy
July 6, 2010 at 7:57 pm
What is the operating System that you are using? The OS will have some effect on the solution.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
July 7, 2010 at 1:52 pm
Hi Jason,
Server A has SQL Server 2000 on Windows 2000 (32-Bit) and Server B has SQL Server 2005 (64 bit) on Windows server 2003 (64 bit)
Thank You,
Best Regards,
SQLBuddy
July 7, 2010 at 2:17 pm
Try this:
http://jasonbrimhall.info/2010/07/07/sql-2008-dts/
I recently ran into the same sort of thing and just finished writing about my experiences with it. It may prove useful to you. Most of the first few steps apply to SQL 2005 as well. Some considerations would be that you may need to copy files to the Program Files (x86) directory rather than the Program Files directory.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
July 8, 2010 at 5:26 am
I believe you need the Backward Compatible Components installed!
July 9, 2010 at 8:40 am
I had a very similar problem with getting Legacy DTS packages working in SSMS 2008. The following article was the only one I found that worked (I found several that did not before finding this one)
I don't know for sure if corresponds well to 2005 but they have specific files that the DTS designer needs that they have you copy from the instance specific folders.
When you get the the file copy sections of the article you will have to change the "...Microsoft SQL Server\100..." references to the correct 2005 folder I think it is "...Microsoft SQL Server\90..."
Also in SQL 2008 only sysadmins can modify DTS packages that they do not own. I had to alter two system stored procedures to allow specific users to alter all DTS packages on one server who needed this ability but could not be made sys admins. (Modifying system stored procs is never recommended but it was required for our upgrade) Unfortunately, I can't remember the stored proc names I found them by Googleing the error code that we were getting.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply