Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

All! I have an issue that neither I nor the contractors that I have working for me have been able to figure out, and I'm hoping you all might be able to help me.

I have several users that are getting email notifications to complete tasks on workflows that have been completed or outright deleted. In most cases, the list item itself has been deleted as well (although not in all cases). In most cases, the links in the email lead to an error message saying that the item in question has been deleted.

Here is what I've tried so far -

I've looked in the recycle bin - There is nothing in it to recover. I have used SQL to try and find "orphaned" workflows. None exist. I thought perhaps the issue was due to the fact that I had disabled the Workflow Cleanup service so I turned it back on. It's been two weeks since I have done so and the ghost task notices are still going out.

I know that part of my issue here is a result of the fact that I didn't code these lists and workflows to prevent users from deleting items instead of properly completing the workflow and I'm working on fixing that now, but in the meantime I have got to find the source of these emails and kill them.

Any help would be greatly appreciated.

share|improve this question
    
Do the related tasks belonging to the workflow still exist? Typically that is what generates the emails. –  Richard Mar 29 '13 at 15:45
    
They do not. We can't find the tasks OR the list items. –  Michael C. McGreevy Mar 29 '13 at 17:03

1 Answer 1

We had this same issue happen twice last year for two different causes

  1. We had copied one of our production content databases back to QA for other work. Once it was in QA, it happily fired off alerts from the QA environment though the URLs themselves were the clue on this one
  2. We upgraded a web app from SharePoint 2007 to 2010 but left the SharePoint 2007 copy running in read-only mode for the purposes of comparison. When doing this, it still sent out workflow emails as if it were still a live production site and, since we changed the URLs to point to the new 2010 farm, it appeared to be a valid production email. However, looking through the SMTP headers on the emails themselves told us it was coming from the 2007 farm.

In both cases, changing the outbound SMTP server on the non production farm to a non-existent server name resolved the duplicate emails.

share|improve this answer
    
I've looked at all of the farms that we have running, and the data doesn't exist on any of them. No data in the development farms. –  Michael C. McGreevy Apr 5 '13 at 15:55
1  
Go into Outlook and open one of the alerts being sent then go to File - Properties - Internet Headers and copy that block of text to Notepad. You should see a few headers that start with "Received: " followed by a machine name. Those headers will tell you where the message is originating as well as the path it took to get to your Inbox. If it points back to your current farm then we are back at the original issue where there is a rogue workflow. If not, at least you will be able to trace down the machine. –  Dave Wise Apr 5 '13 at 16:01

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.