dbTalk Databases Forums  

SQL 2005 DTS

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss SQL 2005 DTS in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
doug
 
Posts: n/a

Default SQL 2005 DTS - 06-18-2009 , 06:58 PM






I have converted a sql 2000 dts job to sql 2005 SSIS (64 bit). The package
exports data to excel. I have the Run64BitRuntime project property set to
False and have been able to execute the package using the dtexecui.exe
utility. However, I am having problems running thsi package from a scheduled
job through the sql agent. I keep getting a error refenencing an invalid
path for my package. What is the correct syntax to run this as a scheduled
sql agent job?

Thanks in advance.

Reply With Quote
  #2  
Old   
Todd C
 
Posts: n/a

Default RE: SQL 2005 DTS - 06-19-2009 , 07:08 AM






Doug:
How did you 'install' the package to the server? Did you add it to the MSDB
node (in which case it is stored in the MSDB database) or did you add it to
the File System?

When executing via an SSIS instance or invoking from SQL Agent, you use
different Accounts, and therefore different permission sets. Make sure the
account under which is being executed under has proper permissions.

HTH
=====
Todd C


"doug" wrote:

Quote:
I have converted a sql 2000 dts job to sql 2005 SSIS (64 bit). The package
exports data to excel. I have the Run64BitRuntime project property set to
False and have been able to execute the package using the dtexecui.exe
utility. However, I am having problems running thsi package from a scheduled
job through the sql agent. I keep getting a error refenencing an invalid
path for my package. What is the correct syntax to run this as a scheduled
sql agent job?

Thanks in advance.

Reply With Quote
  #3  
Old   
doug
 
Posts: n/a

Default : - 06-19-2009 , 07:37 AM



The packaage was created by a sysadmin user, which is also the same user that
will be executing the job. It is saved on the file system. I have tried
calling the file by using the mapped drive letter
(D:\folder\folder\file.dtsx) and the unc path
(\\server\folder\folder\folder\file.dtsx) and get the same error either way.


"Todd C" wrote:

Quote:
Doug:
How did you 'install' the package to the server? Did you add it to the MSDB
node (in which case it is stored in the MSDB database) or did you add it to
the File System?

When executing via an SSIS instance or invoking from SQL Agent, you use
different Accounts, and therefore different permission sets. Make sure the
account under which is being executed under has proper permissions.

HTH
=====
Todd C


"doug" wrote:

I have converted a sql 2000 dts job to sql 2005 SSIS (64 bit). The package
exports data to excel. I have the Run64BitRuntime project property set to
False and have been able to execute the package using the dtexecui.exe
utility. However, I am having problems running thsi package from a scheduled
job through the sql agent. I keep getting a error refenencing an invalid
path for my package. What is the correct syntax to run this as a scheduled
sql agent job?

Thanks in advance.

Reply With Quote
  #4  
Old   
Todd C
 
Posts: n/a

Default : - 06-19-2009 , 07:59 AM



Doug:
I highly suggest you first install the package to the Integration Services
instance. There are several ways to do this. I prefer navigating to the
+Stored Packages > MSDB node under the SSIS instance in SQL Management Studio
and importing the package.
Then try running the package from there. After you get it to work there,
create your SQL Agent job to execute an SSIS package (instead of trying to
create a long T-SQL or shell command).

Can you copy the exact error message back here? Is it possible the package
is actually running, but something *inisde* the package cannot reconcile the
path?

Just some rambling thoughts, hope they help.
=====
Todd C


"doug" wrote:

Quote:
The packaage was created by a sysadmin user, which is also the same user that
will be executing the job. It is saved on the file system. I have tried
calling the file by using the mapped drive letter
(D:\folder\folder\file.dtsx) and the unc path
(\\server\folder\folder\folder\file.dtsx) and get the same error either way.


"Todd C" wrote:

Doug:
How did you 'install' the package to the server? Did you add it to the MSDB
node (in which case it is stored in the MSDB database) or did you add it to
the File System?

When executing via an SSIS instance or invoking from SQL Agent, you use
different Accounts, and therefore different permission sets. Make sure the
account under which is being executed under has proper permissions.

HTH
=====
Todd C


"doug" wrote:

I have converted a sql 2000 dts job to sql 2005 SSIS (64 bit). The package
exports data to excel. I have the Run64BitRuntime project property set to
False and have been able to execute the package using the dtexecui.exe
utility. However, I am having problems running thsi package from a scheduled
job through the sql agent. I keep getting a error refenencing an invalid
path for my package. What is the correct syntax to run this as a scheduled
sql agent job?

Thanks in advance.

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.