SQL Server Developer Center > SQL Server Forums > SQL Server Security > Executing third party tool "textpipe" using SQL Server service account
Ask a questionAsk a question
 

QuestionExecuting third party tool "textpipe" using SQL Server service account

  • Tuesday, October 27, 2009 7:24 AMMMohsin Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi All,

    I have batch which triggers third party tool "textpipe". If I execute the batch script using my account, it works fine. However If I execute the same batch scripts using SQL Server service account, it never triggers.

    Batch scripts are executed using task scheduler jobs in windows 2008 enterprise server. When task scheduler jobs starts, I could see a tread (SPID) running in task manager but no action would takes place.

    I am confused and tried all sorts of option. Please let me know how I can resolve this issue.

    Also, I have granted full privleges to service account for textpipe.exe application.

    Thanks,
    -Mohsin

All Replies

  • Tuesday, November 03, 2009 9:11 AMChunSong Feng -MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hello Mohsin,

    This problem is related to a third party application, you'd better get help from your vendor or you may post a thread here: http://www.datamystic.com/forums/.

    Thanks for your understanding,


    ChunSong Feng
    Microsoft Online Community Support

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
  • Friday, November 06, 2009 1:56 AMMichael HotekModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    The problem you are having is security.  When you shell out and execute an external command, SQL Server almost never bubbles up a security violation through the command shell.  This is very simple to test.  RDP to the machine using the SQL Server service account.  Launch the application from a command line.  You should see some sort of security error.  Once you fix that security issue, you'll be able to launch the application from within SQL Server.

    You should also see a security error in the Windows Application Event Log.

    Mike Hotek BlowFrog Software, Inc. http://www.BlowFrogSoftware.com Affordable database tools for SQL Server professionals