| Event Id | 10036 |
| Source | Windows SharePoint Services 3 |
| Description | Description 1: [DBNETLIB][ConnectionOpen (Connect()).]Specified SQL server not found. Description 2 : Error Description: Could not access the Search service configuration database. |
| Event Information | According to News group: Resolution : 1.Make sure the search service account has got DBCreator role on DB server. You can remove this role once the service is started. 2.Offcourse your normal Farm Admin service account also needs DbCreator and SecurityAdmin role. 3.I have read someone saying to use Named Pipes for remote connection. But this is not true it should work with TCP/IP connection as well. So in your SQL server make sure that your remote connection is enabled for either TCP/IP or Named Pipes or for both. 4.Make sure the DB Server name in your connection string is consistent in your farm for all other webapps, admin content config database etc etc.. 5.Finally the solution that worked for me was that I was using "DB server name\Instance, port" as the connection string and this format of connection string uses Named Pipes. Unfortunately Named Pipes was disabled so I have to use an Alias of the DB server to use the TCP/IP connection. Also once the alias is setup for you by the DBA's you have to set it up on the MOSS server under SQL Server Client Configuration settings. You can also use server name if you are using default instance for TCP/IP. |
| Reference Links |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.