DTS 2000 Designer Components

After installing the DTS 2000 designer components from the feature packI get the following error message when trying to open a package:

-

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. (Microsoft.SqlServer.DtsObjectExplorerUI)

The thing is that I have installed them!! so what's going on here, is there a registry key I need to remove or something?, I've uninstalled and re-installed them, rebooted the server numerous times but still no joy, SQL Server just tells me that they're not installed, as you can imagine this is a real pain as I cannot do anything with my legacy packages on the 2005 server.

I cannot just migrate the packages from my 2000 server as they are in daily use on a production server. Is there an option to migrate/copy packages but leave the source packages untouched?

Help!

Yay, I seem to have stumbled across a solution for this:-

1. Uninstall SQL Server 2005 Backward Compatibilty

2. Uninstall SQL Server 2000 DTS Designer Components

3. Re-install SQL Server 2005 Backward Compatibilty

4. Re-install SQL Server 2000 DTS Designer Components

5. On the SQL Server 2000, open te DTS package and save it to the 2005 Server ( it will be placed in the <server name>\Management\Legacy\Data Transformation Services folder)

6. Edit the package on the 2005 server, NB. if you make any changes and save the package, the designer will take it upon itself to kindly auto-arrange your package so the package you had taken time to lay out in a nice readable format now resembles a bowl of spaghetti.

I found that moving the 2000 DTS packages in any other way than in step 5 resulted in the designer throwing up all sort of errors, although it did still work until you actually tried to save it. In my opinion, this is far too flaky and I am very hesitant to upgrade to SQL 2005 and leave my DTS packages in the hands of this designer.

|||I am trying to to the same thing, where do I find the download "SQL Server DTS Designer Components"? Second question, did you get it to work?|||

The DTS designer components are part of the SQL Server 2005 feature pack, just do a search for it on the microsoft website.

I found that the designer components work ok for some of my 2000 packages but not for others. I don't know why it behaves like this and there is no pattern to it, all I know is that it is a pain in the backside.

hope this helps

|||

Feature Pack for Microsoft SQL Server 2005 - November 2005 http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

Which includes -

Microsoft SQL Server 2000 DTS Designer Components http://download.microsoft.com/download/4/4/D/44DBDE61-B385-4FC2-A67D-48053B8F9FAD/SQLServer2005_DTS.msi

|||Thank you this solved my problem.

DTExec is the only redist for executing dtsx file?

Question:

trying to execute SSIS package "Package.dtsx" from another machine. What are the requirements to do this without installing full SSIS?
I presume that we need .Net framework 2.0, but what are the minimum component or files I need to run a package?

thanks
HorseshoeMy understaning is that SSIS is not redistributable as DTS was. Either way there are more files than just dtexec. All the tasks and components are spread accross several assemblies for example. If it is redistributable, then it will be covered in redist.txt or the equivalent if that has changed from SQL 2000. I believe it is now licencsed as server component, so you need a server licence for any machine you install it on.|||Darren's absolutely right. For a headless install (without UI) on a server, you can select to not install the Tools, but you still need a license and the SQL Server setup to install SSIS on another machine.

regards
ash

DST Problem

