Scheduled Job

  • Hi To all,

    I have a DTS Package that calls an executable file.

    This executable file renames a report and then post the renamed file into an FTP server.

    When I Right-click/"Execute Package" my DTS Package, the renamed report is successfully posted in FTP server, but when triggered by a scheduled job, posting to ftp fails but the report was renamed. Have tried to re-create the scheduled job, but the same thing happens. FYI, exe file was built using vb6.0

    Any idea, anyone?

    Thanks,

    Renan

  • Perhaps a security issue of sqlagent. What is its windowsaccount? Local machine, ...

  • Thanks Jo. yes, its LocalMachine.

    But FYI, not all scheduled jobs behave like this. Only few of them.

    Here's a little background of our DTS Package. May be it'll help... There is a need to recreate all our DTS Package, prior to that, exe file was stored on C:\, but now it's on different drive. After moving these files, this specific DTS Package fails to post the report in FTP server

  • Is the exe on a local drive (E:...)

    or a network drive \\otherserver\myexe (not accessable by local machine)?

  • It's accessible, Jo. I have tried to run MyExe manually, and it renames and posts the report to FTP server.

    Also, the new drive is on the same machine. But I don't have much idea how this drive (where myExe is now located) was attached to our server. What I know for now is that there's a data portal(third party) between localMachine and the new drive.

  • ... hmmm ... the SQL Agent runs as LocalService ... you can execute the package under your Windows Credentials with the target on another server ... try using a Domain User account for the SQL Server and Agent services. This account needs to be a Local Administrator on the SQL Server plus additional rights to the network location where you are putting the file.

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

  • [font="Verdana"]Hi Renan,

    Since you are a windows user I hope your ID will be available in SQL with necessary privileges. Hence change the job owner to your ID and check whether the job succeeds! [/font]

  • Thanks for your replies.

    Anyways, I just did a work around since we really need to have our report posted. I added another Execute Process Task that calls a separate batch file.

    Regard,

    Renan

  • What do you have the owner set as in your schedueld task?

    e.g. A few of our jobs go a bit skew if we don't use a SA acct..

  • Thanks Janine.

    Yes under SA account since in our prod all jobs are owned by this account.

    regards,

    Renan.

Viewing 10 posts - 1 through 9 (of 9 total)

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