Sharepoint Search Service Crashed after KB956716 update
Our networking guys installed this patch over the weekend on our only front-end sharepoint server: KB956716
http://support.microsoft.com/kb/956716
Then our search service stopped working.
When trying to search in any of our apps, we get this error: System.IndexOutOfRangeException: DisplayInAdminUI (stack info below)
I went to the Shared Services admin page and when I click on search options it just crashes.
I've also included the event viewer error below ...
Any ideas?
Thank,
Christopher
Event Type: Warning Event Source: ASP.NET 2.0.50727.0 Event Category: Web Event Event ID: 1309 Date: 12/30/2008 Time: 1:03:35 User: N / A Computer: VKSPS02 Description: Event ID: 3005 Message about event: an unhandled exception occurred. Event time: 12/30/2008 01:03:35 PM Event time (UTC): 12/30/2008 07:03:35 AM Event code: 90ade1cc6d5949a3ae2ea97afa5d75e6 Sequence of events: 19275 Event: 67 Event detail code: 0
Application Information: Scope: / LM / W3SVC / 1927250994 / Root-1-128751076993856152 Trust Level: WSS_Minimal Application Virtual Path: / Application Path: C: \ Inetpub \ wwwroot \ wss \ VirtualDirectories \ vktoday80 \ Machine Name: VKSPS02
Process Information: Process ID: 8136 Process Name: w3wp.exe Account Name: VIRCHOWKRAUSE \ SharePointSSPApp
Exception Information: Exception Type: IndexOutOfRangeException Exception Message: DisplayInAdminUI
Request information: Request URL: http://sitename.domain.net/searchcenter/Pages/peopleresults.aspx?k=lori Request Path: /searchcenter/Pages/peopleresults.aspx User Host Address: 172.30.202.56 User: VIRCHOWKRAUSE \ JF11767 Is Authenticated: True Authentication Type: NTLM Topic Account Name: DOMAINNAME \ SharePointSSPApp
: : 6 : DOMAINNAME\SharePointSSPApp : False : System.Data.ProviderBase.FieldNameLookup.GetOrdinal(String fieldName) System.Data.SqlClient.SqlDataReader.GetOrdinal( ) System.Data.SqlClient.SqlDataReader.get_Item ( ) Microsoft.Office.Server.Search.Query.ConsumerScopeCache.Refresh() Microsoft.Office.Server.Search.Query.ConsumerScopeCache.EnsureFresh() Microsoft.Office.Server.Search.Query.ScopeCache.TryGetScope(Guid siteGuid, Int32 id, ScopeInformation & scope) Microsoft.Office.Server.Search.Query.ScopeCache.TryGetSharedScope(Int32 id, ScopeInformation & scope) Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.SetPropertiesOnHiddenObject() Microsoft.Office.Server.Search.WebControls.PeopleCoreResultsWebPart.SetPropertiesOnHiddenObject() Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.OnPreRender(EventArgs e) Microsoft.Office.Server.Search.WebControls.PeopleCoreResultsWebPart.OnPreRender(EventArgs e) System.Web.UI.Control.PreRenderRecursiveInternal() System.Web.UI.WebControls.WebParts.WebPart.PreRenderRecursiveInternal() System.Web.UI.Control.PreRenderRecursiveInternal() System.Web.UI.Control.PreRenderRecursiveInternal() System.Web.UI.Control.PreRenderRecursiveInternal() System.Web.UI.Control.PreRenderRecursiveInternal() System.Web.UI.Control.PreRenderRecursiveInternal() System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Information about a specific event:
For more information, see the Help and Support Center at http://go.microsoft.com/fwlink/events.asp .
Server error in application "/".
DisplayInAdminUI Description: An unhandled exception was thrown during the execution of the current web request. Review the stack trace for more information about the error and how it occurs in your code.
Exception Details: System.IndexOutOfRangeException: DisplayInAdminUI
Source error:
An unhandled exception was thrown during the execution of the current web request. Information about the origin and location of an exception can be identified using the exception stack trace below.
Stack trace:
[IndexOutOfRangeException: DisplayInAdminUI] System.Data.ProviderBase.FieldNameLookup.GetOrdinal (String fieldName) +1433771 System.Data.SqlClient.SqlDataReader.GetOrdinal (string_name) +102 System.Data.SqlClient.String_name +102 System.Data.SqlClient.SqlDataReader12 Microsoft.Office.Server.Search.Query.ConsumerScopeCache.Refresh () +1241 Microsoft.Office.Server.Search.Query.ConsumerScopeCache.EnsureFresh () +58 Microsoft.Office.Server.Search.Query.ScopeCache.Try siteGetScope (Guid siteGetScope , Int32 id, ScopeInformation & scope) +75 Microsoft.Office.Server.Search.Query.ScopeCache.TryGetSharedScope (Int32 id, ScopeInformation & scope) +68 Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.SetPropertiesOnHidden2503bject () Microsoft.Office.Server.Search.WebControls.PeopleCoreResultsWebPart.SetPropertiesOnHiddenObject () +41 Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.OnPreRender (EventArgs e) +1977 Microsoft.Office.Server.Search.WebControls.PeopleCoreResultsWebPart.OnPreRender (EventArgs e) +11 System.Web.UI.Control.PreRender + System.Web.UI.Control.PreRender + SystemRe86cursiveInternalInternal .WebControls.WebParts.WebPart.PreRenderRecursiveInternal () +62 System.Web.UI.Control.PreRenderRecursiveInternal () +170 System.Web.UI.Control.PreRenderRecursiveInternal () +170 System.Web.UI.Control.InPreternalRender +Recursive 170 System.Web.UI.Control.PreRenderRecursiveInternal () +170 System.Web.UI.Control.PreRenderRecursiveInternal () +170 System.Web.UI.Page.ProcessRequestMain (Boolean includeStagesBeforeAsyncPoint, Boolean includeStages +20Async)OnPreRender (EventArgs e) +11 System.Web.UI.Control.PreRenderRecursiveInternal () +86 System.Web.UI.WebControls.WebParts.WebPart.PreRenderRecursiveInternal () +62 System.Web.UI.Control.PreRenderRecursive0Internal () +17 System.Web.UI.Control.PreRenderRecursiveInternal () +170 System.Web.UI.Control.PreRenderRecursiveInternal () +170 System.Web.UI.Control.PreRenderRecursiveInternal () +170 System.Web.UI.Control.PreRenderRecursiveInternal () +170 System.Web.UI.Page.ProcessRequestMain (Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2041OnPreRender (EventArgs e) +11 System.Web.UI.Control.PreRenderRecursiveInternal () +86 System.Web.UI.WebControls.WebParts.WebPart.PreRenderRecursiveInternal () +62 System.Web.UI.Control.PreRenderRecursiveInternal () +17 System.Web.UI.Control.PreRenderRecursiveInternal () +170 System.Web.UI.Control.PreRenderRecursiveInternal () +170 System.Web.UI.Control.PreRenderRecursiveInternal () +170 System.Web.UI.Control.PreRenderRecursiveInternal () +170 System.Web.UI.Page.ProcessRequestMain (Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2041PreRenderRecursiveInternal () +170 System.Web.UI.Control.PreRenderRecursiveInternal () +170 System.Web.UI.Control.PreRenderRecursiveInternal () +170 System.Web.UI.Page.ProcessRequestMain (Boolean includeStagesBeforeanAsyncPoint)PreRenderRecursiveInternal () +170 System.Web.UI.Control.PreRenderRecursiveInternal () +170 System.Web.UI.Control.PreRenderRecursiveInternal () +170 System.Web.UI.Page.ProcessRequestMain (Boolean includeStagesBeforeanAsyncPoint)
Version Information: Microsoft .NET Framework Version: 2.0.50727.1433; ASP.NET Version: 2.0.50727.1433
source to share
I had a similar experience with a corrupt search index (caused by accidentally restarting the index server) and unfortunately the only way to fix this is to stop the search services and start them again. This is done via Central Admin-Operations-Topology and Services-Services on the servers.
Not that we are getting this error - the IndexOutOfRangeException error you are getting has to do with going out of scope or something while displaying the UI, not doing something with the search index. However, the behavior you are describing is the same as we do - search returns errors and cannot access the search configuration scope in the SSP.
Note that this is not like stopping and starting a Windows service - stopping the search service removes it from the index server and restarts it, so you will lose your search index and have to do a full crawl to get it back. Therefore, be sure that you have no other options and are prepared to lose your search index before going down this path.
source to share
Ok, I broke down and opened a support ticket w / M $. They solved the problem pretty quickly. We use a local table to push our patches to our servers. After the patch was installed, the guys from the networks did not start the sharepoint product configuration wizard. My guess is that this should be done on any binary update that most updates fix.
So, we ran the setup wizard, it didn't work. Then it tries to run it using the command line:
C: \ Program Files \ Common Files \ Microsoft Shared \ Web Server Extensions \ 12 \ BIN> PSCO NFIG -CMD UPGRADE -INPLACE B2B -FORCE -WAIT
That didn't work either ... but only in the last step of restarting the service (found this information in the log). So, we started the services manually, reset iis. and it WORKS!
I think our networking guys need to learn how to run Wixard or PSconfig on the command line.
source to share