SharePoint Experts, Information Architects, Expert Witness

We provide consulting in a broad array of business and technology from architecture to design to deployment of global systems with a focus on surfacing data in the enterprise. Specialists in Microsoft, we are a premier provider of SharePoint Expertise (including 2016 and Office 365). We also provide Expert Witness/Legal Expert in eDiscovery, source discovery, patent infringement, piracy and more! We also have established SICG DLDS s.a. - our counterpart in Costa Rica that specializes in water systems (http://www.crwatersolutions.com) - Contact me direct: david_sterling@sterling-consulting.com or call 704-873-8846 x704.

Search This Blog

Tuesday, October 6, 2015

Troubles installing SharePoint 2016

If you are working with the pre-release SharePoint 2016 preview, you may get an error when trying to install. The error in the System Event Application log - Event ID 5586 shows the error as:

Unknown SQL Exception 53 occurred. Additional error information from SQL Server is included below.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

There are a variety of reasons this may occur, most notable:

1) Not using a SQL Alias - this has been a problem will all SharePoint versions. If you attempt to use the SQL instance name it will work - sort of. If it is the default instance you might be OK but usually services like the User Profile will not. If you've not setup an alias before, the command is "cliconfg". Be sure to enable TCP/IP and Named Pipes (with TCP/IP as the priority).

2) An actual network problem - some have experienced this in networks where the DNS is flakey; often adding all of the farm servers to the Hosts file (on all servers) will correct.

3) Incorrect settings in SQL Server - if SQL is set to Named Pipes vs. TCP/IP, this will occur.

4) Something else - sometimes, simply re-running the installation will 'fix' the issue. I had this occur on a fresh system; I rebooted and ran again and the install completed.

Hope this helps!

No comments: