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.
| Author |
Topic |
|
bhaveshcjain
Starting Member
1 Post |
 Posted - 2009-09-17 : 05:30:28
|
| Hello,I have developed SSIS Package using 2008.which executes daily using sql job. I received below error in the shcedule job.MessageExecuted as user: . Microsoft (R) SQL Server Execute Package Utility Version 10.0.1600.22 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 7:42:35 AM Error: 2009-09-16 07:42:41.07 Code: 0xC0202009 Source: Contact Data Flow OLE DB Command 1 [1329] Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Transaction (Process ID 67) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.". End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 7:42:35 AM Finished: 7:43:04 AM Elapsed: 28.156 seconds. The package execution failed. The step failed.Please let me know why this error occured periodically.Regards,BJBhavesh Jain |
|
|
YellowBug
Aged Yak Warrior
616 Posts |
Posted - 2009-09-17 : 05:57:56
|
quote:
Transaction (Process ID 67) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction
Deadlocks can occur periodically, depending on resource usage/contention.Have you set DBCC TRACEON(1204,1222)? Is there any information in the SQL Server Errorlog?If not, you may want to enable the trace option to gather the deadlock information, so you can resolve the issue.Or you can use Profiler. |
 |
|
|
|
|
|
SSIS Package failed in SQL Job.