Error Description differs when logged with Redirect Rows compared with Debug mode

Hi,

Can any one please tell me how to get the complete error description for example when i dont Redirect Row for Error in OLEDB Source i get a detailed error message with column name as

[RCheck [385]] Error: There was an error with input column "CHECK_STATUS" (456) on input "OLE DB Destination Input" (398). The column status returned was: "The value could not be converted because of a potential loss of data.".

But when I set Redirect Row for error and use the Script component to log them into a Table with ErrorDescription based on ErrorColumnID it only gives me this.

The data value cannot be converted for reasons other than sign mismatch or data overflow.

Thanks

Sat

Can't make the FailComponent and RedirectRow error messages the same with stock OLEDB source component.

If you want to actually redirect AND get the original provider error message that you would get in Fail Component mode, well, that component has yet to be written by Microsoft.

Instead, as you're seeing, when performing redirection using the OLEDB source; only the generic ErrorCode => generic textual description is exposed via ComponentMetaData.GetErrorDescription().

With a custom component of course, you can amend error outputs with additional columns, which is exactly what I have had to do to circumvent this problem.

Error connecting to OLEDB for DB2

I'm attempting to configure a new Microsoft OLE DB Provider for DB2 connection using the provided Data Access Tool and Wizard. I'm configured for DB2\MVS TCP/IP and have my Catalog and other defaults set. When I go to connect I get the following:

Could not connect to data source 'New Data Source':
An internal network library error has occurred. A network level conversational protocol error has occurred. SQLSTATE: HY000, SQLCODE: -343

The port I've configured is what is used when we use the IBM OLE DB and ODBC drivers. Where can I look to see what the problem is?

Thanks,

Mike

I'm moving your thread to the Data Access forum as you'll have a greater chance of having an OLEDB question answered.|||

Hi,

some OLEDB providers have the functionality for logging implemented which can be turned on with a flag on the client side, this should give you more information about the error you ar egetting. The Provider flags are very specific so you should look in the documentation of the used provider.

HTH, jens Suessmeyer.

http://www.sqlserver2005.de

error column

Hi,

There is an error output from one oledb destination which causes error to another which populated a table called tblFailedRows.

I have mapped the errorcolumn to the errorcolumn in tblFailedRows.

When looking at the errorcolumn in tblFailedRows I see just numbers not the column name.

How do I get the column name that causes the error?

Thanks

Here's a thread with information on this:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1509836&SiteID=1