sjones,
Is SQL 2000 installed on the same server as SQL 2005? If it is on a server
all by its lonesome, I'm guessing you don't have (and can not get)
permissions to log on/remote desktop in to this server to use EM on it,
correct?
Do you still have the SQL 2000 install disks around? Can you install EM on
a client machine that does not use SSMS/SQL 2005? I know that is a lot of
work, but I'm not very experienced and editing the package with EM is the
only solution I've found online...just have to wait and see if MS is going
to fix this bug.
The only 2 updates I see on my computer for SQL Server is:
1. Microsoft SQL Server 2005 SP2 (KB 921896) applied Friday, 7/20/2007
2. Critical Update for SQL Server 2005 SP2 (KB 934458) applied Monday,
7/23/2007
Keep in mind, these updates are applied to my client computer. I don't know
what, if any, updates have been applied to the server.
Now, I did not notice the problem instantaneously as I do not work in
SSMS/SQL 2005 every day. Who knows...maybe some other Windows update messed
things up.
Bye-the-bye, I'm using SSMS on Win XP Pro and our SQL 2005 Instance is
installed on Win Server 2003.
Sorry I couldn't be of any more help,
Conan
"sjones" <sjones RemoveThis @discussions.microsoft.com> wrote in message
news:07F233F4-48FA-456D-A35B-742D79F64028@microsoft.com...
> Thank you for the quick response, however . . .
>
> 1. I am already trying to open it from a SQL 2000 instance.
> 2. I don't have access to EM anywhere.
>
> Do you happen to remember which update/service pack it was that started
> your
> having problems? I ask because this problem is something new. There was
> a
> time (not too long ago) when I WAS able to open DTS from SQL 2005. Maybe
> the
> same thing happened to me.
>
> "Conan Kelly" wrote:
>
>> sjones,
>>
>> I don't recall the exact messages I was getting when trying to open DTS
>> packages in SSMS (connected to a SQL 2005 server)...they may have been
>> the
>> same message. It was weird...some would open and some wouldn't. After
>> googling the error message, I came across a site that mentioned that if a
>> DTS package was last edited with SQL2 005 (or SSMS...don't remember
>> which),
>> it would not open again on SQL 2005/SSMS (don't have a link...didn't
>> think
>> to keep it).
>>
>> A couple of things I can suggest is:
>> 1. If you still have a SQL 2000 instance somewhere, try connecting to
>> that through SSMS and opening the package through the SQL 2000 connection
>> (may not make a difference).
>> 2. The one thing I know that always works for me is I remote desktop
>> into our server that still has SQL 2000 installed on it and then I open
>> and
>> edit the DTS package in EM. I first try opening it in SSMS connected to
>> SQL
>> 2005, and if I get error messages, then I go this route and it always
>> works.
>>
>> These errors started popping up for me after an update (or service pack)
>> to
>> SSMS.
>>
>> HTH,
>>
>> Conan
>>
>>
>>
>>
>>
>> "sjones" <sjones RemoveThis @discussions.microsoft.com> wrote in message
>> news:DCE0C995-0951-4BC7-A634-E396EF5FE779@microsoft.com...
>> >I have installed the SQL Server 2000 DTS Designer Components on a Vista
>> > machine. When trying to open a .dts file (Management Studio |
>> > Management |
>> > Legacy | right-click Data Transformation Services | Open Package File |
>> > browse to desired .dts file), I get the following message:
>> >
>> > "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."
>> >
>> > However, as I said, the SQL Server 2000 DTS Designer Components ARE
>> > installed.
>> >
>> > Does anyone know what the problem is?
>> >
>> > Thank you!
>>
>>
>> >> Stay informed about: Error when trying to open DTS package using 2000 DTS Desig.. 
FAQ
Profile
Private Messages
Log in
