Post reply

SSIS Package runs as a package but won't run in job scheduler

  • September 10, 2013 at 5:07 pm

    #298640

    I have a package that will not complete in the job scheduler, runs fine as a package.

    Part of the process was to delete a file on our network using the File System Task Editor delete file and when the job runs in the scheduler I get an error saying that the server does not have permissions. It runs fine from the server when I run the package.

    I changed it to rename the file instead of deleting it and now it says it can not find the file to rename it when I run it in the scheduler.

    I am at a total loss and am very new to doing all of this. Any help would be greatly appreciated as I am supposed to go on vacation in a week and a half and need for these to be running while I am gone. 🙂

  • September 11, 2013 at 1:06 am

    #1649120

    When you run it as a package it works because it runs under your credentials and I'm guessing your login has access to execute/write.

    When you run it from a job it executes as "SQL Service Agent". Does SQL Agent have access?

  • September 11, 2013 at 1:56 am

    #1649130

    possibly not working because , the sql server agent dont have the rights.!

    or,, if ur folder path is of network then it will not work under current authentication. for this you need to create a proxy account and use this to execute.

  • September 12, 2013 at 6:01 am

    #1649657

    The SQL Server Agent Account needs permissions on the network share and the directory where the file is.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply