SSIS Error message - SQL Server Forums

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2008 Forums

SSIS and Import/Export (2008)

SSIS Error message

Author

Topic

Groenigen
Starting Member

3 Posts

Posted - 2011-07-11 : 03:27:45

Hi all,

my collegue came across the following error:

ErrorDescription MachineName UserName EventDateTime
Error: SSIS Error Code DTS_E_THREADFAILED. Thread "WorkThread0" has exited with error code 0xC0209029. There may be error messages posted before this with more information on why the thread has exited. S30-0042 BANK\uSYS-UC-P 05/07/2011 11:07
Error: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "tlbDimTransactions" (61) failed with error code 0xC0209029. The identified component returned an error from the ProcessInput method. 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 messages posted before this with more information about the failure. S30-0042 BANK\uSYS-UC-P 05/07/2011 11:07
Error: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR. The "input "OLE DB Destination Input" (74)" failed because error code 0xC020907B occurred, and the error row disposition on "input "OLE DB Destination Input" (74)" specifies failure on error. An error occurred on the specified object of the specified component. There may be error messages posted before this with more information about the failure. S30-0042 BANK\uSYS-UC-P 05/07/2011 11:07
Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80004005 Description: "[DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation.". S30-0042 BANK\uSYS-UC-P 05/07/2011 11:07

SQL meets network. I am a network engineer myself, but I couldn't find any weird things in the communication path between the two databases. Anyone here knows something more about those SQL error messages?

Thanks in advance

Lumbago
Norsk Yak Master

3271 Posts

Posted - 2011-07-11 : 06:25:05

I'm not 100% sure but a very qualified guess would be that the connection string to the destination database where the table "tlbDimTransactions" resides is configured wrong. Probably a typo or something in the server name...or maybe it's controlled my a package configuration that doesn't work.

- Lumbago
My blog-> http://thefirstsql.com/2011/07/08/how-to-find-gaps-in-identity-columns-at-the-speed-of-light/

Groenigen
Starting Member

3 Posts

Posted - 2011-07-11 : 07:17:23

Lumbago,

at first I also thought of a authorisation issue of some kind. But the thing is, that the job rerunned, and everything went ok. But why did it go wrong the first time, and not the second?

(because the job ran ok afterwards, there is no hurry, I just want to figure out what was wrong).

Thanks for your reply.

russell
Pyro-ma-ni-yak

5072 Posts

Posted - 2011-07-11 : 12:53:01

The network connection dropped. Could be a loose cable, bad NIC, switch, Windows error...could be too much network traffic at the time.

Groenigen
Starting Member

3 Posts

Posted - 2011-07-13 : 01:24:58

Russel,

thanks, we will check the connection.

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources