locked
Search Error - "Your search cannot be completed because of a service error."

    Question

  • When I search from my portal I get the following error message:

    Your search cannot be completed because of a service error.

    I've just installed and configure MOSS. Search indexing is working fine and the indexes are propagating to my query server just fine. Below is event log info:

    Event Source: Office Server Search

    Event Category: Gather

    Event ID: 10032

    Description: Could not create a database session

    Details: The database connection string is not available.

    I've tried for days to to resolve this problem. Any help would be much appreciated.

    Regards,

    Glenn Meyer

    • Edited by Mike Walsh FIN Friday, November 14, 2008 5:52 PM Subject enhanced. "Search Error" is not enough of a subject in the Search forum
    Friday, March 09, 2007 12:37 AM

Answers

  •  Hi,

    We had this exact same error with Search Administration showing a server error, crawl logs were empty and the application event log showing the following error

    "A database error occurred.

    Source: Microsoft OLE DB Provider for SQL Server

    Code: 8144 occurred 1 time(s)

    Description: Procedure or function proc_MSS_FlushTemp0 has too many arguments specified.

    We found that had applied cumulative updates KB955586, KB957693, KB958569 KB958567 to our WFE servers but not our indexing server, once we applied them to the indexing server and ran configuration wizard everything was OK

    • Marked as answer by Mike Walsh FIN Friday, February 20, 2009 6:05 AM
    Friday, November 14, 2008 5:42 PM
  • I have a 5 server farm and it turns out that one of the servers were not on the same patch levels as the others.  I completed the following steps to resolve the problem described above:

    - Ensure all servers are patched to the same level (SP1 included)
    - Executed Configuration Wizard on all (This resulted in one server, SSP1, not completing correctly)
    - I completed the Infrastructure Update on SSP1 (which failed to upgrade above) and reran the configuration wizard

    So basically the error above is a server patch / service pack mismatch.

    Thanks for the replies.


    http://technicallead.wordpress.com/
    • Marked as answer by Mike Walsh FIN Friday, February 20, 2009 6:05 AM
    Monday, November 17, 2008 6:29 AM

