Search Error 10032: Could not create a database session. Context: Application {GUID} Details: The database connection string is not available

SharePoint 2007 Search on a specific WFE returned “Your search cannot be completed because of a service error. Try your search again or contact your administrator for more information.” while in other WFEs search worked perfectly. This happened after I stopped the search service on a specific server and started it on another server in the Farm.

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

Examined the event logs and found the error:
Could not create a database session. Context: Application {GUID} Details: The database connection string is not available
Search Error 10032: Could not create a database session

Fix:

Exported the registry key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Applications\{GUID}] from the WFE where search works and imported to the problematic server.

Which was something like:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Applications\19d466e6-f04b-40b5-b9fa-525791e7fb50\ResourceManager]
“Data”=”Server=SQLServerName;Database=SharedServices1_Search_DB;Trusted_Connection=yes;App=Windows SharePoint Services;Timeout=15”
“Search”=”Server=SQLServerName;Database=SharedServices1_DB;Trusted_Connection=yes;App=Windows SharePoint Services;Timeout=15”

and it worked like a charm!

Salaudeen Rajack

Salaudeen Rajack - Information Technology Expert with Two decades of hands-on experience, specializing in SharePoint, PowerShell, Microsoft 365, and related products. Passionate about sharing the deep technical knowledge and experience to help others, through the real-world articles!

One thought on “Search Error 10032: Could not create a database session. Context: Application {GUID} Details: The database connection string is not available

  • Agreed, worked like a charm. I had just had to rebuild SharePoint Shared Services with MS following a corruption, and two replacement servers in the farm showd this error, and didn’t have the new search guid in the registry. Copied whole branch from a working WFE and people search sprang to life. THANKS.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *