Barton Friedland
I have set up several farms and not had this problem, however, on one deployment, I am seeing something like this as well.
The crawl logs show that content is being crawled, however, whenever a user searches for anything through the SharePoint UI, they get
"Your search cannot be completed because of a service error. Try your search again or contact your administrator for more information"
Review of the logs show that no errors are generated at the time the user searches on the server, however, there are some errors that show up in the log that are similar to the above:
Event Type: Error
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 10036
Date: 4/3/2007
Time: 6:01:53 AM
User: N/A
Computer: XXXX
Description:
A database error occurred.
Source: Microsoft OLE DB Provider for SQL Server
Code: 17 occurred 4097 time(s)
Description: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
Context: Application '1ec2aec6-f2b1-4d97-9087-f9d9e82315ad'
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 10036
Date: 4/3/2007
Time: 12:35:28 PM
User: N/A
Computer: XXXX
Description:
A database error occurred.
Source: Microsoft OLE DB Provider for SQL Server
Code: 11 occurred 1 time(s)
Description: [DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 10036
Date: 4/4/2007
Time: 3:00:58 AM
User: N/A
Computer: XXXX
Description:
A database error occurred.
Source: Microsoft OLE DB Provider for SQL Server
Code: 18452 occurred 1 time(s)
Description: Login failed for user ''. The user is not associated with a trusted SQL Server connection.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Any troubleshooting steps that will help to identify how to solve this issue would be greatly appreciated.
Thanks,
Barton