none
Collaboration Site Collection Deleting Itself

    Question

  • I have a collaboration site with its own site collection. For some reason, it keeps being deleted. It happened all of a sudden and does so every week. None of the other site collections have this issue. We have removed all permissions so that users can no longer delete the site or the collection, only admins. We also verified that the auto delete feature is set to 60 days and 4 notifications, and no notifications are being sent. Nothing appears in the logs to show that it has been deleted. I was told that because SharePoint Designer is built on FrontPage web server extensions, that a delete would not show up in the logs. Now, there is in IIS for the web application properties in the HTTP Headers tab the enable or disable content expiration. This is set to expire after 365 days. However, as we keep recreating the site collection and restoring the data from backup, this shoudl reset itself? I would think that this would not affect the site, as the SharePoint delete and notification feature would override.

    Does anyone have any idea how and why a site collection would delete itself? It is a huge mystery. Any help in figuring this out is greatly appreciated.
    Friday, February 13, 2009 6:53 PM

Answers

  • Hi,

    The issue happened in this site collection only, I wonder if the site was marked as Deleted by the SharePoint.

     

    Please run the Store Procedure: “exec proc_enumsitesfordeadwebcheck” on the content database hosted the site collection in the SQL Server, You will find some web sites data are listed in the result.

     

    Please locate the site collection by Title and FullUrl, then check whether the DeadWebNotifyCount is equals to 0.

     

    If the DeadWebNotifyCount is greater than to 0, which mean the notices have been sent X times and the site collection will be deleted soon.

     

    If you want to avoid the site collection to be deleted, you can go to "http://the_site_collection_url/_layouts/useconfirmation.aspx”,

    Then run “exec proc_enumsitesfordeadwebcheck” again to see if the DiffTodayCertDate and DeadWebNotifyCount change to 0.

     

    Let me know the result if possible.

    -lambert


    Lambert Qin | Microsoft Online Support Engineer | How to ask a question in the forum (http://support.microsoft.com/kb/555375) | Posting is provided "AS IS" with no warranties, and confers no rights. |
    Tuesday, February 17, 2009 7:11 AM

All replies

  • I have never heard of something like this.

    You seem to have ruled out the automatic delete.

    Is there any chance that someone is going in and doing this manuallY?
    --Paul Galvin of EMC Consulting, New York area Microsoft MVP - SharePoint Blogging @ http://feeds.feedburner.com/PaulGalvinsSharepointSpace Twitter @ http://www.twitter.com/pagalvin
    Saturday, February 14, 2009 10:18 PM
  • Hi,

    The issue happened in this site collection only, I wonder if the site was marked as Deleted by the SharePoint.

     

    Please run the Store Procedure: “exec proc_enumsitesfordeadwebcheck” on the content database hosted the site collection in the SQL Server, You will find some web sites data are listed in the result.

     

    Please locate the site collection by Title and FullUrl, then check whether the DeadWebNotifyCount is equals to 0.

     

    If the DeadWebNotifyCount is greater than to 0, which mean the notices have been sent X times and the site collection will be deleted soon.

     

    If you want to avoid the site collection to be deleted, you can go to "http://the_site_collection_url/_layouts/useconfirmation.aspx”,

    Then run “exec proc_enumsitesfordeadwebcheck” again to see if the DiffTodayCertDate and DeadWebNotifyCount change to 0.

     

    Let me know the result if possible.

    -lambert


    Lambert Qin | Microsoft Online Support Engineer | How to ask a question in the forum (http://support.microsoft.com/kb/555375) | Posting is provided "AS IS" with no warranties, and confers no rights. |
    Tuesday, February 17, 2009 7:11 AM