All replies

  • 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

    Thursday, April 05, 2007 11:47 PM
  • Not sure if you ever solved the issue, but I just had the same problem.  In my case, somehow the index server for my ssp became disassociated with my ssp properties.  Anyhow, I resolved the issue by editing the properties of the ssp and selecting the correct index server - everything was fine after that.
    Monday, May 14, 2007 9:49 PM
  • I also get this event error. I have an SBS 2k3 (no "farm"). seacrh working fine but msg persists
    Friday, June 15, 2007 2:27 PM
  • We have just setup a new Sharepoint 2007 farm, with a single Sharepoint server and a dedicated SQL 2005 server. We too are getting several errors while crawling search contents. We crawl internal web sites and file shares which are quite huge, about 500GB and 3 million files. We get teh following errors while crawling, in some cases the Sharepoint server completely freezes when crawls are run. We cannot logon remotely or to teh console, but some services respond when the server freezes,

     

    Event Type: Error
    Event Source: Office Server Search
    Event Category: Gatherer
    Event ID: 10027
    Date:  6/19/2007
    Time:  7:58:13 AM
    User:  N/A
    Computer: NJASPS01
    Description:
    Failed to update committed transaction in SQL, DocID is 1605321.

    Context: Application 'SharedServices1', Catalog 'Portal_Content'

    Details:
     Unspecified error
     (0x80004005)

    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:  6/19/2007
    Time:  7:57:32 AM
    User:  N/A
    Computer: NJASPS01
    Description:
    A database error occurred.

    Source: Microsoft OLE DB Provider for SQL Server
    Code: 1205 occurred 17 time(s)
    Description: Transaction (Process ID 95) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

    Context: Application 'SharedServices1'

    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:  6/20/2007
    Time:  8:17:15 AM
    User:  N/A
    Computer: NJASPS01
    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.

    Wednesday, June 20, 2007 12:34 PM
  • Getting the same Application Event, but for me it's stuck in the middle of Starting the Index server, so I can't even assign the Index server to the SSP (which has helped me in various situations before).


    Event Type: Error
    Event Source: Office Server Search
    Event Category: Gatherer
    User:  N/A
    Description:
    Could not create a database session.

    Context: Application '5ac793fa-b113-4150-b098-17470abdae22'

    Details:
     The database connection string is not available.   (0xc0041228)

     

     

    On the Services on Server page, it just continues to show Office SharePoint Server Search in the state of Starting.

     

     


    On the intended Index server, there is also this Application Event:


    Event Type: Information
    Event Source: Office SharePoint Server Error Reporting
    Event Category: None
    Event ID: 5001
    User:  N/A
    Description:
    Bucket 12151763, bucket table 5, EventType ulsexception12, P1 owstimer.exe, P2 12.0.4518.1016, P3 45529fd9, P4 microsoft.office.server.search, P5 12.0.4518.0, P6 45439dcc, P7 2681, P8 136, P9 invalidoperationexception, P10 837q.

     

    Data:
    0000: 42 00 75 00 63 00 6b 00   B.u.c.k.
    0008: 65 00 74 00 3a 00 20 00   e.t.:. .
    0010: 31 00 32 00 31 00 35 00   1.2.1.5.
    0018: 31 00 37 00 36 00 33 00   1.7.6.3.
    0020: 0d 00 0a 00 42 00 75 00   ....B.u.
    0028: 63 00 6b 00 65 00 74 00   c.k.e.t.
    0030: 54 00 61 00 62 00 6c 00   T.a.b.l.
    0038: 65 00 20 00 35 00 0d 00   e. .5...
    0040: 0a 00                     ..     

    Thursday, June 28, 2007 12:23 AM
  • Upgraded MOSS deployment from B2R to RTM, Single server.

    Here is a collection of my errors that are related to search:

     

     

    Event Type: Error
    Event Source: Windows SharePoint Services 3 Search
    Event Category: Gatherer
    Event ID: 10036
    Date:  6/29/2007
    Time:  11:45:06 AM
    User:  N/A
    Computer: SPS2007
    Description:
    A database error occurred.

    Source: Microsoft OLE DB Provider for SQL Server
    Code: 8144 occurred 1 time(s)
    Description: Procedure or function proc_MSS_FlushTemp0 has too many arguments specified.

    Context: Application 'Search index file on the search server'

     

     

    Event Type: Error
    Event Source: Windows SharePoint Services 3 Search
    Event Category: Gatherer
    Event ID: 10036
    Date:  6/29/2007
    Time:  11:45:26 AM
    User:  N/A
    Computer: SPS2007
    Description:
    A database error occurred.

    Source: Microsoft OLE DB Provider for SQL Server
    Code: 8144 occurred 17 time(s)
    Description: Procedure or function proc_MSS_ProcessCommitted has too many arguments specified.

    Context: Application 'Search index file on the search server'

     

    Event Type: Error
    Event Source: Windows SharePoint Services 3 Search
    Event Category: Gatherer
    Event ID: 10036
    Date:  6/29/2007
    Time:  11:45:31 AM
    User:  N/A
    Computer: SPS2007
    Description:
    A database error occurred.

    Source: Microsoft OLE DB Provider for SQL Server
    Code: 0 occurred 1 time(s)
    Description: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.

     

     

    Many of the following:
    Event Type: Error
    Event Source: Windows SharePoint Services 3 Search
    Event Category: Gatherer
    Event ID: 10027
    Date:  6/29/2007
    Time:  10:54:33 AM
    User:  N/A
    Computer: SPS2007
    Description:
    Failed to update committed transaction in SQL, DocID is 4.

    Context: Application 'Search index file on the search server', Catalog 'Search'

    Details:
     One or more errors occurred during processing of command.   (0x80040e14)


     



     

    Friday, June 29, 2007 4:07 PM
  •  

    Event Type: Error
    Event Source: Office Server Search
    Event Category: Gatherer
    Event ID: 10027
    Date:  6/19/2007
    Time:  7:58:13 AM
    User:  N/A
    Computer: NJASPS01
    Description:
    Failed to update committed transaction in SQL, DocID is 1605321.

    Context: Application 'SharedServices1', Catalog 'Portal_Content'

    Details:
     Unspecified error
     (0x80004005)

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     


    I too am receiving this error message on my SharePoint 3.0 system.  Did anybody find the reason or resolution?  This is filling up my event viewer very fast.



    Thanks

    Friday, August 24, 2007 1:49 PM
  • Resetting the search index usually does the trick.

    ssp>search settings>reset all crawled content


    Friday, August 24, 2007 6:02 PM
  • Hi,

    i have the same problem like the first poster.
    Search is correctly configured and the solution to reset the index does not work every time.
    The problem is the search works fine since some month but from one day to another it doesnt work fine.
    More warning logs and some later it stops to work.
    If i search for any keywork i'll get this error:

    Your search cannot be completed becasue of a service error. Try your search again or contact your administrator for more information.

    I'll get no event viewer log and it seams like the moss also dont have an error.

    It makes me sick .....

    Chris


    Monday, February 04, 2008 12:31 PM
  • I've same problem and can't to backup, but if Restar server, problem disappears for 4 days. In Can't find the real problem.
    jparias
    Tuesday, September 23, 2008 12:24 AM
  • the same problem i Have.
    Dariusz Bzowk
    Monday, September 29, 2008 7:17 PM
  • Tuesday, September 30, 2008 6:43 AM
  • Hi,

    When navigating to the Search Administration page, I see "Error" next to the Server Status label.  When I try to complete an update of my index (Full to start) it doesnt complete and no errors are reported in the gather log.  I do however see the following error in the application log of the server that has the OSearch Service started on it:

    "A database error occurred.

    Source: Microsoft OLE DB Provider for SQL Server

    Code: 8144 occurred 1 time(s)

    Description: Procedure or function proc_MSS_FlushTemp0 has too many arguments specified.

    Context: Application 'SharedServices_NTGKTT53'"

    Any help will be much appreciated.

    Thanks.


    http://technicallead.wordpress.com/
    • Proposed as answer by ToffeeSP Friday, November 14, 2008 5:32 PM
    • Unproposed as answer by Mike Walsh FIN Friday, February 20, 2009 6:04 AM
    Wednesday, November 12, 2008 10:57 AM
  • Had similar errors myself.  Try checking your SQL server local properties for 'Use Windows NT fibres' under processor tab.  Unckeck if checked and restart SQL service. 
    SCC
    • Proposed as answer by tsetse251 Thursday, November 13, 2008 5:37 PM
    • Unproposed as answer by Mike Walsh FIN Friday, February 20, 2009 6:04 AM
    Thursday, November 13, 2008 5:37 PM
  •  Hi,

    We had this exact same error with Search Administration showing a server error, crawl logs were empty and the application event log showing the following error

    "A database error occurred.

    Source: Microsoft OLE DB Provider for SQL Server

    Code: 8144 occurred 1 time(s)

    Description: Procedure or function proc_MSS_FlushTemp0 has too many arguments specified.

    We found that had applied cumulative updates KB955586, KB957693, KB958569 KB958567 to our WFE servers but not our indexing server, once we applied them to the indexing server and ran configuration wizard everything was OK

    • Marked as answer by Mike Walsh FIN Friday, February 20, 2009 6:05 AM
    Friday, November 14, 2008 5:42 PM
  • I have a 5 server farm and it turns out that one of the servers were not on the same patch levels as the others.  I completed the following steps to resolve the problem described above:

    - Ensure all servers are patched to the same level (SP1 included)
    - Executed Configuration Wizard on all (This resulted in one server, SSP1, not completing correctly)
    - I completed the Infrastructure Update on SSP1 (which failed to upgrade above) and reran the configuration wizard

    So basically the error above is a server patch / service pack mismatch.

    Thanks for the replies.


    http://technicallead.wordpress.com/
    • Marked as answer by Mike Walsh FIN Friday, February 20, 2009 6:05 AM
    Monday, November 17, 2008 6:29 AM