We have an issue that has been solved, but I am trying to find an explanation. Our Sharepoint 2013 was working fine connected to a SQL 2012/Windows 2012 machine via a SQL Server Alias. We had to rename the database server, which we did, and then updated the SQL Server configuration there as directed by Microsoft. http://technet.microsoft.com/en-us/library/ms143799.aspx
We stopped the SharePoint services, and updated the SQL Server alias to point to the new server/instance name. Everything worked fine...for a few days. Then, when trying to open any SharePoint site or Central Administration, we got the error "Server Error in '/' Application". Event Viewer showed:
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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
The SQL Server was up and running. We were able to connect from the Sharepoint Server to the SQL Server via SQL Server Management Studio using an identical alias I created in the 32-Bit SQL Server Native Client configuration (since SSMS is 32-bit, this was required). The SharePoint server was then disconnected and reconnected to the farm. All sites were then accessible EXCEPT Central Administration. When trying to connect to that, we got the error:
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - The handle specified is invalid)
- Removed and rejoined both servers to the domain
- Restarted both servers
- Deleted and recreated the SQL Server Aliases (both 32 and 64 bit)
- Reviewed error logs on SharePoint machine (no good errors other than above)
- Reviewed error logs on SQL Server machine - nothing good
- Ran a Windows "Repair" of SharePoint in the Add/Remove Programs menu
Central Admin was still not working at this point. We finally ran this in the Sharepoint Management Shell:
psconfig.exe -cmd adminvs -provision
Suddenly, Central Administration was then accessible!
Does anyone know what happened in this scenario? Was the issue caused by the SQL Server name change? If so, why was Sharepoint working okay for days with the new database connection? Could there have been an Active Directory trust issue between the machines after the rename?