Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search Problem WSS 3.0 / SPS 2003

Status
Not open for further replies.
Aug 11, 2004
53
CA
I have WSS 3.0 running on a Win2K3SP1+SQL200Sp4 server that used to host SPS2003. When we removed SPS2003, the add/remove programs method failed with a fatal error, so I had to do the uninstall manually according to The only leftovers (other than still being listed in Add/Remove Programs) are three files in C:\Program Files\SharePoint Portal Server\Bin (msscntrs.dll, mserror.dll and tquery.dll) which still seem to be attached to some running process and as a result I can't delete them. Normally, I would just hunt down the service, kill the process and delete the files, but these particular dll's appear to be tied to SQL and I have no desire to break that.

All of this really wouldn't bother me except for the fact that search is not working in WSS 3.0. All of the appropriate services are running and the sites in question have been assigned to the search server, but when I attempt a search, I get "The search request was unable to connect to the Search Service".

On the server, I also get Event ID's: 10038, 10039 and 10040 which have to do with access being denied to the search server and it being taken out of the rotation.

I've reached the end of my rope on this one and I'm hoping someone will be able to provide some insight on this for me.

Thanks,
Jason
 
Were you able to get your search issue resolved?

I am having the exact same problem. I perfromed an upgrade from SPS2.0 to 3.0. Everything upgraded just fine but I am unable to use the search feature now. I receive the same message on the site as well as same errors in the event log.

Let me know if you were able to find a solution to this, much appreciated.
 
It might just be that the component services to match the event ID that it is having problems with. It might be a permissions problem. That seems to be a common theme with the problems I've had in the past with the event errors.

-Laughter works miracles.
 
I'm having a search issues and the following is an example where within a wss site/doc library the follow occurs.

1). I have a document named another.doc
2). Contained in the document is the sentence.."This is another test."
3). when I search for the word "another" in the wss site my document is not found.
4). When I search for the word "test", in the same wss site the word document another.doc is found.

Steps thus far have been to re index the data in the SQL data base for all the portals.

In addition, Is see a HUGE number of event id 502 as follows:

Event Type: Error
Event Source: SharePoint Portal Administration Service
Event Category: None
Event ID: 502
Date: 6/6/2007
Time: 11:09:08 PM
User: N/A
Computer: ABCDEFGHIJUMP
Description:
An exception occurred in the search synchronizer.

Any advice would be appreciated.

Thanks
tcpreime


 
Hi,...

Check if your FWE next services are running, and make sure they got enough permissions to run, otherwise go to the properties of the services, and Choose a different logon credentials.

Services:
Windows SharePoint Services Timer
Windows SharePoint Services Tracing
Windows Sharepoint Services Search (ONLY IF THAT SERVER IS MANAGING YOUR SEARCH)

Bryan van Rijn
MS SharePoint Certified

Sogeti stand for Result
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top