locked
Timout Exception thrown by MOSS 2007 web application RRS feed

  • Question

  • Dear All,

    I have a SharePoint Farm with two front end servers , one application server also working as front end server (i.e holding the central admin and my applction), while my database is on a separte DB cluster.

    We are getting the following alerts very frequently nowadays from a operation monitor software instlled on these servers:

     

    System.ApplicationException: This operation returned because the timeout period expired. (Exception from HRESULT: 0x800705B4)

    System.Threading.ReaderWriterLock.AcquireReaderLockInternal(System.Int32 millisecondsTimeout)
    Microsoft.SharePoint.Utilities.SPInitializeOnceLock..ctor(System.Boolean readerLock)
    Microsoft.SharePoint.Utilities.SPInitializeOnceLock.AcquireReaderLock()
    Microsoft.SharePoint.Administration.SPVolatileCache`2[K,V].GetValue(K key)
    Microsoft.SharePoint.Administration.SPCache`2[K,V].get_Item(K key)
    Microsoft.SharePoint.Utilities.SPUtility.MakeBrowserCacheSafeLayoutsUrl(System.String name, System.Boolean localizable)
    Microsoft.SharePoint.WebControls.ScriptLink.Register(System.Web.UI.Page page, System.String name, System.Boolean localizable, System.Boolean defer, System.String language)
    Microsoft.SharePoint.WebControls.ScriptLink.Register(System.Web.UI.Page page, System.String name, System.Boolean localizable, System.Boolean defer)
    Microsoft.SharePoint.WebControls.ScriptLink.Register(System.Web.UI.Page page, System.String name, System.Boolean localizable, System.Boolean defer, System.String language)
    Microsoft.SharePoint.WebControls.ScriptLink.OnInit(System.EventArgs e)
    System.Web.UI.Control.InitRecursive(System.Web.UI.Control namingContainer)
    System.Web.UI.Control.InitRecursive(System.Web.UI.Control namingContainer)
    System.Web.UI.Control.InitRecursive(System.Web.UI.Control namingContainer)
    System.Web.UI.Control.InitRecursive(System.Web.UI.Control namingContainer)
    System.Web.UI.Control.InitRecursive(System.Web.UI.Control namingContainer)

    System.Web.UI.Page.ProcessRequestMain(System.Boolean includeStagesBeforeAsyncPoint, System.Boolean includeStagesAfterAsyncPoint)

    Can you please help me identifying the cause and get rid of this error:

    Thanks,

    Sami

     

     

     

     

     

    Saturday, December 4, 2010 8:13 AM

Answers

  • Did you recently install any new 3rd party tools or do some custom dev?

    How is SQL holding up?  Maybe there is something on the SQL side that you can investigate.


    --Paul Galvin, Computer Generated Solutions (CGS)
      Microsoft MVP - SharePoint
      Blogging @ http://www.mstechblogs.com/paul
      Twitter @ http://www.twitter.com/pagalvin
    • Marked as answer by Leoyi Sun Thursday, December 23, 2010 6:44 AM
    Saturday, December 4, 2010 12:59 PM
  • I have resloved this issue. I had installed the Aug 2010 Cumlative update from MOSS on the three servers in the Farm but not the WSS CU for AUG 2010. After installing the WSS CU for AUG 2010, we are not having any deadlocks or locks on the DB with the grace of Allah.

    This may not be the best Answer but it has resloved our issue and may help someone cause.

     

    Sami

     

    • Marked as answer by Sami Khan Thursday, December 30, 2010 12:33 PM
    Thursday, December 30, 2010 12:33 PM

All replies

  • Did you recently install any new 3rd party tools or do some custom dev?

    How is SQL holding up?  Maybe there is something on the SQL side that you can investigate.


    --Paul Galvin, Computer Generated Solutions (CGS)
      Microsoft MVP - SharePoint
      Blogging @ http://www.mstechblogs.com/paul
      Twitter @ http://www.twitter.com/pagalvin
    • Marked as answer by Leoyi Sun Thursday, December 23, 2010 6:44 AM
    Saturday, December 4, 2010 12:59 PM
  • Thanks Paul,

    Actually I haven't install any thrid party tools nor I have done any recent develpment, I am not responsible for DB operations and there is a separte DBA looking at the MOSS DBS.

    According to DBA , the database have heavy locks due to the following SharePoint store procedures at different times:

    proc_AddListItem

    Deadlocks

    Share point3

    SP

    proc_DefragmentIndices

    Deadlocks

    Share point4

    SP

    QMChangeSiteDiskUsedAndContentTimestamp

    Deadlocks

    Share point5

    SP

    SecUpdateSiteLevelSecurityMetadata

    Deadlocks

    Share point6

    SP

    proc_GetAuditMaskOutput

    Deadlocks

    Share point7

    SP

    SecUpdateUserToken

    Deadlocks

    Share point8

    SP

    proc_GetTpPageMetaData

    Deadlocks

    Share point9

    SP

    proc_UpdateListItem

    Deadlocks

    Share point10

    SP

    proc_DefragmentIndices

    This may be the cause of the timeout exception.

    Can you please help to elobrate more about this?

    Sami

     

    Sunday, December 5, 2010 8:23 AM
  • I have resloved this issue. I had installed the Aug 2010 Cumlative update from MOSS on the three servers in the Farm but not the WSS CU for AUG 2010. After installing the WSS CU for AUG 2010, we are not having any deadlocks or locks on the DB with the grace of Allah.

    This may not be the best Answer but it has resloved our issue and may help someone cause.

     

    Sami

     

    • Marked as answer by Sami Khan Thursday, December 30, 2010 12:33 PM
    Thursday, December 30, 2010 12:33 PM