Post reply

ssis script task throws error when run from sql agent job

  • November 19, 2013 at 10:29 am

    #1667498

    I am loosing hope, please respond. I am sure many people are using this in their ETL.

    Thanks.

    Forum User:cool:

  • November 19, 2013 at 12:52 pm

    #1667555

    You need to find out what the actual error message is.

    It should be output in the window at the bottom of the package designer (Output window) when you run the package in debug mode.

    If not, try adding a try ... catch round the code in your script task "Set FS File Parameters Script Task" and debug that - set a breakpoint in the code to view the error...

    MM


    select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);

  • Forum Etiquette: How to post Reporting Services problems
    • [/url]
  • Forum Etiquette: How to post data/code on a forum to get the best help - by Jeff Moden
    • [/url]
  • How to Post Performance Problems - by Gail Shaw
    • [/url]

  • November 20, 2013 at 6:03 am

    #1667759

    When I run the package in debug mode using Visual studio, it works fine, no errors.

    When I run it in a scheduled job in SQL Agent using a service account I get this error. I wrapped my code in the script task in a try catch block and I get "Access to the path ... denied", the error message is copied below. I have set everyone full control on the files and folders on E drive.

    Error Message:

    Executed as user: MyDomain\MyServiceAcct . Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 32-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 7:36:00 AM Error: 2013-11-20 07:36:04.36 Code: 0x00000000 Source: Set FSFileParameters Script Task My File Task Description: Access to the path '\\MyServer\E$\MyFiles\FSP\' is denied. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 7:36:00 AM Finished: 7:36:04 AM Elapsed: 3.588 seconds. The package execution failed. The step failed.

    Forum User:cool:

  • November 20, 2013 at 6:23 am

    #1667769

    Try using a UNC path rather than a mapped drive.

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

  • November 21, 2013 at 6:11 am

    #1668083

    I am using a UNC path, not a mapped drive.

    Forum User:cool:

  • November 21, 2013 at 6:41 am

    #1668097

    ForumUser3 (11/21/2013)

    I am using a UNC path, not a mapped drive.

    My apologies, I misread the error.

    Are you able to physically log in to the SQL Server server using the service account and try to access the file directly in Explorer?

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

  • November 22, 2013 at 9:45 am

    #1668476

    Sharing the folder solved the problem.

    Forum User:cool:

    • Viewing 7 posts - 16 through 21 (of 21 total)

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