I would like to be able to edit SQL 2000 DTS packages from the SQL 2005
Server Management Studio however I get the message "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".

I have installed the DTS Designer Components and this works on some PCs but
not on others.

I have also tried the steps outlined in KB917406 and that does not help
either.

What do I need to do to get this work consistently?

Hello,

I understand that you cannot edit SQL 2000 DTS packages from mangement
studio on some machines. To know the issue better, I'd like to know the
following information:

1. Do you have SQL 2005 Backward Compatibility Components installed on the
problemtic machines? Or you only installed 2005 feature package which
includes Microsoft SQL Server 2000 DTS Designer Components?

905417 FIX: Error message when you try to open SQL Server 2000 Data
Transformation Services (DTS) packages in SQL Server Management Studio:
"SQL Server 2000 DTS Designer components are required to edit DTS packages"
http://support.microsoft.com/default...b;EN-US;905417

2. Did you have SSIS installed on the machines having this issue?


3. Did you check if the folder c:\Program Files\Microsoft SQL
Server\80\Tools\Binn exist and the following registry key exist?

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\80\Tools\ClientSetup

By default, Support for SQL Server 2000 DTS is installed automatically when
you install SQL Server 2005 Integration Services. However, some of the
registry settings and some of the environment settings that SQL Server 2000
DTS requires are deleted when you upgrade the last instance of SQL Server
2000. You may want to use the method4 in the following article to fix the
issue if the registry key is not correct:

919131 You may experience problems when you try to run a SQL Server 2000
DTS package after you upgrade all the instances of SQL Server 2000 to SQL
Server 2005
http://support.microsoft.com/default...b;EN-US;919131


Also, if you have 2005 sp1 installed, you may want to install latest
feature pack to see if it helps:

Feature Pack for Microsoft SQL Server 2005 - April 2006
http://www.microsoft.com/downloads/d...5aa-b4bd-4705-
aa0a-b477ba72a9cb&DisplayLang=en


In addtion, as I know, the SQL 2000 DTS Designer Components are not
supported on workstations with both 2000 and 2005 clients. The reason is
that the add-on was only designed to be loaded with SQL 2005 client tools,
not with SQL 2000 tools. You may encounter issues when saving DTS pacakge
in 2005 when you have both 2005 and 2000 client tools installed. The
workaround as I know is to save the package using menu Package --> Save,
then close using "X" on the right hand side.


If you have any update on the issue, please feel free to let me know. Thank
you!

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Hello,



Thanks for putting this list together for me, however I verified all the
items on your list and I still cannot edit a DTS package in SQL 2005.



I have looked at the following based on your list:



1. Backward Compatibility is installed.

2. SSIS is installed.

3. I checked the registry key and environment variable specified in KB919131
and both were correct. I do have SQL 2005 SP1 on the PC and installed the
Backward Compatibility and DTS Designer Components from the latest feature
pack as you suggested.



A few other notes about the main machine I am troubleshooting on, this PC is
running Windows 2003 SP1 and is a fresh install after a system reset a few
days ago. I was not upgrading SQL on this machine, in fact I didn't even
install SQL 2000 on it at first. After I did a reset of Windows, I
installed SQL 2005 and SP1, installed the DTS components, and then
determined that I could not edit the DTS packages. I then installed SSIS,
but still had the problem. I then did some further searching on this
problem and found a suggestion to install SQL 2000 client tools and did so
at that point.



I have several other PCs that are having this problem but I am trying to
first get the problem fixed on one.



Thanks again for your help,

Laura Galusha





"Peter Yang [MSFT]" <petery (AT) online (DOT) microsoft.com> wrote

Hello Laura,

I was not able to reproduce the issue on my side. I have SQL 2005 sp1
installed, I then installed DTS Designer Components and I can open DTS
package saved from another SQL 2000 server properly.

You may want to create a new simple package in Enterpise Manager on the
same Win2003 machine, and save it to local folder, and try to open it via
Management studio to see the result.

If the issue still occurs, I suspect backup compatiblity component is not
installed properly. You may want to repair backup compatiblity component as
described in KB 919131 to see if it is helpful at this point. Or you may
want to reinstall backup compatiblity component to test.

Please let me know if there is any update. I look forward to your reply.
Thank you!

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support


================================================== ===


This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====

Hello,

I tried creating and saving a package to a local folder but I could not open
in SQL 2005.

I looked at KB 919131 and I did the steps in method 1, reapplied SQL 2005
SP1, and no luck.

I then tried method 4 - the registry entry and the path variable already
looked OK but I readded the registry value, made sure it pointed to the
correct location and I still get an error.

