views:

335

answers:

3

Hi

I have an ssis package that uses excel files. I am using the Run As with an admin account.

when I call it from a batch file it runs fine

"C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\DTExec.exe" /SQL "\SOME_SSIS_PACKAGE" /SERVER "MYSERVER,PORT" /DECRYPT "Password" /VALIDATE  /REPORTING E

when I schedule it as a job, it fails with the error message : 'The system cannot find the path specified'

what path are you trying to find ?

the excel file path is accessed like this : \\server\folder\template.xls when I'm logged on the server and punch in the address \\server\folder\template.xls the file is found

A: 

Actually, it is because the server calling the job doesn't have rights to the template.xls. The file resides on \ServerA but the ServerB calling the job may not be able to see it so check those rights.

ajdams
I'm running the batch file from the sql server running the job, why doesn't the batch file fail?The sql server running the job uses the 'Run As' with a domain admin account
freddoo
Hmm odd. Have you tried removing that particular job from SQLAgent and readding it?
ajdams
Yes I did remove the job and recreate it, still failling
freddoo
A: 

Bear in mind that Sql Server agent jobs run in the context of the user running the SQL Server Agent service (which is not the same service as SQL server).

You can also define your job to be executed in the context of a proxy account

river0
It's already running with a proxy account.I am using the Run As with an admin account.
freddoo
A: 

I am facing the issue now. By focussing into depth: even when I directly execute the command:

"C:\Program Files (x86)\Microsoft SQL Serve r\80\Tools\Binn\dtsrun.exe" -S"KFTUSOKTULVCE17" -U"voicetran_user" -P"voicetranu ser" -N"Pkg_Stg_Shpt_Ld_EUDI" -A"g_FeedFileName"="\KFTUSOKTULVCE17\Voice\Data\ Voice Application\Voice\SourceFiles\Shipment\Formatted\VOICE_20081124_093029_SH IPMENT_COM.TXT"

It was erroring out a 1 simple liner: "The system cannot find the path specified."

No clue as to where the issue could be.

Direct execution of the "Pkg_Stg_Shpt_Ld_EUDI" (as in the above command) works perfectly fine!

This works in Production but not in the Test environment. No obvious solution for me yet! :(

Thanks and regards, Sriram

Sri
Note that we've validated the above paths to be valid.
Sri