Hello,
I have a package that copies data FROM an MS Access database table to a SQL Server 2005 table. 'Run64BitRunTime' has been set to 'False'. The package has been saved to SQL Server. I have a Job that runs the package using an operating system command. The following is the command syntax:
“C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\dtexec.exe” /SQL "\Rebates\Rebates_TotalSecurity" /SERVER bwdbfin1 /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING E
I created the package on a machine other than bwdbfin1. I can run the package from Visual Studio. I can run the package from Integration Services. I have sysAdmin rights on bwdbfin1. I've tried running the job using two different proxy accounts and the sql agent account. I have the location of the Access database. No matter what I do, the Job fails with the following error:
The process could not be created for step 1 of job 0xD947EF76ACD96340B12279FEDDC580CE (reason: The system cannot find the file specified). The step failed.
I have an identical package that copies data TO an Access database. The database addressed in that package and this package are in the same location. The 'CreatorName' of both packages is the same. I have logging enabled for every category, but nothing is written to the sysdtslog90 table when the Job runs. I set up error output in the DataFlow task, and have also tried to 'ignore' errors. I have searched the forum, done a web search, and I can't find a reason for the failure.
Is dtexec the file that is not found? If that were the case, then why can a Job run my other package?
Any ideas?
Thank you for your help!
cdun2