SSIS process fails as a job but not when manually executed

  • Hi

    I have a SSIS process that is failing on a data pump step when it is executed as a job. The error is due to a conversion from date/time to a string. However, when I run the same process manually on my PC it does not fail. I also had a look at the actual date columns to see if there were any invalid dates, but could not find any.

    Does anyone perhaps know as to why the process fails when executed as a job and not when it's manually executed?

  • Could it be that the server's default date format is dd/mm/yyyy and your PC it is mm/dd/yyyy (or vice versa)?

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

  • No, the date format of the server has not changed as other processes that uses a date would also have failed. So I'm not sure why this is specific process is always failing.

  • private.2010.skipp (11/26/2012)


    No, the date format of the server has not changed as other processes that uses a date would also have failed.

    Check the default language for the SQL Server login that the job is running under. That can be different to the default language for the server entire.

    Hmm, if you're reading from a text file, the chances are the date format at issue may actually be associated with the Windows login that the job is running under. Checking that would be a good idea as well.

Viewing 4 posts - 1 through 3 (of 3 total)

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