DTS package permissions errors when transferring pkgs btw servers



Hi -

I have a DTS problem that's been giving me fits and am hoping someone here
can help.

I am transferriing a SQL Server 2000 database sever from one machine to
another. Neither machine is mine. The destination machine is to be the same
configuration & operate similarly to the source machine. The source machine
is Win2k and the destination is Win2k3. The source machine is an old dying
32 bit machine, and the destination is a Dell 2950 64 bit machine (with the
same SQL Server 32 bit media installed [automatically] - in a Program Files
(x86) folder on the 64 bit machine - and yes, I've resolved all the db data
file path issues.)

I've copied & restored the db's, synced all the SIDs, synchronized the SQL
Server service and SQL Server Agent logins, (they use mixed mode security -
and the SQL Server service logs in through a local userid that has admin
priveledges). it works fine, except ..My problem is the old DTS packages..

There are 40 odd DTS packages, which I transferred (by using Save As for the
local packages, to the new machine) from the source to the destination
machine, while I was logged in as the same user as the SQL Server service
uses. They run fine whe I'm logged in as that admin user. When I'm logged
into SQL Server as a user with less rights (but who still has dbo in the
relevant dbs + master & msdb), and I run the packages through query analyzer
using a proc that uses OACreate & specifies the package, etc, then I get
package errors, and little or no error messages.

I have read vague references to the need to configure a "default login" in
the registry, associated with DCOM/DTS/SQL Server to get packages that do
I/O to run correctly. Here's the link:

http://support.microsoft.com/kb/q298725/

Yes, I have checked/created the shares, and like I said, all the SQL Server
login SIDs are synced throughout all the dbs. The packages do not have
package userid's (no owner, no operator, etc. ) or passwords defined. They
are simple packages that reat a text file on a share, and import the text
file into a table in a local db. I know, they should be re-written , but
just not now. What I need now is to get DTS permissions configured properly.

Can anyone clarify the pro




.



Relevant Pages

  • RE: DTS Sucess but fails to go to next step when scheduled
    ... odbc connection to an Oracle database in my dts packages. ... My particular situation involves pulling data from an Oracle 9database into ... SQL Server 2000 -- when the Oracle database was in 8i it worked much faster ...
    (microsoft.public.sqlserver.dts)
  • Re: "Class not registered" error when opening DTS package...
    ... Build packages in Designer ... Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) ... www.SQLDTS.com - The site for all your DTS needs. ... Building a Package in the DTS Designer ...
    (microsoft.public.sqlserver.dts)
  • Re: Upgrading DTS to SSIS
    ... You cannot run packages outside of BI Development Studio on a client computer that does not have Integration Services installed, and the terms of your SQL Server 2005 licensing may not permit you to install Integration Services on additional computers. ... SQL Server 2005 Integration Services (SSIS) is now a server component and is not redistributable to client computers in the same manner that the components required for SQL Server 2000 Data Transformation Services (DTS) were redistributable. ...
    (microsoft.public.sqlserver.dts)
  • Re: Editing DTS Packages on a 64-bit SQL Server 2005 installation
    ... The tips for running 32-SSIS packages can be extended to running 32-bit DTS ... store your DTS packages in a 64-bit SQL Server database. ... have tried installing the Web download it says to install but then I get ...
    (microsoft.public.sqlserver.setup)
  • SQL Server 2005 Workgroup Edition und SSIS
    ... The Business Intelligence Development Studio option installs the Integration ... and you cannot run packages outside of BI Development Studio. ... Mit dem SQL Server 2005 Workgroup Edition werden Teile der Integration ...
    (microsoft.public.de.sqlserver)