locked
Overdue Task reminder email issue RRS feed

  • Question

  • I am not sure why my initial post was deleted by moderators, since I do not know the reason, I can't fix it and re-posting it again.

    Issue I am having is around overdue task reminder emails. 

    I've copied a content DB from my PROD environment to DEV and attached to a web app, about 7 months ago. I have a MOSS 2007 farm both in PROD and DEV.

    So I have at hand, http://dev-projects.xxxx.com and http://projects.xxxx.com

    Now fast forward to yesterday, at 2:50pm my users started receiving "overdue task" reminder emails for tasks that were created 3 years ago from the DEV instance which are obviously not valid.

    I have no idea what's going on, and need the community's help on this. 

    Ali 

     


    • Edited by alisalih Wednesday, January 18, 2012 2:45 PM clarification.
    Wednesday, January 18, 2012 2:44 PM

All replies

  • Hello Ali,

     

    Thank you for your question.

     

    I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.

     

    Thank you for your understanding and support.

     

    Thanks,

    Wayne Fan

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact  tnmff@microsoft.com.


    Wayne Fan

    TechNet Community Support

    Thursday, January 19, 2012 3:10 AM
  • Hi Ali,

    I believe that the overdue task emails are search bsaed alerts. In short they are triggered when the search crawler runs over them, checks them against it's index and sees if an alert has already been sent, and determines that an alert is due. When you migrated the content DB to a different environment as far as the search crawler/index was concerned they were new content and any alerts due should be sent.

    To prevent the problem, after migrating the DB you could have disabled search based alerts, run the search crawler and then re-enabled the alerts so that current/future content would be picked up correctly.

    See: http://technet.microsoft.com/en-us/library/cc261943(office.12).aspx

    I think that at this point all of the invalid alerts will have been sent, so no current action should be required.

     

    Thursday, January 19, 2012 11:57 AM
  • Hello Steven. 

    Thank you for your response. Currently, my SSP doesn't have this function active. It is set to "Currently inactive." Additionally, I checked the crawl logs around the time frame +/- 2 hours, and I do not have any crawling done at that time for this specific web app...

    Any other ideas?

    Regards,

    Ali.


    • Edited by Mike Walsh FIN Thursday, January 19, 2012 1:37 PM Unnecessary full quote removed
    Thursday, January 19, 2012 1:32 PM
  • Hello alisalih,

    Can you provide these details to further narrow down the cause of the erroneous emails:


    - What build are the Dev and Prod test farms at?

    - Is SQL at the same build in each of the environments?

    - Are there any errors in the application event logs that are related to SQL?

    - Is this an out of the box workflow, or is it custom?

    - Are the emails being sent for one workflow, or multiple workflows?


    Now, a couple of ideas for stopping them:


    - Clear the configuration cache on the web front end server(s) using the steps in this KB: http://support.microsoft.com/kb/939308

    - Run stsadm -o sync -listolddatabases 0 (http://technet.microsoft.com/en-us/library/cc263196(office.12).aspx) to see if there are out of sync records in the database.

    - If you receive anything but 0 in the stsadm output, you should run stsadm -o sync -deleteolddatabases 0, which essentially causes the SSP to synchronize with the site collection.


    I will look forward to hearing your results.


    Thanks,

    Bob


    • Edited by Bob_Rainey Tuesday, January 24, 2012 5:20 PM Edit
    Tuesday, January 24, 2012 5:19 PM
  • - What build are the Dev and Prod test farms at?
    DEV:  12.0.0.6557
    PROD: 12.0.0.6554 
    - Is SQL at the same build in each of the environments?
    Yes.
    - Are there any errors in the application event logs that are related to SQL?
    There are errors, but not related to SQL.
    - Is this an out of the box workflow, or is it custom?
    This is a task created by an OOB workflow. 
    - Are the emails being sent for one workflow, or multiple workflows?
    One workflow. Emails are overdue task reminders.
    Here are the results for stsadm -o sync -listolddatabases 0
    Shared Service Provider SSPExternal
    ID: b908399c-7b2a-4bc9-99a7-83ed42a8a5af  Synchronized: 9/13/2011 11:00:01 AM
    ID: 87640180-86a2-4c45-ba4b-9144af0549ae  Synchronized: 9/13/2011 11:00:01 AM
    Shared Service Provider SSPPrimary
    ID: aa48861f-7e6c-45d7-a67c-0047e6779149  Synchronized: 1/24/2012 3:00:01 PM
    ID: 48b72897-49ca-44c0-b661-008dfda3ab7a  Synchronized: 1/24/2012 3:00:01 PM
    ID: ef809428-ff52-4681-89f3-0b18ce12a717  Synchronized: 1/24/2012 3:00:01 PM
    ID: cd57f30d-bdae-488f-88de-177e08166e7c  Synchronized: 1/24/2012 3:00:00 PM
    ID: 6e98a957-9c09-47f8-b510-25aa5cc78628  Synchronized: 1/24/2012 3:00:01 PM
    ID: 23ac5647-b902-4ebd-93a8-2f07bb55ca37  Synchronized: 1/24/2012 3:00:00 PM
    ID: e03b1ee8-b45c-4656-97bb-466df0808284  Synchronized: 1/24/2012 3:00:01 PM
    ID: e98ed430-78b0-4d6a-94eb-5100cec9b55e  Synchronized: 1/24/2012 3:00:02 PM
    ID: c7f698c0-3529-412c-b6fa-54a8d5e0d668  Synchronized: 1/24/2012 3:00:01 PM
    ID: 2a1b3633-d7dd-4134-987d-5d7fdaa59496  Synchronized: 1/24/2012 3:00:01 PM
    ID: 5f09f03b-2d4e-4428-a356-63c6b90ff281  Synchronized: 1/24/2012 3:00:02 PM
    ID: 2abe6330-6da0-437c-b184-68c70b46b857  Synchronized: 1/24/2012 3:00:01 PM
    ID: e38835a6-917a-489a-91f2-70d1c700eae0  Synchronized: 1/24/2012 3:00:00 PM
    ID: 0ecb8914-9514-4251-920a-bc743e06b6d0  Synchronized: 1/24/2012 3:00:03 PM
    ID: e59b07b0-f256-4a5d-8acf-bedd94bd5c8c  Synchronized: 11/15/2011 2:00:03 PM
    ID: 03ebc92b-6b88-4879-bbf1-bf3110798206  Synchronized: 1/24/2012 3:00:02 PM
    ID: e40a90ef-bf6b-4c20-9d2c-c5728b5324ff  Synchronized: 1/24/2012 3:00:01 PM
    ID: 79827711-be62-40ab-b603-c8842aa5ecf6  Synchronized: 1/24/2012 3:00:01 PM
    ID: 319035ca-b688-4055-8cd1-da750262032b  Synchronized: 1/24/2012 3:00:00 PM
    ID: cdc8d24c-3df9-45ec-aa45-dd97ca877dd0  Synchronized: 1/24/2012 3:00:00 PM
    ID: aae81d17-f969-43cd-b874-efd9898a235d  Synchronized: 1/24/2012 3:00:01 PM
    Tuesday, January 24, 2012 8:21 PM
  • Hi,

    You can delete those tasks to get rid of these.


    Thanks, Rahul Rashu
    Wednesday, January 25, 2012 3:37 AM
  • Hi,

    You can delete those tasks to get rid of these.


    Thanks, Rahul Rashu
    Point is to find out why they are triggering an alert, 2 years after randomly. I can just delete the farm and get rid of these too, but would not be a viable solution, isn't it?
    Wednesday, January 25, 2012 4:40 AM
  • Hi ALi

    During My research on you issue

    I found there is Kb article that talks about ths issue

    http://support.microsoft.com/kb/972569

    "In Microsoft Office SharePoint Server 2007, you start an out-of-the-box approval workflow and set a due date. As soon as the due date passes, you edit the workflow and then delete the due date. Immediately a task overdue e-mail is sent out to the approvers with the original due date. The approvers continue to receive a task overdue e-mail (referencing the original due date) weekly until the workflow is canceled, a future due date is set or the workflow is approved. "

    Do check the Kb

    hope so this helps you

    thanks

    Wednesday, January 25, 2012 5:55 AM

  • Hi ALi

    During My research on you issue

    I found there is Kb article that talks about ths issue

    http://support.microsoft.com/kb/972569

    "In Microsoft Office SharePoint Server 2007, you start an out-of-the-box approval workflow and set a due date. As soon as the due date passes, you edit the workflow and then delete the due date. Immediately a task overdue e-mail is sent out to the approvers with the original due date. The approvers continue to receive a task overdue e-mail (referencing the original due date) weekly until the workflow is canceled, a future due date is set or the workflow is approved. "

    Do check the Kb

    hope so this helps you

    thanks

    This is an interesting find. It is interesting because I have  12.0.0.6557 which is beyond that June 2009 CU, and issue should be handled already....Also, copy operation took place 7months ago, still can't find why 7 months later, only in DEV these alerts triggered...
    Wednesday, January 25, 2012 10:45 AM
  • Hi Ali,

    I apologize for the length of time that has passed since my last post.  Were you able to complete the recommended step of clearing the configuration cache?

    - Clear the configuration cache on the web front end server(s) using the steps in this KB:http://support.microsoft.com/kb/939308

    If this does not resolve the issue, I would recommend opening a case with the SharePoint support team to get to the bottom of the overdue task emails.

    Best Regards,

    Bob

    Thursday, March 1, 2012 2:25 PM
  • Hello Bob.

    I have no had a chance to Clear cache yet, however it is in my todo list.

    Hardest part of this issue is; This behaviour didn't repeat itself since the last time. So, I do not know if any change at this point can be verified as a solution.

    Thanks for the help!

    Ali.

    Thursday, March 1, 2012 2:29 PM