Sarah Catherall

My feedback

  1. 6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  3 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Sarah Catherall commented  · 

    Any further word on this? I'm running SSIS 2017, and even when I run the package myself (right click execute) because the package kicks off an Execute Process Task, that task is unable to access the assigned identity's user profile (where we are holding important credentials!). I even created a super simple package to prove this that just executes a .bat file containing the below. When run via Visual Studio the package finds the cmdkey list just fine, when run via SSIS hosting manually it doesn't.

    C:\Windows\System32\whoami.exe >> \\myserver\Experiments\whoami.txt
    C:\Windows\System32\cmdkey.exe /list >> \\myserver\Experiments\whoami.txt

    The output of which I then get is

    mydomain\myaccount

    Currently stored credentials:

    * NONE *

Feedback and Knowledge Base