No its not in a farm. Yes i selected the server in the dropdown box.
Main Topics
Browse All TopicsI am getting this error after a c drive restore on our sharepoint server. Everything else works fine except for search. I keep getting that error. I noticed when i go into central administration and click on where i can view the services of my server it now says "Windows SharePoint Services Help Search" Where is used to say " Windows Sharepoint Services Search" Or something along those lines. Why did that change? Thanks
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Try restarting the service and check. Else go thru the last post on this forum if it helps: http://social.technet.micr
Can you try another search, note the exact time, then check if there are any events in the ULS logs (c:\program files\common files\microsoft shared\web server extensions\12\logs
Re the change in the name of the service, are you sure the name has changed? Are you using WSS or MOSS? I know that if you're using MOSS, the WSS search service gets named the WSS help search. It's exactly the same service, it's just that they rename it to differentiate it from the vastly better Office Server Search. It's called the Help search service by the way, because the only place it's used in MOSS is to search the online help files!!
Here is what I get in the logs. i searched at 1:01
10/19/2009 13:01:06.11 w3wp.exe (0x077C) 0x0630 Search Server Common GatherPI 0 Monitorable SearchDB GetSession failed application cdad17f6-98f5-4b12-8408-93
10/19/2009 13:01:06.11 w3wp.exe (0x077C) 0x0630 Search Server Common GathererSql 0 Monitorable GetManagedProperties: Failed in GetSession, Error is 0xc0041228 - File:d:\office\source\sear
10/19/2009 13:01:06.11 w3wp.exe (0x077C) 0x0630 Search Server Common Exceptions 0 Monitorable <Exception><HR>0xc0041228</HR><ei
10/19/2009 13:01:06.11 w3wp.exe (0x077C) 0x0630 Search Server Common Common 0 Monitorable Application cdad17f6-98f5-4b12-8408-93
10/19/2009 13:01:06.11 w3wp.exe (0x077C) 0x0630 Search Server Common Common 0 Monitorable Application cdad17f6-98f5-4b12-8408-93
10/19/2009 13:01:06.11 w3wp.exe (0x077C) 0x0630 Search Server Common Common 0 Monitorable CAppConfig::DoQuery, Application 'cdad17f6-98f5-4b12-8408-9
10/19/2009 13:01:06.11 w3wp.exe (0x077C) 0x0630 Search Server Common Exceptions 0 Monitorable <Exception><HR>0xc0041228</HR><ei
10/19/2009 13:01:06.11 w3wp.exe (0x077C) 0x0630 Search Server Common Common 0 Monitorable CAppConfig::GetProperty Exception caught. - File:d:\office\source\sear
10/19/2009 13:01:06.11 w3wp.exe (0x077C) 0x0630 Search Server Common Exceptions 0 Monitorable <Exception><HR>0xc0041228</HR><ei
10/19/2009 13:01:06.11 w3wp.exe (0x077C) 0x0630 Windows SharePoint Services Web Parts 89a1 Monitorable Error while executing web part: Microsoft.SharePoint.Searc
10/19/2009 13:01:06.11* w3wp.exe (0x077C) 0x0630 Windows SharePoint Services Web Parts 89a1 Monitorable ... exception stack trace --- at Microsoft.SharePoint.Searc
10/19/2009 13:01:06.11 w3wp.exe (0x077C) 0x0630 Windows SharePoint Services Web Parts 89a2 Monitorable InnerException 1: System.Runtime.InteropServ
10/19/2009 13:01:13.19 OWSTIMER.EXE (0x0A04) 0x10E8 Windows SharePoint Services General 0 Medium Entering MRU trim routine.
10/19/2009 13:01:13.19 OWSTIMER.EXE (0x0A04) 0x10E8 Windows SharePoint Services General 0 Medium Initial table size: 0 in 0 entries
10/19/2009 13:01:13.19 OWSTIMER.EXE (0x0A04) 0x10E8 Windows SharePoint Services General 0 Medium Final table size: 0 in 0 entries
10/19/2009 13:01:13.19 OWSTIMER.EXE (0x0A04) 0x10E8 Windows SharePoint Services General 0 Medium Exiting MRU trim routine.
I went and clicked stop within sharepoint central administration and got this error.
An update conflict has occurred, and you must re-try this action. The object SPSearchJobDefinition Name=SharePoint Services Search Refresh Parent=SPSearchService Name=SPSearch is being updated by TRICOUNTY\administrator, in the w3wp process, on machine TCHSQL. View the tracing log for more information about the conflict.
When i try to disable that in teh timer job defenition I get this error.
An update conflict has occurred, and you must re-try this action. The object SPSearchJobDefinition Name=SharePoint Services Search Refresh Parent=SPSearchService Name=SPSearch is being updated by TRICOUNTY\administrator, in the w3wp process, on machine TCHSQL. View the tracing log for more information about the conflict.
Have you followed the steps mentioned in the KB http://support.microsoft.c
Also ensure that you run through the KB on every SharePoint server.
I followed that article and it seemed to get me farther. Now I can stop the search service. When I try to start it I get this error.
WSS_Search_TCHSQL on np:\\.\pipe\MSSQL$Microsof
Aha, I thought that might be the case! I think this is what was causing your original search problem, I saw this in another posting somewhere and was trying to get you to this point.
I don't think there is any way to change the collation of a database after it has been created. I would just create it again - you should be prompted for the collation when you create it. I believe the proper collation is Latin1_General_CI_AS_KS_WS
Business Accounts
Answer for Membership
by: MsShadowPosted on 2009-10-19 at 09:13:15ID: 25606524
Is it a farm. Did you select the correct server in the dropdownlistbox?