After installing the Microsoft DST patch on the server running RS2000 we are
getting the following error when trying to run reports:
Specified argument was out of the range of valid values. Parameter name: date
If I uncheck the observe DST on the date/time control panel app then all is
OK.
Right now I have it off and adjusted the time manually.
Any suggestions on how to resolve this.On Mar 12, 8:51 am, Kyle <K...@.discussions.microsoft.com> wrote:
> After installing the Microsoft DST patch on the server running RS2000 we are
> getting the following error when trying to run reports:Specifiedargumentwasoutof therangeofvalidvalues.Parametername:date
> If I uncheck the observe DST on thedate/time control panel app then all is
> OK.
> Right now I have it off and adjusted the time manually.
> Any suggestions on how to resolve this.
I too have found the same issue and your workaround works for me as
well. If I come up with a resolution, I will post back. What SP are
you running? I we are on SP1.|||We are running:
Windows 2000 SP4
Reporting Services 2000 SP1
SQL Server 2000 (Not sure of the service pack)
"msprygada@.gmail.com" wrote:
> On Mar 12, 8:51 am, Kyle <K...@.discussions.microsoft.com> wrote:
> > After installing the Microsoft DST patch on the server running RS2000 we are
> > getting the following error when trying to run reports:Specifiedargumentwasoutof therangeofvalidvalues.Parametername:date
> >
> > If I uncheck the observe DST on thedate/time control panel app then all is
> > OK.
> >
> > Right now I have it off and adjusted the time manually.
> > Any suggestions on how to resolve this.
> I too have found the same issue and your workaround works for me as
> well. If I come up with a resolution, I will post back. What SP are
> you running? I we are on SP1.
>|||On Mar 12, 10:05 am, mspryg...@.gmail.com wrote:
> On Mar 12, 8:51 am, Kyle <K...@.discussions.microsoft.com> wrote:
> > After installing the Microsoft DST patch on the server running RS2000 we are
> > getting the following error when trying to run reports:Specifiedargumentwasoutof therangeofvalidvalues.Parametername:date
> > If I uncheck the observe DST on thedate/time control panel app then all is
> > OK.
> > Right now I have it off and adjusted the time manually.
> > Any suggestions on how to resolve this.
> I too have found the same issue and your workaround works for me as
> well. If I come up with a resolution, I will post back. What SP are
> you running? I we are on SP1.
Our sys admin had me look at this
http://support.microsoft.com/?kbid=931975&SD=tech
but he updated the server with the update and we do not have SQL
Notification Services. So this was of no help to me but maybe it can
help you.|||On Mar 12, 10:46 am, Kyle <K...@.discussions.microsoft.com> wrote:
> We are running:
> Windows 2000 SP4
> Reporting Services 2000 SP1
> SQL Server 2000 (Not sure of the service pack)
>
Windows 200 SP4, RS 200 SP1 (I think SP2 is out), and SQL Server SP3
To get version, type select @.@.version in QA (version info below)
SQL Server 2000 version and level @.@.VERSION ProductLevel
SQL Server 2000 Original Release 8.00.194 RTM
Database Components SP1 or 8.00.384 SP1
Desktop Engine SP1
Database Components SP2 or 8.00.534 SP2
Desktop Engine SP2
Database Components SP3 or SP3a, or 8.00.760 SP3
Desktop Engine SP3 or SP3a|||On Mar 12, 10:57 am, mspryg...@.gmail.com wrote:
> On Mar 12, 10:46 am, Kyle <K...@.discussions.microsoft.com> wrote:
> > We are running:
> > Windows 2000 SP4
> > Reporting Services 2000 SP1
> > SQL Server 2000 (Not sure of the service pack)
> Windows 200 SP4, RS 200 SP1 (I think SP2 isout), and SQL Server SP3
> To get version, type select @.@.version in QA (version info below)
> SQL Server 2000 version and level @.@.VERSION ProductLevel
> SQL Server 2000 Original Release 8.00.194 RTM
> Database Components SP1 or 8.00.384 SP1
> Desktop Engine SP1
> Database Components SP2 or 8.00.534 SP2
> Desktop Engine SP2
> Database Components SP3 or SP3a, or 8.00.760 SP3
> Desktop Engine SP3 or SP3a
Man, need to slow down when I type:
Windows 2000 SP4, RS 2000 SP1 (I think SP2 is out), and SQL Server
2000 SP3|||We are having the same issue as the one noted and we are using the same work
around at the moment.
SQL Server 2000 Version: 8.00.2039
SQL Server Reporting Services Version: 8.00.1042
This is a huge problem for us.
"msprygada@.gmail.com" wrote:
> On Mar 12, 8:51 am, Kyle <K...@.discussions.microsoft.com> wrote:
> > After installing the Microsoft DST patch on the server running RS2000 we are
> > getting the following error when trying to run reports:Specifiedargumentwasoutof therangeofvalidvalues.Parametername:date
> >
> > If I uncheck the observe DST on thedate/time control panel app then all is
> > OK.
> >
> > Right now I have it off and adjusted the time manually.
> > Any suggestions on how to resolve this.
> I too have found the same issue and your workaround works for me as
> well. If I come up with a resolution, I will post back. What SP are
> you running? I we are on SP1.
>|||We are also having the same problem, but the workaround is working for us
right now.
Regards,
Steve
"Kyle" wrote:
> After installing the Microsoft DST patch on the server running RS2000 we are
> getting the following error when trying to run reports:
> Specified argument was out of the range of valid values. Parameter name: date
> If I uncheck the observe DST on the date/time control panel app then all is
> OK.
> Right now I have it off and adjusted the time manually.
> Any suggestions on how to resolve this.
>|||We have the same issue.
I also temporaily turned off the Windows Time service so it wouldn't re-sync
with our domain controller.
Thanks,
MB
"Kyle" <Kyle@.discussions.microsoft.com> wrote in message
news:660D17F1-EE9C-4EBE-99FA-99E9688C885D@.microsoft.com...
> After installing the Microsoft DST patch on the server running RS2000 we
> are
> getting the following error when trying to run reports:
> Specified argument was out of the range of valid values. Parameter name:
> date
> If I uncheck the observe DST on the date/time control panel app then all
> is
> OK.
> Right now I have it off and adjusted the time manually.
> Any suggestions on how to resolve this.
>|||Same problem here as well. It does not seem to be an issue with RS
2005, only RS 2000.|||I'm also seeing the same problem with our SQL 2000 RS Server.
Microsoft! We need a patch for this....(can you have it ready sometime
last week?)|||This was posted on over on MSDN in response to the same problem:
You need to apply a patch that replaces two dll's on your web server that
deal with time services. I don't have the KB article but it shouldn't be hard
to find at the MS website. FYI, if you have a Win 2000 server and don't have
an extended service contract with M$ they'll charge you $4000 for the patch
(I'm told). We have the extended service contract... We had the same problem
and this is how we fixed it.
I have yet to find the KB article he is talking about. Thought maybe more
people searching would help wade throught the 1000's of DST articles.
"Kyle" wrote:
> After installing the Microsoft DST patch on the server running RS2000 we are
> getting the following error when trying to run reports:
> Specified argument was out of the range of valid values. Parameter name: date
> If I uncheck the observe DST on the date/time control panel app then all is
> OK.
> Right now I have it off and adjusted the time manually.
> Any suggestions on how to resolve this.
>|||I saw that too. I believe that person was referring to the DST patch itself.
(He mentions the $4000 charge; and that was for the DST patch).
I do not believe there is a RS patch, and according to KB931975 there is no
need for one. Conversely, they do mention a patch for SQL Notification
Services in that article.
http://support.microsoft.com/kb/931975
Now is the time when searching the MSDN blogs could prove useful. Maybe
we'll find a SQL RS developer who will acknowledge this oversight.
-Rob
"Kyle" wrote:
> This was posted on over on MSDN in response to the same problem:
> You need to apply a patch that replaces two dll's on your web server that
> deal with time services. I don't have the KB article but it shouldn't be hard
> to find at the MS website. FYI, if you have a Win 2000 server and don't have
> an extended service contract with M$ they'll charge you $4000 for the patch
> (I'm told). We have the extended service contract... We had the same problem
> and this is how we fixed it.
> I have yet to find the KB article he is talking about. Thought maybe more
> people searching would help wade throught the 1000's of DST articles.
>
> "Kyle" wrote:
> > After installing the Microsoft DST patch on the server running RS2000 we are
> > getting the following error when trying to run reports:
> > Specified argument was out of the range of valid values. Parameter name: date
> >
> > If I uncheck the observe DST on the date/time control panel app then all is
> > OK.
> >
> > Right now I have it off and adjusted the time manually.
> > Any suggestions on how to resolve this.
> >|||Poster on MSDN came up with this:
http://support.microsoft.com/default.aspx/kb/932590
Win2000 is not listed so I forwarded it to our server guys to see if we have
an extended contract on the server in question.
Hope this helps...
"Kyle" wrote:
> This was posted on over on MSDN in response to the same problem:
> You need to apply a patch that replaces two dll's on your web server that
> deal with time services. I don't have the KB article but it shouldn't be hard
> to find at the MS website. FYI, if you have a Win 2000 server and don't have
> an extended service contract with M$ they'll charge you $4000 for the patch
> (I'm told). We have the extended service contract... We had the same problem
> and this is how we fixed it.
> I have yet to find the KB article he is talking about. Thought maybe more
> people searching would help wade throught the 1000's of DST articles.
>
> "Kyle" wrote:
> > After installing the Microsoft DST patch on the server running RS2000 we are
> > getting the following error when trying to run reports:
> > Specified argument was out of the range of valid values. Parameter name: date
> >
> > If I uncheck the observe DST on the date/time control panel app then all is
> > OK.
> >
> > Right now I have it off and adjusted the time manually.
> > Any suggestions on how to resolve this.
> >|||Has there been any word on a patch?
We're in the same boat, but we don't have the luxury of using the workaround
(in our infinite wisdom, we decided to install WRS on a domain controller),
and the only option open right now is migrating it to a new box where
hopefully we can get the workaround working.|||If you have not rebooted your servers after applying the DST patch...you need
to.
"Jacques C" wrote:
> Has there been any word on a patch?
> We're in the same boat, but we don't have the luxury of using the workaround
> (in our infinite wisdom, we decided to install WRS on a domain controller),
> and the only option open right now is migrating it to a new box where
> hopefully we can get the workaround working.|||We had the exact same error as described above. After we restarted our
server, the issue was resolved.
SQL 2000 SP4
WINDOWS 2000
REPORTING SERVICES 2000 SP2
"Jacques C" wrote:
> Has there been any word on a patch?
> We're in the same boat, but we don't have the luxury of using the workaround
> (in our infinite wisdom, we decided to install WRS on a domain controller),
> and the only option open right now is migrating it to a new box where
> hopefully we can get the workaround working.