Others

Fix SharePoint Server Cannot Connect to Existing Farm Database

Anum MushtaqAnum Mushtaq Oct 28, 2026 869 views

Question details

The SharePoint Configuration Wizard is unable to connect to an existing farm database.

How to Fix SharePoint Server Cannot Connect to Existing Farm Database
Product
Microsoft SharePoint Server 2016
Device & OS
Windows Server 2019
Scenario
Adding a new Windows Server 2019 application server to an existing SharePoint Server 2016 farm.
Observed behavior
The Configuration Wizard fails to connect to the farm database, even though network connectivity, SQL permissions, ports, and instance names have all been verified as correct.
Before you start

Ensure you have the exact SQL Server instance name and confirm that the SQL Server Browser service is running before proceeding with advanced troubleshooting.

Solution 1Recommended

Consult Microsoft Q&A SharePoint Specialists

Since basic connectivity, permissions, and port configurations have been ruled out, consulting specialized Microsoft forums is the most effective next step for complex farm configurations.

Farm configuration issues involving mixed OS versions (like Windows Server 2019 with SharePoint 2016) often involve undocumented compatibility quirks or strict cumulative update requirements. Microsoft specialists can analyze your specific topology.

1
Navigate to Microsoft Q&A

Open your web browser and go to the official Microsoft Q&A community platform.

2
Select the appropriate tags

When creating your post, use tags such as 'SharePoint Server IT Professional', 'SharePoint Server Development', or 'SharePoint Server Administration' to ensure the right experts see it.

3
Provide detailed diagnostic information

Post a detailed description of your issue, explicitly mentioning that network connectivity, SQL permissions, ports, and instance names have already been tested and verified.

Consult Microsoft Q&A SharePoint Specialists
Required Details: Be sure to include the specific error code from the PSCDiagnostics logs when posting your question to expedite the troubleshooting process.
Free Microsoft Office alternative

Looking for a Lightweight Office Suite Alternative?

While resolving complex SharePoint server issues requires specialized administration, everyday document management shouldn't be complicated. WPS Office provides a free, lightweight, and highly compatible alternative to Microsoft Office for creating, editing, and sharing documents without complex server dependencies.

  1. 1. Visit the WPS Office Website: Go to the official WPS website to access the free download.
  2. 2. Download the Installer: Click the 'Download' button to get the lightweight installation file for your operating system.
  3. 3. Install and Run: Open the downloaded file and follow the on-screen prompts to install WPS Office in minutes.
Fully compatible with Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx).Lightweight installation with extremely fast startup times.All-in-one tabbed interface for seamless document management.Free alternative for standard office productivity.
microsoft office alternative - wps office

Frequently Asked Questions

Why does the SharePoint Configuration Wizard fail to detect the database server?

This often happens if the SQL Server Browser service is disabled, firewalls are blocking the specific SQL port (default 1433), or if the account running the wizard lacks the 'dbcreator' or 'securityadmin' roles on the SQL server.

Does Windows Server 2019 support SharePoint Server 2016?

SharePoint Server 2016 was originally designed for Windows Server 2012 R2 and Windows Server 2016. Running it on Windows Server 2019 is not natively supported out of the box and can cause compatibility issues during farm configuration unless specific cumulative updates are applied.

What logs should I check for SharePoint farm connection errors?

You should review the PSCDiagnostics (SharePoint Products and Technologies Configuration Wizard) logs. These are typically located in the 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\LOGS' directory on the server.