How to log "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.".

  • Hi All,

    I am using custom error loging method to log SSIS errors. I am using "System::ErrorDescriptionsystem variable for logging the error message. However when the package encounters error in Data Flow Task (DFT) then multiple entries are created: The error statement is usually 2nndntry rest all other entries are process related as stated below:

    Entry 1: "Multiple-step DB operation generated errors. Check each OLE DB status value, if available. No work was done.".

    Entry 2: Actual Reason for failure

    Entry 3 SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR. The "OLE DB Destination.Inputs[OLE DB Destination Input]" failed because error code 0xC0209077 occurred, and the error row disposition on "OLE DB Destination.Inputs[OLE DB Destination Input]" specifies failure on error. An error occurred on the specified object of the specified component. There may be error messagmessagesd before this with more information about the failure.

    Entry 4:SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessProcessInput on component "OLE DB Destination" (75) failed with error code 0xC0209029 while processing input "OLE DB Destination Input" (88). The identified component returned an error from the ProcessProcessInput. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messagemessages before this with more information about the failure.

    I do not want to create multiple entries ( 4 entries are created) for each DFT ?I need only 1 entry either all the error concatenated or only entry 2. How should I achieve this.

    Any help will be appreciated.

    Thanks,

    Sa.M

    any help is highly appreciated.

  • Is this just the "wordiness" of SSIS? That is, when an error occurs you see multiple error messages in the process tab. These are what is getting logged.

    Would it be possible to filter out the messages you're not interested in in your stored proc/code that writes the error to your table?

    Just thinking out loud,

    Rob

  • Even I thought abt that but The exact reason for failure unless we have a look at it cannot be done 🙁 .. Will try to see if i can find an alternative

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

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