hello all,

i have on esubscripotion which sends report as an email to my 4 clients 

now , when  i check status on reportserver somtimes , it shows 4 processed of 4 total ; 0 errors 

sometimes 4 processed of 4 total ; 2 errors and sometimes 4 processed of 4 total ; 3 errors 

can any one please help me on this ..

and email to single client never hadany issue ..

Hello all,

actually , it is deadlock issue 

and when i create trace in SQL profiler on my server database and select deadlock graph event 

and it is caught ..

have a look on image ..

but i dont understand how to resolves issue using this ...

Hi ,

i have a subscription which is sending emails to my multiple clients ..

subscription runs fine when there are only two recepients and gets errored as i list 3rd recepient in To  field.

i found that 

, it is deadlock issue 

and when i create trace in SQL profiler on my server database and select deadlock graph event 

and it is caught ..

have a look on image ..

but i dont understand how to resolves issue using this ...

can anyone narrate this graph to identi

Hi Dilip Patil,

According to your description, you configured subscription to send emails to multiple users, it works fine when there are only recipients, if there are three recipients, you will get deadlock error.

A deadlock occurs when two system server process IDs (SPIDs) are waiting for a resource and neither process can advance because the other process is preventing it from getting the resource.

For Node 1, an exclusive (X) lock is being held by SPID 66 on an index KEY on the object. Node 2 shows that an exclusive (X) lock is being held by SPID 65 on an index key on the same object. For each node, is the Requested By section, which details any resource requests that cannot be granted, due to blocking. For Node 1, we can see that that SPID 66 is waiting for a shared read lock on the index key (it is blocked by the X lock held by SPID 65). For Node 2, we can see that SPID 65 is waiting to acquire a shared read on the index key (it is blocked by the X lock held by SPID 66).

In this case, we need to kill one of the SPID to free the resources and allow the other SPID to continue.

For detail information about Handling Deadlocks and Minimizing Deadlocks in SQL Server, please refer to the following document:
https://www.simple-talk.com/sql/database-administration/handling-deadlocks-in-sql-server/
https://technet.microsoft.com/en-us/library/ms191242(v=sql.105).aspx

If you have any more questions, please feel free to ask.

Thanks,
Wendy Fu

Thanks wendy fu for reply,

actually, i have resolve this by identifying a key lock and creating a cover index on the column 

and its not happening a key lock nomore ..

but you can help me for the similar issue i have raised here

Click