Hi

We have SQL Server 2005 Standard Edition Running on a 64-bit processor.
We have been unable to get the DTS Designer to open and edit packages. I
have tried installing the Web download it says to install but then I get
an error saying the package could not be read. The message points to a
KB article that talks about removing a dependency in a config file but
this dependency does not exist on the server.

(Sorry I am typing from memory I don't have access to the server right
now).

Is it possible to edit DTS Packages on a 64-bit SQL Server 2005
installation?

-Dick





*** Sent via Developersdex http://www.developersdex.com ***

Dick C. wrote:
> Hi

Hello

Have a look here There are some bad news for you
http://support.microsoft.com/kb/810927


in a nutshell the DTS runtime and its designer tools are not available
on the 64-bit platform. You can read data from and write data to a
64-bit system from a 32-bit system running DTS, and you can physically
store your DTS packages in a 64-bit SQL Server database. But the DTS
packages themselves will not run on the 64-bit platform.

regards
SW

>
> We have SQL Server 2005 Standard Edition Running on a 64-bit processor.
> We have been unable to get the DTS Designer to open and edit packages. I
> have tried installing the Web download it says to install but then I get
> an error saying the package could not be read. The message points to a
> KB article that talks about removing a dependency in a config file but
> this dependency does not exist on the server.
>
> (Sorry I am typing from memory I don't have access to the server right
> now).
>
> Is it possible to edit DTS Packages on a 64-bit SQL Server 2005
> installation?
>
> -Dick
>
>
>
>
>
> *** Sent via Developersdex http://www.developersdex.com ***

No, it is not as bad as that. KB 810927 is about SQL Server 2000. Here is
a KB on 2005:
http://technet.microsoft.com/en-us/l.../ms141766.aspx

The tips for running 32-SSIS packages can be extended to running 32-bit DTS
packages. Simply create a SQL Agent job with an Operating System job step
and run:
DTSRUN your package parameters.
Since DTSRUN is a 32-bit executable it will run in 32-bit Windows-On-Windows
(WOW) on a 64-bit server. The one thing to look our for in running 32-bit
packages is the location of some executables.

64-Bit
Windows\System32
Program Files

32-bit
Windows\SysWOW64
Program Files (x86)

In order to maintain the ability to edit these DTS packages, read:
http://technet.microsoft.com/en-us/l.../ms143755.aspx. See the note on
downloading theDTS package designer.

I am happily running 64-bit SSIS, 32-Bit DTS, etc, etc, without any
problems.

RLF


"Sebastian Waksmundzki" <sebwaks@yahoo.co.uk> wrote in message
news:%23nubQSOGIHA.5328@TK2MSFTNGP05.phx.gbl...
> Dick C. wrote:
>> Hi
>
> Hello
>
> Have a look here There are some bad news for you
> http://support.microsoft.com/kb/810927
>
>
> in a nutshell the DTS runtime and its designer tools are not available
> on the 64-bit platform. You can read data from and write data to a
> 64-bit system from a 32-bit system running DTS, and you can physically
> store your DTS packages in a 64-bit SQL Server database. But the DTS
> packages themselves will not run on the 64-bit platform.
>
> regards
> SW
>
>>
>> We have SQL Server 2005 Standard Edition Running on a 64-bit processor.
>> We have been unable to get the DTS Designer to open and edit packages. I
>> have tried installing the Web download it says to install but then I get
>> an error saying the package could not be read. The message points to a
>> KB article that talks about removing a dependency in a config file but
>> this dependency does not exist on the server.
>>
>> (Sorry I am typing from memory I don't have access to the server right
>> now).
>>
>> Is it possible to edit DTS Packages on a 64-bit SQL Server 2005
>> installation?
>>
>> -Dick
>>
>>
>>
>>
>>
>> *** Sent via Developersdex http://www.developersdex.com ***

Russell Fields wrote:
> No, it is not as bad as that. KB 810927 is about SQL Server 2000. Here is
> a KB on 2005:
> http://technet.microsoft.com/en-us/l.../ms141766.aspx

Wow I was late yeo you have absolutely right

regards
SW
>

Russell Fields wrote:
> No, it is not as bad as that. KB 810927 is about SQL Server 2000. Here is
> a KB on 2005:
> http://technet.microsoft.com/en-us/l.../ms141766.aspx

Wow it was late You have absolutely right

regards
SW

Hi Russell,

You wrote:
In order to maintain the ability to edit these DTS packages, read:
http://technet.microsoft.com/en-us/l.../ms143755.aspx. See the note
on
downloading theDTS package designer.


Yes I have read this page before, and downloaded and installed the
"Microsoft SQL 2000 DTS Designer Components" but it still doesn't allow
me to open DTS Packages, it references a knowledge base article at
http://support.microsoft.com/kb/917406 which talks about deleting a
dependency in the SQLwb.exe.manifest file which I have also done. But I
am still unable to even open/edit the DTS Packages on the SQL 2005
64-bit server.

We are able to use DTSRUN with no problems on this box.

-Dick


*** Sent via Developersdex http://www.developersdex.com ***

Dick,

Yes, I reviewed my notes and found that my response was colored by the first
post. However, with regard to your on-going problem, I have not experienced
that here.

Just reviewing my landscape I find that I am not actually trying to run the
DTS Designer on the 64-bit server's client tools, but I am running it from
32-bit desktop installations that are connecting to the 64-bit servers. My
landscape has exactly the three cases that are supposed to cause the
problem, but no problem here. (Why not? Don't know.)

As the KB mentions, reinstalling SQL Server 2000 Enterprise Manager also
should allow you to edit DTS packages. Have you tried resaving them from
SEM 2000 then opening them again in SSMS 2005?

RLF

"Dick C." <nospam@devdex.com> wrote in message
news:eBYsjhmGIHA.3768@TK2MSFTNGP06.phx.gbl...
> Hi Russell,
>
> You wrote:
> In order to maintain the ability to edit these DTS packages, read:
> http://technet.microsoft.com/en-us/l.../ms143755.aspx. See the note
> on
> downloading theDTS package designer.
>
>
> Yes I have read this page before, and downloaded and installed the
> "Microsoft SQL 2000 DTS Designer Components" but it still doesn't allow
> me to open DTS Packages, it references a knowledge base article at
> http://support.microsoft.com/kb/917406 which talks about deleting a
> dependency in the SQLwb.exe.manifest file which I have also done. But I
> am still unable to even open/edit the DTS Packages on the SQL 2005
> 64-bit server.
>
> We are able to use DTSRUN with no problems on this box.
>
> -Dick
>
>
> *** Sent via Developersdex http://www.developersdex.com ***

Hi

Thanks to those who replied,

Well I have seen two sorts of failures on different machines. In the first
case it won't open the package at all It just comes up with the "You must
install the web download "Microsoft SQL 2000 DTS Designer Components". In
the second case it will pop up with the designer but then say you can't edit
the package.

Editing the SQLwb.exe.manifest file seems to in the second case.

But currently on our SQL 2006 64-bit installation it keeps doing the first
thing, (not even opening the designer), I have tried installing and
uninstalling the "Microsoft SQL 2000 DTS Designer Components" several times
(which might be part of the problem) Strangely the SQLwb.exe.manifest file
is off in a folder called Program Files (x86) or Program Files (32 bit) or
something like that. and if you completely clear the SQLwb.exe.manifest file
SMS (SQL Server Management Studio) will not start at all. which makes me
wonder if SMS is itself a 32-bit program.

Regarding Enterprise Manager, It seems to me the article said you could save
the DTS Package to a file (not to the SQL 2005 Server) which is of limited
usefulness since. we need to be able to execute the packages on the SQL 2005
server to see what might be failing.

We can kind of do this now by editing the packages from our 32-bit installs
on our desktops but of course file mappings are a bit of a problem as the D:
drive of the SQL Server is not the D: drive of the desktop PC.

I guess the big question I stll have is should it be possible to edit DTS
Packages on the 64-bit SQL Server 2005. All my googling has not provided a
definitive answer.

--
-Dick Christoph

"Russell Fields" <russellfields@nomail.com> wrote in message
news:%23OKZNOvGIHA.284@TK2MSFTNGP02.phx.gbl...
> Dick,
>
> Yes, I reviewed my notes and found that my response was colored by the
> first post. However, with regard to your on-going problem, I have not
> experienced that here.
>
> Just reviewing my landscape I find that I am not actually trying to run
> the DTS Designer on the 64-bit server's client tools, but I am running it
> from 32-bit desktop installations that are connecting to the 64-bit
> servers. My landscape has exactly the three cases that are supposed to
> cause the problem, but no problem here. (Why not? Don't know.)
>
> As the KB mentions, reinstalling SQL Server 2000 Enterprise Manager also
> should allow you to edit DTS packages. Have you tried resaving them from
> SEM 2000 then opening them again in SSMS 2005?
>
> RLF
>
> "Dick C." <nospam@devdex.com> wrote in message
> news:eBYsjhmGIHA.3768@TK2MSFTNGP06.phx.gbl...
>> Hi Russell,
>>
>> You wrote:
>> In order to maintain the ability to edit these DTS packages, read:
>> http://technet.microsoft.com/en-us/l.../ms143755.aspx. See the note
>> on
>> downloading theDTS package designer.
>>
>>
>> Yes I have read this page before, and downloaded and installed the
>> "Microsoft SQL 2000 DTS Designer Components" but it still doesn't allow
>> me to open DTS Packages, it references a knowledge base article at
>> http://support.microsoft.com/kb/917406 which talks about deleting a
>> dependency in the SQLwb.exe.manifest file which I have also done. But I
>> am still unable to even open/edit the DTS Packages on the SQL 2005
>> 64-bit server.
>>
>> We are able to use DTSRUN with no problems on this box.
>>
>> -Dick
>>
>>
>> *** Sent via Developersdex http://www.developersdex.com ***
>
>

Dick,

> Regarding Enterprise Manager, It seems to me the article said you could
> save the DTS Package to a file (not to the SQL 2005 Server) which is of
> limited usefulness since. we need to be able to execute the packages on
> the SQL 2005 server to see what might be failing.

You can use DTSRUN to run packages on SQL Server 2005 from disk as well. (My
policy is to always store the packages on disk and run them from there,
rather than storing the packages in msdb.)

DTSRUN /f filepathandname /n packagename


RLF