October 1, 2007 at 9:20 am
I have installed SQL Server 2000 DTS Designer Components, when i try to open a package. it will pop up errors.
Error source: M DTS
Error description: DTS host failed to load or save the package properly.
I clicked ok
DTS package error
The selected pakcage cannot be opened. DTS designer has been closed.
I clicked ok
SQL server 2000 dts designer components are required to edit dts. installed speacil webdownload.....
October 1, 2007 at 11:13 am
Are you opening packages that were saved to SQL Server or are they files? I found that I had to save them as files and open them in SSMS with DTS Designer, then I could save them to SQL Server.
Greg
Greg
October 1, 2007 at 11:48 am
just a quick reminder here.
remember that you can only 'see' the dts packages (that is they are read-only)
even though you have the designer components, and can view the package
in 2005 dts designer components are there for ONLY 2 things.
1. View the DTS package. (editing them is not supported)
2. DTS 2000 run-time environment. (so they can be run as normal)
a good trick is to modify the package on the source 2000 server with new
connection properties to represent my 2005 server, then when i pull them over
they don't seen any modification.
hope this is useful.
_________________________
October 1, 2007 at 11:52 am
saved it as .dts. on SS2000 as storage file with extension .dts.
Went to SSMS / legacy / dts Tried to opened the package and the error popup.
October 1, 2007 at 12:20 pm
Hm. Do you have any custom tasks i.e. DLLs in the packages that need to be registered? Check out Ed Vassie's comments in this thread: http://www.sqlservercentral.com/Forums/Topic396124-5-1.aspx
NeoTokyo, I'm able to edit and save legacy DTS packages in SSMS, so I don't think it's entirely accurate to say editing them is unsupported. 🙂
Greg
Greg
October 2, 2007 at 7:55 pm
I also edit DTS packages in 2005. Are you on Service SS-2005 Pack 2 ? And you have the Backward Compatibilty add-in for DTS ?
October 4, 2007 at 2:51 am
This sounds ilke the KB 917406 problem. Even though our sitation did not meet the criteria listed in KB 917406, we got the message quoted, and applying the workaround in 917406 fixed the problem for us.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
October 4, 2007 at 9:48 am
interesting... i might not be patched up completely. i'll look things over this afternoon. would be nice to edit completely.
_________________________
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply