locked
Site Level Warning threhold reached, not sending messages to the event viewer RRS feed

  • Question

  • We have configured our content databases with the Site Warning Level at 20, max sites at 30.  Several of our databases now contain 23-25 site collections, but we do not see any warning messages written to the event viewer.  What is the event ID for the Site Warning Level messages, and how often should they be written to the event logs?

    Wednesday, July 20, 2011 11:57 AM

Answers

  • Hi TrentonB,

     

    Thanks for posting back.

     

    Please do as Mike said, restart the server and check whether the Event ID is displayed. Additionally, the event ID 6593 is fired only on the server hosting the Central Admin, it does not present in any other servers of the farm.

     

    If it persists, please provide more information about how many sites in the content databases when you set the “Site Warning Level”.

     

    There is a known issue that when you add a content database by using Central Administration or the stsadm –o addcontentdb command, if the value you specify in WarningSiteCount or the value that you specify in the MaximumSiteCount is less than or equal to the current number of sites in the content databases, the values that you specified are not used. Instead, the following values are set: WarningSiteCount = currentSiteCount + 500. It has fixed in Windows SharePoint Services 3.0 Cumulative Update Server Hotfix Package (Sts.msp):June 30, 2009, for more information, please refer to:

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

     

    Thanks,

    Qiao Wei

    Tuesday, July 26, 2011 12:10 PM
    Moderator

All replies

  • Hi TrentonB,

     

    Could you provide more information about how you configured the content database with the site level warning, the site level warning can be configured in CA at site level (Go to Central Administrator->Application Management->content databases, choose the database that needs to configure the site level warning).

     

    The Event ID for site level warnings is 6593, it logs the warning inside the “Event Log” and the message looks like:”The content database have exceeded the warning web site count, either change the content database website capacity settings or add more content database.”

     

    You will not get notified from SharePoint when the limit is crossed as all it does is logs the warning in the eventviewer.

     

    For more information about “site level warning notification”, please refer to:

    http://www.dzeee.net/sharepoint/post/2010/01/17/Site-Level-Warning-Notification.aspx

     

    Thanks,

    Qiao Wei

    Monday, July 25, 2011 12:07 PM
    Moderator
  • Qiao Wei,

    Thanks for your response.  We configured the database site level warnings through CenAdmin as you described.  We expected the behavior listed above, including the messages being written to the event viewer.  However, to date no events have been written to the event viewer indicating a warning, though several of our databases are now definitely over their warning level. 

    Monday, July 25, 2011 3:01 PM
  • did you do a stop / start in the meantime ?
    SP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx
    WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx
    Both also have links to extensive book lists and to (free) on-line chapters
    Monday, July 25, 2011 3:18 PM
  • Hi TrentonB,

     

    Thanks for posting back.

     

    Please do as Mike said, restart the server and check whether the Event ID is displayed. Additionally, the event ID 6593 is fired only on the server hosting the Central Admin, it does not present in any other servers of the farm.

     

    If it persists, please provide more information about how many sites in the content databases when you set the “Site Warning Level”.

     

    There is a known issue that when you add a content database by using Central Administration or the stsadm –o addcontentdb command, if the value you specify in WarningSiteCount or the value that you specify in the MaximumSiteCount is less than or equal to the current number of sites in the content databases, the values that you specified are not used. Instead, the following values are set: WarningSiteCount = currentSiteCount + 500. It has fixed in Windows SharePoint Services 3.0 Cumulative Update Server Hotfix Package (Sts.msp):June 30, 2009, for more information, please refer to:

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

     

    Thanks,

    Qiao Wei

    Tuesday, July 26, 2011 12:10 PM
    Moderator