![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
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. |
#3
| |||
| |||
|
|
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. |
#4
| |||
| |||
|
|
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. |
![]() |
| Thread Tools | |
| Display Modes | |
| |