Post reply

SQL server agent job fail when run from scheduler, but run fine when start manually.

  • June 12, 2009 at 9:48 am

    #134995

    I am just wondering if anyone run in the followed problem... I have a 3 step job which 1st execute ssis package under SQL Server Agent account, 2nd run a batch script under proxy account, 3rd execute ssis package under SQL Server Agent account.

    When I go and manually start the job from ("Start Job at Step") it runs without any issues.

    When I enable the schedule it fails... on a batch script step...

    Batch script call gpg (encryption) and error I is public key is not found...

    Thanks,

    Pavel

  • June 26, 2009 at 7:45 am

    #1016027

    Ok, here is how the issue resolved if anyone run into it in a future... when import the keys with gpg it save them in a separate files under your profile... which not accessable via proxy account... sql server job agent run by sa... so what is needed is importing the public key under admin user on the server, be sure you edit the key and set trust to ultimate... otherwise the step may hang... After public key was imported under admin user... the job run without any issues.

Viewing 2 posts - 1 through 2 (of 2 total)

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