IT 专业人士的资源 > 论坛主页 > SharePoint - Search > Could not create a database session
提出问题提出问题
 

已答复Could not create a database session

  • 2007年3月18日 16:44woef 用户奖牌用户奖牌用户奖牌用户奖牌用户奖牌
     
    Hello,

    When I do a search in a sharepoint site, I get the following error :
    Your search cannot be completed because of a service error. Try your search again or contact your administrator for more information.

    When I check the app. log, the following is mentioned :

    Event Type:    Error
    Event Source:    Office Server Search
    Event Category:    Gatherer
    Event ID:    10032
    Date:        18/03/2007
    Time:        17:36:16
    User:        N/A
    Computer:    SVRPOE
    Description:
    Could not create a database session.

    Context: Application 'bdc68541-4efc-461e-838a-9aa19aafd291'

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

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


    Can somebody please shine a light on this problem ?

    Thanks,
    Woef.

答案

  • 2007年3月22日 21:24Andrew WoodwardMVP, 版主用户奖牌用户奖牌用户奖牌用户奖牌用户奖牌
     已答复

    Search is now part of the Shared Service Provider and also uses a Search SQL database for metadata and additional information.  You need to check your search configuration in the ShareServices - via Central Administration. 

    Andrew

全部回复

  • 2007年3月22日 21:24Andrew WoodwardMVP, 版主用户奖牌用户奖牌用户奖牌用户奖牌用户奖牌
     已答复

    Search is now part of the Shared Service Provider and also uses a Search SQL database for metadata and additional information.  You need to check your search configuration in the ShareServices - via Central Administration. 

    Andrew

  • 2007年11月3日 19:33VladBath 用户奖牌用户奖牌用户奖牌用户奖牌用户奖牌
     

    I had the same problem.  The specific steps taken to resolve it were:

     

    (1) Open Central Administration->SharedServices1 (my SSP).

    (2) Click on Search Settings.  An error will appear saying something about the search not being configured.  It will offer a link to request appropriate account information.  Click it.

    (3) Configure the page presented and click OK.

    (4) Wait a couple of minutes while the index migration occurs.

     

    Everything should be back to normal!

     

    Vlad

  • 2008年6月9日 19:50Gisch 用户奖牌用户奖牌用户奖牌用户奖牌用户奖牌
     
    I was having the same problem in my farm.  I have two App servers, and two front ends...with a SQL clustered back end.  Turns out that my index server dissappeared on me.  Just had to add that back and the errors went away, and I was able to search again...

    1. Open Central Admin
    2. In the Application Tab go to Create or Manage this farm's shared services
    3. Click the drop down of the SSP you want to edit, and click edit
    4. Add the Indexing server

    I had to recrawl all the content, but that doesn't take very long