DTS not running as scheduled job

Hi
I have a DTS package that I can run manually without any problem but when I
try to run it as a scheduled job I get the following error msg:-
Executed as user: DOMAIN\accountname. The process could not be created for
step 1 of job 0x836FF304FA1D6A4C931D9992F6A10681 (reason: The system cannot
find the file specified). The step failed.
The DTS package was originally created under the domain\administrator
account and the SQL services are running under the domain\accountname
account. I thought the problem was related to the fact that the DTS package
was set up using the administrator account so it was recreated under the
domain\acccountname account, but the problem still exists.
Any ideas how to solve this?
ThanksHi
What drive/path is being accessed?
If it is a network path, via UNC, it should work. If it is a mapped drive
with a drive letter, until SQL agent is re-started, the drive is not visible
to it (assuming the drive was mapped when the DOMAIN\accountname was logged
into the console).
Make sure that the SQL Agent uses the same account as SQL Server service.
Regards
Mike
"jonjo" wrote:
> Hi
> I have a DTS package that I can run manually without any problem but when I
> try to run it as a scheduled job I get the following error msg:-
> Executed as user: DOMAIN\accountname. The process could not be created for
> step 1 of job 0x836FF304FA1D6A4C931D9992F6A10681 (reason: The system cannot
> find the file specified). The step failed.
> The DTS package was originally created under the domain\administrator
> account and the SQL services are running under the domain\accountname
> account. I thought the problem was related to the fact that the DTS package
> was set up using the administrator account so it was recreated under the
> domain\acccountname account, but the problem still exists.
> Any ideas how to solve this?
> Thanks|||Hi Mike
I didn't write the package but as far as I can see it is just copying data
from certain tables in one SQL db to another server. I don't think any mapped
drives are being used.
Both services are using the same account.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> What drive/path is being accessed?
> If it is a network path, via UNC, it should work. If it is a mapped drive
> with a drive letter, until SQL agent is re-started, the drive is not visible
> to it (assuming the drive was mapped when the DOMAIN\accountname was logged
> into the console).
> Make sure that the SQL Agent uses the same account as SQL Server service.
> Regards
> Mike
> "jonjo" wrote:
> > Hi
> >
> > I have a DTS package that I can run manually without any problem but when I
> > try to run it as a scheduled job I get the following error msg:-
> >
> > Executed as user: DOMAIN\accountname. The process could not be created for
> > step 1 of job 0x836FF304FA1D6A4C931D9992F6A10681 (reason: The system cannot
> > find the file specified). The step failed.
> >
> > The DTS package was originally created under the domain\administrator
> > account and the SQL services are running under the domain\accountname
> > account. I thought the problem was related to the fact that the DTS package
> > was set up using the administrator account so it was recreated under the
> > domain\acccountname account, but the problem still exists.
> >
> > Any ideas how to solve this?
> >
> > Thanks