Post reply

SSIS execute process (cURL) doesn't fail doesn't execute

  • March 3, 2017 at 12:50 pm

    #335508

    Hello!
    Like half the SSIS posts out there I am struggling with "but it worked in dev...."
    I have an SSIS package that uses an execute process task  to run a curl command on a remote server.  Running it from VS on my local machine runs fine.  Running it as my SSIS Proxy account from VS works fine.  Logging into the server and manually executing the command works fine, both under my own credentials and the proxy credentials.  When I deploy it out to the sql server it runs, with no errors, but the file is never sent to the destination. 
    Any suggestions?  I tried having my IT dep't set permissions to "everyone" to see if there is some permissions error with the SQL Agent or some other account I don't realize is being used, but that didn't resolve it either.

    thanks in advance!

  • March 3, 2017 at 2:55 pm

    #1931636

    szona - Friday, March 3, 2017 12:50 PM

    Hello!
    Like half the SSIS posts out there I am struggling with "but it worked in dev...."
    I have an SSIS package that uses an execute process task  to run a curl command on a remote server.  Running it from VS on my local machine runs fine.  Running it as my SSIS Proxy account from VS works fine.  Logging into the server and manually executing the command works fine, both under my own credentials and the proxy credentials.  When I deploy it out to the sql server it runs, with no errors, but the file is never sent to the destination. 
    Any suggestions?  I tried having my IT dep't set permissions to "everyone" to see if there is some permissions error with the SQL Agent or some other account I don't realize is being used, but that didn't resolve it either.

    thanks in advance!

    I have 2 thoughts:
    1 - is the SQL Server Agent Service account an AD account?  If not, then it might not be included in "everyone" (forget how that all works... been a while since I delved into windows permissions)
    2 - is it pulling data from a network share?  and if so, are you using the UNC name or drive letter?  Drive letter will likely fail.

    The above is all just my opinion on what you should do. 
    As with all advice you find on a random internet forum - you shouldn't blindly follow it.  Always test on a test server to see if there is negative side effects before making changes to live!
    I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.

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

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