Any other ideas?



"Peter Yang [MSFT]" <petery (AT) online (DOT) microsoft.com> wrote

Hi,

Going forward, plesae refer to the following steps to capture

1. http://www.sysinternals.com/Utilities/Filemon.html - you plan on using
File monitor on WinNT/2K/XP. Extract it and run file monitor.
2. From the option menu, uncheck Capture events. From the Edit menu, click
Clear Display
4. Open Management studio and select the DTS package
5. Enable Capture events in File monitor tool, and then try to open the
package. Once the error occurs, stop capture events.
6. From the File menu in File monitor, click Save As to save the log to a
file and then send the file to me for further analysis.
7. Use the regmon http://www.sysinternals.com/Utilities/regmon.html to do
following steps 1-6 to get regmon

You may send the log to me at petery (AT) microsoft (DOT) com, and I will check if I'm
able to find any clues from here.

Also, you could use listdll or process explorer in www.sysinternals.com to
get the DLL list of the sqlwb.exe to check if there is any difference with
that on known good machines.

Thank you!

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support


================================================== ===

This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====

Hello Laura,

Thank you for your reply. From the log I saw Sqlwb tried to load sqlgui.dll
from C:\WINDOWS\system\ folder other than C:\Program Files\Microsoft SQL
Server\80\Tools\Binn folder.


1783 9:49:15 AM SqlWb.exe:2976 QUERY INFORMATION C:\Program Files\Microsoft
SQL Server\90\Tools\Binn\VSShell\Common7\IDE\SQLGUI.dl l NOT FOUND
Attributes: Error
1784 9:49:15 AM SqlWb.exe:2976 QUERY INFORMATION C:\Program Files\Microsoft
SQL Server\90\Shared\SQLGUI.dll NOT FOUND Attributes: Error
1785 9:49:15 AM SqlWb.exe:2976 QUERY INFORMATION
C:\WINDOWS\system32\SQLGUI.dll NOT FOUND Attributes: Error
1786 9:49:15 AM SqlWb.exe:2976 QUERY INFORMATION
C:\WINDOWS\system\SQLGUI.dll SUCCESS Attributes: A

1794 9:49:15 AM SqlWb.exe:2976 READ C:\WINDOWS\system\SQLGUI.dll SUCCESS
Offset: 0 Length: 256
1795 9:49:15 AM SqlWb.exe:2976 READ C:\WINDOWS\system\SQLGUI.dll SUCCESS
Offset: 64 Length: 256

I suggest that you temporarily remove the file from
C:\WINDOWS\system\sqlgui.dll to another folder, and let sqlwb load than
C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlgui.dll to test the
situation. It seems sqlwb tries to use the %path% variable to search for
sqlgui.dll and it searches C:\WINDOWS\system\ before C:\Program
Files\Microsoft SQL Server\80\Tools\Binn folder.

In addition, the file version of C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\sqlgui.dll shall be 2000.80.2039 for sp1.

If you have any update, please feel free to let's know. Thank you for your
time.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support


================================================== ===

PLEASE NOTE: The partner managed newsgroups are provided to assist with
break/fix
issues and simple how to questions.

We also love to hear your product feedback!

Let us know what you think by posting
- from the web interface: Partner Feedback
- from your newsreader: microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====

Hi Peter,

I was able to get this to work by deleting SQLQUI.DLL and SQLSVC.DLL from
the C:\windows\system directory.

The 2 DLL files in this directory were much older than the DLLs in
C:\Program Files\Microsoft SQL Server\80\Tools\Binn.

I don't think that SQLWB is using the path variable to find these files as I
tried listing C:\Program Files\Microsoft SQL Server\80\Tools\Binn first in
my path and SQLWB still looked in this directory last.

Could you provide me with some information as to what installs the SQL DLLs
to the C:\windows\system directory, I would like to have some ideas for
avoiding this problem in the future.

Thanks for your help,
Laura Galusha


"Peter Yang [MSFT]" <petery (AT) online (DOT) microsoft.com> wrote

Hello Laura,

Based on the further research, I agree with c:\windows\system folder is not
related to path variable and this behavior is from inside SQLWB itself.
However, I was not able to find any possible reasons that sqlqui.dll and
sqlsvc.dll could be copied to c:\windows\system folder. I suspect it might
be installed by some third party programs that need these dlls. Just a
guess though.

Usually c:\windows\system folder is not used to store dlls as that in
Windows9x any more though some programs may still use this folder for
backward compatiblity purpose.

If you anything is unclear or you have any comments, please feel free to
let's know. Thank you!

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support


================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====