question

LynkxVavri-5911 avatar image
0 Votes"
LynkxVavri-5911 asked EmilyDu-MSFT edited

SharePoint Foundation 2010 on MSSQL2012 - Search Service errors because of SQLNCLI10

Hi,
I'm trying to migrate from SQL 2008 to SQL 2012 (and also from windows server 2008 R2 to windows server 2012) in our SharePoint Foundation 2010 farm. We can run everything except Search Service, apparently because it is trying to use SQL Native Client 10 (SQLNCLI10) - but SQL 2012 runs on SQLNCLI11. See error logs from ULS by Search Service below text.

Within the sp2 service pack information for SharePoint Foundation 2010, it is stated that MSSQL 2012 is supported. So, my question is, if it is possible to change connection string for Search Service to use SQLNCLI11? Or if there is another solution to this.


Relevant part of ULS log:

10/17/2021 22:30:02.10 mssearch.exe (0x0B00) 0x0DC4 SharePoint Foundation Search Common 0000 High CResourceManager::CreateSessionEx2 Error creating non fastload session 'Provider=SQLNCLI10;Extended Properties='Server=dmssql;Database=WSS_Search_PROD;Trusted_Connection=yes;App=Microsoft SharePoint Foundation;Timeout=15';'. [resourcemanagerimpl.cpp:1124] d:\office\source\search\native\mssrch\resourcemanagerimpl.cpp
10/17/2021 22:30:02.10 mssearch.exe (0x0B00) 0x0DC4 SharePoint Foundation Search UtilCommon cd08 High SQL call failed (0x80004005: Unspecified error ) [atldbext.cxx:1290] d:\office\source\search\libs\utild\atldbext.cxx
10/17/2021 22:30:02.10 mssearch.exe (0x0B00) 0x0DC4 SharePoint Foundation Search UtilCommon cd09 High error 0: Client unable to establish connection (source Microsoft SQL Server Native Client 10.0, 0x80004005, code 10054: Unspecified error ) [atldbext.cxx:1386] d:\office\source\search\libs\utild\atldbext.cxx
10/17/2021 22:30:02.10 mssearch.exe (0x0B00) 0x0DC4 SharePoint Foundation Search UtilCommon cd09 High error 1: TCP Provider: An existing connection was forcibly closed by the remote host. (source Microsoft SQL Server Native Client 10.0, 0x80004005, code 10054: Unspecified error ) [atldbext.cxx:1386] d:\office\source\search\libs\utild\atldbext.cxx
10/17/2021 22:30:02.10 mssearch.exe (0x0B00) 0x0DC4 SharePoint Foundation Search UtilCommon cd08 High SQL call failed (0x80004005: Unspecified error ) [atldbext.cxx:1290] d:\office\source\search\libs\utild\atldbext.cxx
10/17/2021 22:30:02.10 mssearch.exe (0x0B00) 0x0DC4 SharePoint Foundation Search UtilCommon cd08 High SQL call failed (0x80004005: Unspecified error ) [atldbext.cxx:1290] d:\office\source\search\libs\utild\atldbext.cxx
10/17/2021 22:30:02.10 mssearch.exe (0x0B00) 0x0DC4 SharePoint Foundation Search GatherPI e5he High CGatherPluginMgr::SQLGetCurrentRegistryVersion Failed in GetSession, Error is 0x80004005 [gatherpimgr.cxx:826] d:\office\source\search\native\gather\server\gatherpimgr.cxx


sharepoint-dev
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

EmilyDu-MSFT avatar image
0 Votes"
EmilyDu-MSFT answered EmilyDu-MSFT edited

@LynkxVavri-5911

Per my research, there is Microsoft documentation indicates that how to change connection string for search service application to use SQLNCLI11

I suggest you create a new search service application to test whether search works well.


If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@LynkxVavri-5911

I’m checking how the things are going on about this issue. Whether the answer helps you?

If there is any problem with this issue, feel free to let me know.

0 Votes 0 ·

Hi,
no resolution yet. Connection string can be found registry, but it is just "farm" connection string and you cannot change "provider" property. I'm thinking though, that SQLNCLI10 is not the root cause. Other things are working fine, like browsing content on sites, cetral admin, etc. It is just Search serivces that are having moods.

Unfortunately, we could not rebuild current production server. It is too risky and we would like to avoid triggering business continuity management processes by requesting server recovery from backup. So, we have to keep it running on old database hosted on win 2008 r2 server and mssql 2008, for now.

There seem to be too many variables, including the fact that this new database server is in different domain. We are waiting for new application server to be prepared (in the same domain as new database server) which will put application and database servers into same datacenter segment and on the same operating system version. In the meantime, we plan to try to build new farm using development server and connect it to this new 2012 database server to see if it is a configuration problem or a "feature" ;-)

Btw. On SPF there are limited options to search service configuration and management compared to SharePoint Server version - which uses enterprise search service.

0 Votes 0 ·

@LynkxVavri-5911

Yes, SharePoint Server has more features than SharePoint Foundation, SharePoint Server is recommended to use.

If there is any update, you could update the thread.

0 Votes 0 ·