14,494 questions
Source: "Microsoft DB2 OLE DB Provider" Hresult: 0x80040E14 Description: "A TCPIP socket error
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 21%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBH%3C/text%3E%3C/svg%3E)
Bilal H. Bhatt
136
Reputation points
Hello,
We are getting below error while executing a SSIS job
Error: 2023-08-21 20:40:04.93 Code: 0xC0202009 Source: Data Flow Task 21 OLE DB Source [161] Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E14. An OLE DB record is available. Source: "Microsoft DB2 OLE DB Provider" Hresult: 0x80040E14 Description: "A TCPIP socket error has occured (10054): An existing connection was forcibly closed by the remote host. ". End Error Error: 2023-08-21 20:40:04.93 Code: 0xC0047038 Source: Data Flow Task 21 SSIS.Pipeline Description: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on OLE DB Source returned error code 0xC0202009. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 7:10:00 PM Finished: 8:55:39 PM Elapsed: 6338.06 seconds. The package execution failed.
Please help
SQL Server Other
{count} votes
-
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator2023-08-22T21:53:06.2333333+00:00 Have you checked the SQL Server errorlog for error messages that correlate to this message in time?
-
ZoeHui-MSFT 41,491 Reputation points2023-08-23T07:31:06.42+00:00 Hi @Bilal H. Bhatt,
Could you please use ODBC Driver to connect to DB2 for a try?
-
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator
2023-08-23T20:59:39.4766667+00:00 Have you checked the SQL Server errorlog for error messages that correlate to this message in time?
Oops. I did not pay attention to that this was the DB2 provider. I guess then that you need to look in the DB2 errorlog or what diagnostics they have.
Does the error occur directly on connection or does it appear right in the middle of the execution?
-
Bilal H. Bhatt 136 Reputation points
2023-11-13T04:45:07.9366667+00:00 Hello,
I am facing same issue intermittently .. The SQL Logs looks fine, no errors there
This error is coming during the execution
Please suggest
Sign in to comment
Sign in to answer