Post reply

IS Package running C# Script logging file name is csv file. Works fine is ISSIS but doesnt log all files when set up as an overnight job

  • December 2, 2014 at 5:14 am

    #397720

    Hi there,

    Im just in the middle of testing this issue but I wondered if anyone else had seen anything like this?

    I have an IS Package. There is a script task that runs through all files in subdirectories and logs the file name in a csv file.

    If I run it in IS it always records every file name.

    I had it set up as an overnight job and it ran last night. There were 320 files but only 2 of them was logged.

    I just ran the package again manually and it worked. I thought Id check to see if there were any known reasons for this before I carried on testing?

    Debbie

  • December 2, 2014 at 5:46 am

    #1762013

    May I ask what you mean by 'IS' in this:

    f I run it in IS it always records every file name.

    Could it be a permissions issue?

  • December 2, 2014 at 6:10 am

    #1762025

    Integration Services.

    Hmmmm I shouldnt think its permissions. I have all the right permissions set on all the folders the job needs to access. But I could be wrong. Im going to test the job again tonight to see what happens.

  • December 2, 2014 at 6:34 am

    #1762039

    Debbie Edwards (12/2/2014)

    Integration Services.

    Hmmmm I shouldnt think its permissions. I have all the right permissions set on all the folders the job needs to access. But I could be wrong. Im going to test the job again tonight to see what happens.

    Nine times out of ten, when people have a task which works OK except for when it is run as a SQL Agent job, the problem is that the SQL Agent user does not have sufficient permissions.

  • December 2, 2014 at 6:36 am

    #1762040

    Its certainly something to put forward when I do some further testing on this. Thanks for that!

    Debbie

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

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