October 31, 2006 at 2:09 pm
We are running both SQL 2000 Enterprise Manager and SQL 2005 Client tools on our XP workstation. After installing the SQL Server 2005 DTS add-in, we are having the following problem in SQL 2000 Enterprise Manager. After making a change to a DTS Package (in EM), if you close the package window without saving your changes, it then prompts you to save your DTS Package. When choosing yes, it brings up a Package Error as follows:
Error Source: Microsoft Data Transformation Services (DTS) Package
Error Description: The DTS host failed to load or save the package properly.
Yes we can save the changes before exiting but many developers close the DTS package window and then save. We don't want to roll this out to all of our developers and cause problems or annoyances for them when doing their work.
I've tried the Microsoft SQL Server 2005 Backward compatibility Repair (in add/remove programs), I've tried reinstalling SP4 and tried a manifest file hack none of which have fixed the problem.
Thanks
October 31, 2006 at 11:36 pm
Are you connecting to SQL 2000 or SQL 2005 with Enterprise Manager? Enterprise Manager isn't forwards compatible with SQL 2005.
November 1, 2006 at 9:43 am
I'm connecting to SQL 2000 Enterprise Manager. --Trying to edit and save a SQL 2000 package.
Do you have both installed on your XP workstation with the DTS Add-in? I'm wondering if others haven't noticed this problem because it only happens if you exit the package and then choose to save it.
Thanks for your reply!!!
November 1, 2006 at 12:02 pm
There's a lot of "stuff" wrong with any new product like this... I would just document it and get on with the rollout... developers can deal with problems... maybe one will even provide a solution. We went through this with the beta versions and ended up with a four or five page document with each new release... I'm sure it's not as bad today; but, I am also quite sure everything isn't fixed either. you have to just deal with it sometimes.
Thank-you,
David Russell
Any Cloud, Any Database, Oracle since 1982
November 1, 2006 at 12:03 pm
I know that Enterprise Manager is a SQL 2000 client tool and that DTS packages are SQL 2000 as well, but my question is about the database engine. Are you connecting to SQL Server 2000 or are you connecting to SQL Server 2005?
November 1, 2006 at 1:08 pm
Sorry about that, I'm connecting to SQL Server 2000.
November 1, 2006 at 1:24 pm
Have you read this KB article? http://support.microsoft.com/kb/917406
It sounds like to me that once a DTS package has been edited in SQL 2005, it never works right in SQL 2000 again.
November 1, 2006 at 2:02 pm
I did try those fixes and neither worked.
I've never tried to edit these packages in SQL 2005. It seems the 2000 Enterprise Manager on my XP wkst no longer functions correctly after installing the DTS add-in.
Do you have both on your workstation? Can you determine if you have the same results?
November 1, 2006 at 3:02 pm
I no longer have both on my workstation as we are no longer using SQL 2000 here.
Is there anything that your developers would need to do that they can't do with SQL Server Management Studio? I've been using it exclusively for SQL 2000 for quite some time ... at least I was until we stopped using SQL 2000.
December 6, 2006 at 7:01 am
Has anybody heard from MS about this ? The 2000 and 2005 clients (with DTS Designer) cannot coexist on the same WS, this is a big problem for me. I reverted to an image prior to the install of the 2005 client and this now works fine, but moving forward I need to have both.
This is a major issue.
December 7, 2006 at 9:13 am
Right click in "design package" window, then choose save, this works instead of trying to save when exiting EM2000
December 7, 2006 at 10:57 am
Do the names have any non-alphanumeric charcters in them? I've read that removing these from the package names has helped some people.
I've lso read that you should download and install SQLServer2005_BC component for backward compatibility from Microsoft first and then Install SQLServer2005_DTS component. If you didn't do it in that order, maybe reinstall both of those items in that order.
However, after reading that this problem only exists on Wndows XP or 2003 for packages that were created on Windows 2000 (I'm not saying that is 100% accurate, just that I read that), it makes me think that it may be related to the security changes in Win XP/2K3.
Try checking the security settings of the directory to which you are trying to save the package. Once you are sure that the security settings are correct, be sure to propogate the settings to child directories and files. You may also need to disable inheritance of the directory's parent directories.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply