Post reply

Run an SSIS Package Under a Different Account

  • July 15, 2010 at 7:23 pm

    #1193854

    Thank you Grey Cat,

    I did what you told me to, but the package still fails.

    the only way i can avoid the failure is to change the 'credential' password under security of the database.

    I guess i did not make it clear

    I found that whenever the user's password is changed in the windows operating system, i have to change the passward in the SQL server credentials too otherwise it will fail the package scheduled under the Sql Agent jobs.

    My case is - one of our system administrators just went ahead changed the password without telling me and all my packages failed, i had to let him reverse back the password (or i could have just changed the password in SQL security - credentials)

    And I wanted to know if there is another way to avoid this troublesome.

    cheers,

    Min

  • July 16, 2010 at 10:02 am

    #1194197

    I see. the password in credential has to be the correct account password. Sorry, but your admin has to inform you if the password has been changed.:-P

  • October 23, 2012 at 2:04 pm

    #1552059

    Great article. Used on a SSIS package for verifying addresses via the Melissa Data Contact Verify component against MS CRM contact addresses. Account running SQL agent did not have permissions to access data in the CRM db. This allowed me to setup a proxy with a known user and it worked like a champ.


    Gene A Scruggs
    American College of Emergency Physicians
    Technical Support Manager

Viewing 3 posts - 16 through 17 (of 17 total)

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