I would like to know if someone can help me figure out what this message means.
Here is a little information about the server setup, we have two virtual servers one is our sharepoint server (SPWEB) and the other is our SQL server (SPSQL). Both servers are running Windows Server 2008 R2.
This is the error message that the sharepoint administrator gets when he tries to open a SP list withing the website.
08/29/2012 15:38:20.68 w3wp.exe (0x1120) 0x0F4C SharePoint Foundation Logging Correlation Data xmnv Medium Site=/ ec265a10-5e02-4c43-8de9-90
08/29/2012 15:38:20.71 w3wp.exe (0x1120) 0x0F4C SharePoint Foundation Runtime tkau Unexpected System.NullReferenceExcept
ion: Object reference not set to an instance of an object. at Microsoft.SharePoint.Appli
() at Microsoft.SharePoint.Appli
s e) at ASP._layouts_listedit_aspx
entArgs e) at System.Web.UI.Control.Load
) at System.Web.UI.Page.Process
int, Boolean includeStagesAfterAsyncPoi
08/29/2012 15:38:20.71 w3wp.exe (0x1120) 0x0F4C SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (GET:http://x.x.x.x:7000/procardauditfindingsnotice/_layouts/listedit.aspx?List=%7B819D0A08%2D9431%2D471C%2DA32F%2D3472084355AA%7D
)). Execution Time=51.2294160291322 ec265a10-5e02-4c43-8de9-90
08/29/2012 15:38:30.52 OWSTIMER.EXE (0x04C4) 0x0EDC SharePoint Foundation Monitoring nasq Medium Entering monitored scope (Timer Job job-diagnostics-blocking-q
08/29/2012 15:38:30.52 OWSTIMER.EXE (0x04C4) 0x1264 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (Timer Job job-diagnostics-sql-memory
This problem started to happen after our Windows administrator pushed a MS patch update to all the windows server. The Microsoft update (patch) was applied a few hours before this error started to happen.
About 30 minutes later the SP administrator informed me that he could not reach the SP website. I confirmed this and it appears that the Microsoft patch may have caused more harm then good.
After, several hours of doing an emergency restore of both servers SPWEB and SPSQL we finally have both servers back online.
So, I have two questions, first it is logical to think that what caused the problem was the patch update, do you agree?
If so then how do I determine which MS update caused the problem?
Besides doing a DBCC CHECKDB on the databases which I already have done, is there a MS SP application that the SP administrator (SP Doctor?) can use to check if the SP application is working normally?