Discussion:
SQL 2005 DTS
(too old to reply)
doug
2009-06-18 23:58:01 UTC
Permalink
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.
Todd C
2009-06-19 12:08:01 UTC
Permalink
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
Post by doug
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.
doug
2009-06-19 12:37:01 UTC
Permalink
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.
Post by Todd C
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
Post by doug
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.
Todd C
2009-06-19 12:59:01 UTC
Permalink
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
Post by doug
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.
Post by Todd C
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
Post by doug
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.
Continue reading on narkive:
Loading...