January 11, 2009 at 11:49 pm
Hi,
Can anyone help me in deciphering the below erroelog code.
2009-01-11 21:52:12.57 spid4 Node:2,0
2009-01-11 21:52:12.57 spid4 Port: 0x802ce100 Xid Slot: -1, EC: 0xabf43600, ECID: 0 (Coordinator), Exchange Wait Type :e_etypeClose,0
2009-01-11 21:52:12.57 spid4 Coordinator: EC = 0xabf43600, SPID: 61, ECID: 0, Not Blocking,0
2009-01-11 21:52:12.57 spid4 Consumer List::,0
2009-01-11 21:52:12.57 spid4 Consumer: Xid Slot: 0, EC = 0xa7e0c0c0, SPID: 61, ECID: 1, Blocking,0
2009-01-11 21:52:12.57 spid4 Consumer: Xid Slot: 1, EC = 0x3403e0c0, SPID: 61, ECID: 4, Blocking,0
2009-01-11 21:52:12.57 spid4 Consumer: Xid Slot: 2, EC = 0x33ffc0c0, SPID: 61, ECID: 6, Blocking,0
2009-01-11 21:52:12.57 spid4 Consumer: Xid Slot: 3, EC = 0xa79a40c0, SPID: 61, ECID: 8, Blocking,0
2009-01-11 21:52:12.57 spid4 Consumer: Xid Slot: 4, EC = 0x3401e0c0, SPID: 61, ECID: 7, Blocking,0
2009-01-11 21:52:12.57 spid4 Consumer: Xid Slot: 5, EC = 0xa79c60c0, SPID: 61, ECID: 5, Blocking,0
2009-01-11 21:52:12.57 spid4 Consumer: Xid Slot: 9, EC = 0xa7de20c0, SPID: 61, ECID: 3, Blocking,0
2009-01-11 21:52:12.57 spid4 Consumer: Xid Slot: 13, EC = 0xa7f840c0, SPID: 61, ECID: 2, Blocking,0
2009-01-11 21:52:12.57 spid4 Producer List::,0
2009-01-11 21:52:12.57 spid4 Producer: Xid Slot: 6, EC = 0x3492a0c0, SPID: 61, ECID: 17, Blocking,0
2009-01-11 21:52:12.57 spid4 Producer: Xid Slot: 7, EC = 0x39ff60c0, SPID: 61, ECID: 20, Blocking,0
2009-01-11 21:52:12.57 spid4 Producer: Xid Slot: 8, EC = 0x3493a0c0, SPID: 61, ECID: 23, Blocking,0
2009-01-11 21:52:12.57 spid4 Producer: Xid Slot: 10, EC = 0x5a6040c0, SPID: 61, ECID: 18, Blocking,0
2009-01-11 21:52:12.57 spid4 Producer: Xid Slot: 11, EC = 0xa79ac0c0, SPID: 61, ECID: 24, Blocking,0
2009-01-11 21:52:12.57 spid4 Producer: Xid Slot: 12, EC = 0xa79d40c0, SPID: 61, ECID: 21, Blocking,0
2009-01-11 21:52:12.57 spid4 Producer: Xid Slot: 14, EC = 0x3495c0c0, SPID: 61, ECID: 22, Blocking,0
2009-01-11 21:52:12.57 spid4 Producer: Xid Slot: 15, EC = 0x349120c0, SPID: 61, ECID: 19, Blocking,0
2009-01-11 21:52:12.57 spid4 ,0
2009-01-11 21:52:12.57 spid4 -- next branch --,0
2009-01-11 21:52:12.57 spid4 ,0
2009-01-11 21:52:12.57 spid4 ,0
2009-01-11 21:52:12.57 spid4 Node:2,0
2009-01-11 21:52:12.57 spid4 Port: 0x802ce100 Xid Slot: -1, EC: 0xabf43600, ECID: 0 (Coordinator), Exchange Wait Type :e_etypeClose,0
2009-01-11 21:52:12.57 spid4 Coordinator: EC = 0xabf43600, SPID: 61, ECID: 0, Not Blocking,0
2009-01-11 21:52:12.57 spid4 Consumer List::,0
2009-01-11 21:52:12.57 spid4 Consumer: Xid Slot: 0, EC = 0xa7e0c0c0, SPID: 61, ECID: 1, Blocking,0
2009-01-11 21:52:12.57 spid4 Consumer: Xid Slot: 1, EC = 0x3403e0c0, SPID: 61, ECID: 4, Blocking,0
2009-01-11 21:52:12.57 spid4 Consumer: Xid Slot: 2, EC = 0x33ffc0c0, SPID: 61, ECID: 6, Blocking,0
2009-01-11 21:52:12.57 spid4 Consumer: Xid Slot: 3, EC = 0xa79a40c0, SPID: 61, ECID: 8, Blocking,0
2009-01-11 21:52:12.57 spid4 Consumer: Xid Slot: 4, EC = 0x3401e0c0, SPID: 61, ECID: 7, Blocking,0
2009-01-11 21:52:12.57 spid4 Consumer: Xid Slot: 5, EC = 0xa79c60c0, SPID: 61, ECID: 5, Blocking,0
2009-01-11 21:52:12.57 spid4 Consumer: Xid Slot: 9, EC = 0xa7de20c0, SPID: 61, ECID: 3, Blocking,0
2009-01-11 21:52:12.57 spid4 Consumer: Xid Slot: 13, EC = 0xa7f840c0, SPID: 61, ECID: 2, Blocking,0
2009-01-11 21:52:12.57 spid4 Producer List::,0
2009-01-11 21:52:12.57 spid4 Producer: Xid Slot: 6, EC = 0x3492a0c0, SPID: 61, ECID: 17, Blocking,0
2009-01-11 21:52:12.57 spid4 Producer: Xid Slot: 7, EC = 0x39ff60c0, SPID: 61, ECID: 20, Blocking,0
2009-01-11 21:52:12.57 spid4 Producer: Xid Slot: 8, EC = 0x3493a0c0, SPID: 61, ECID: 23, Blocking,0
2009-01-11 21:52:12.57 spid4 Producer: Xid Slot: 10, EC = 0x5a6040c0, SPID: 61, ECID: 18, Blocking,0
2009-01-11 21:52:12.57 spid4 Producer: Xid Slot: 11, EC = 0xa79ac0c0, SPID: 61, ECID: 24, Blocking,0
2009-01-11 21:52:12.57 spid4 Producer: Xid Slot: 12, EC = 0xa79d40c0, SPID: 61, ECID: 21, Blocking,0
2009-01-11 21:52:12.57 spid4 Producer: Xid Slot: 14, EC = 0x3495c0c0, SPID: 61, ECID: 22, Blocking,0
2009-01-11 21:52:12.57 spid4 Producer: Xid Slot: 15, EC = 0x349120c0, SPID: 61, ECID: 19, Blocking,0
2009-01-11 21:52:12.57 spid4 Victim Resource Owner:,0
January 12, 2009 at 2:12 am
It looks like it may have to do with deadlocks. What traceflags do you have enabled? What version of SQL?
Please post in the appropriate forum next time, not just anywhere.
This post has been reported to the moderator with a request to move it.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 12, 2009 at 2:20 am
Hi Gail,
Sorry for posting it in wrong location.
this is related to SQL server 2000.
i just open the dbcc trace.(“DBCC TRACEON (3605, 1204))
January 12, 2009 at 9:28 am
Moved to SQL 2000 forum.
what is the issue you are having or are you just looking for information?
January 15, 2009 at 7:46 am
There is a sheduled job in my application......which runs on daily basis.but one in around two weeks it get failed. on the basis of the output file we found that the job was failed due to deadlock .please below find the detail of out file:
the job failed because the “Transaction (Process ID 58) “was deadlocked on lock. The communication buffer resources with another process and has been chosen as the deadlock victim.
for tracing the cause for the deadlock we open the DBCC trace flags.and recieve the error log mentioned in the first message.
but, now we are not able to trace out the information on the basis of the log.
the only information that we got is the name of DB.
Colud you please suggest us how to get the information from the log mentioned in the first message.
January 15, 2009 at 8:00 am
There's nothing there that makes any sense and certainly nothing that points to a cause for a deadlock. I've never heard of a deadlock on a communication buffer before.
Maybe give Microsoft's customer support a shout on this one?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply