Post reply

SSIS Package failing as a job

  • April 30, 2009 at 5:09 am

    #203458

    Hi,

    I have a SSIS package that works perfectly fine when i run it on my machine.But when i deployed it as a job on SQL Server it is failing with DTS_E_INDUCEDTRANSFORMFAILUREONERROR.

    I would appreciate if someone could tell me why could this happen?

    Thanks,

    Shishir.

  • April 30, 2009 at 5:43 am

    #986580

    What does the package do?

    Can you paste the detailed error message?

  • April 30, 2009 at 5:45 am

    #986585

    post the error messages.

    Quite often when a job runs fine locally and does not work on the server, it comes down to permission issues on the data sources/destinations. So this might be a good place to begin your investigations.

  • April 30, 2009 at 8:30 am

    #986689

    Hi Phil,

    Mine is a simple SSIS package that takes data from Sybase and dumps it into SQL Server.Here is the snapshot of the detailed error message for your consideration.

    The point is that this SSIS package works perfectly fine on my machine but it is only throwing up this error when i am running it as a SQL Server Agent Job.

    Regards,

    Shishir.

  • April 30, 2009 at 6:53 pm

    #987102

    Wow, felt like I was downloading a movie as I was waiting for that huge screen-shot to appear 🙂

    There is a very strong suggestion that there is a problem with the 'Contract' column - I've seen this error before and it was related to truncation of data (input bigger than output).

    I have no idea why you would not see this error in BIDS. Are you using exactly the same data?

    I suggest that you try setting up a redirect, so that you can see which records are creating the problems. From that, you should be able to work out why.

    Phil

  • April 30, 2009 at 10:28 pm

    #987142

    Hi Phil,

    Thanks for the reply.Actually i was able to solve the issue.This link helped me in debugging the problem : http://social.technet.microsoft.com/Forums/en-US/sqlintegrationservices/thread/9169fd30-0057-4a01-a33e-04db7017e9dd/

    Basically my target machine had Adapative Server Enterprise ODBC driver which is probably a non-compliant ODBC driver as per the above document.So i added Sybase ASE ODBC Driver to the target machine and ran the SSIS package again and it worked fine.

    Thanks for all your help.

    Regards,

    Shishir.

  • April 30, 2009 at 10:38 pm

    #987143

    Well done!

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

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