December 30, 2014 at 6:48 am
I have a job (lets call it CEOdata) which periodically will deadlock with a communication buffer resource. I have set up a retry on the step (retry 1 time after 10 minutes) which seemed to prevent the job from failing. There are high level reports that run later in the morning which depend on CEOdata running and updating a table.
I also set up a notification so that I get an email if the job fails. I was thinking that if the retry was not successful, I'd get an email and could take the necessary steps to resolve the issue before the morning reports run. The email notification was set up after the retry was set up.
This morning when CEOdata ran, it failed with a message indicating (I've condensed it here) TCP Provider:The specified Network Name is no longer available OLE DB Provider 'SQLXXXXxx' for linked server 'YYYYYYServer' returned message 'Communication link failure'
A retry was not attempted and I don't understand why. 30 minutes after this failure, I reran it and all was well. Did the email notification preempt the retry?
It would be nice if the retry would be attempted prior to a notification email being sent.
Thanks for any insight...
December 30, 2014 at 7:16 am
Did the failure occur on the same step on which you set up the retry?
John
December 30, 2014 at 7:17 am
Yes it did...
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply