hi

i just migrated my sharepoint databases from one sql server 2012 to another due to the fact that sharepoint could no longer connect to that sql server

apparenlty the new sql server seems to solve all the problems. on sharepoint product and configuration wizard. when i input the name of the sql server and click on retrieve database, it brings back the default sharepoint_config which works well

but upon clicking next button i get the error below. i have googled  the error and followed the steps to resolve the problem but i have not been able to fix it. is there a log on the server to know what may be happening?

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: 28 - Server doesn't support requested protocol

Steps to resolve the Error

1. SQL Server should be up and running.

2. Enable TCP/IP in SQL Server Configuration

Go to All Programs >> Microsoft SQL Server 2008 >> Configuration Tools >> SQL Server Configuration Manager >> Select TCP/IP

Right Click on TCP/IP >> Click on Enable

3. Open Port in Windows Firewall

Go to Control Panel >> Windows Firewall >> Change Settings >> Exceptions  >> Add Port

Make the following entries in popup Add a Port and click OK.
Name : SQL
Port Number: 1433
Protocol: Select TCP

4. Enable SQL Server Browser Service

5. Enable Remote Connection

Right click on the server node and select Properties

i have done all of that. doesn't seem to work. is there a log on the sharepoint server i can look at?

You can get the log on the configuration wizard once you get the error and click cancel.

i mean a log file.

02/23/2015 14:50:07  1  ERR                                                  An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown.  Additional exception information: Failed to connect to the existing server farm located at the specified database server and database name.  The database name is not a valid configuration database.
Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException: Exception of type 'Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException' was thrown.
   at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.EnsureFarmOnConnect()
   at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Validate(Int32 nextExecutionOrder)
   at Microsoft.SharePoint.PostSetupConfiguration.TasksQueue.Validate(Boolean useDefaultExecutionOrder)
02/23/2015 14:50:07  1  ERR                                                  A PostSetupConfigurationTaskException was thrown: Failed to connect to the existing server farm located at the specified database server and database name.  The database name is not a valid configuration database.
02/23/2015 14:50:07  1  INF                                                  Entering function Common.BuildExceptionInformation
02/23/2015 14:50:07  1  INF                                                    Entering function Common.BuildExceptionMessage
02/23/2015 14:50:07  1  INF                                                      Entering function StringResourceManager.GetResourceString
02/23/2015 14:50:07  1  INF                                                        Resource id to be retrieved is ExceptionInfo for language English (United States)
02/23/2015 14:50:07  1  INF                                                        Resource retrieved id ExceptionInfo is An exception of type {0} was thrown.  Additional exception information: {1}
02/23/2015 14:50:07  1  INF                                                      Leaving function StringResourceManager.GetResourceString
02/23/2015 14:50:07  1  INF                                                    Leaving function Common.BuildExceptionMessage
02/23/2015 14:50:07  1  INF                                                  Leaving function Common.BuildExceptionInformation
02/23/2015 14:50:07  1  ERR                                                  An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown.  Additional exception information: Failed to connect to the existing server farm located at the specified database server and database name.  The database name is not a valid configuration database.
Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException: Exception of type 'Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException' was thrown.
   at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.EnsureFarmOnConnect()
   at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Validate(Int32 nextExecutionOrder)
   at Microsoft.SharePoint.PostSetupConfiguration.TasksQueue.Validate(Boolean useDefaultExecutionOrder)
   at Microsoft.SharePoint.PostSetupConfiguration.PsconfigBaseForm.ValidateConfigurationData()
   at Microsoft.SharePoint.PostSetupConfiguration.PsconfigBaseForm.TryValidateConfigurationData()
02/23/2015 14:50:07  1  INF                                                  Entering function PsconfigMessageBox.ShowMessageBox
02/23/2015 14:50:07  1  INF                                                  Leaving function PsconfigMessageBox.ShowMessageBox
02/23/2015 14:50:07  1  INF                                                  Entering function StringResourceManager.GetResourceString
02/23/2015 14:50:07  1  INF                                                    Resource id to be retrieved is Branding for language English (United States)
02/23/2015 14:50:07  1  INF                                                    Resource retrieved id Branding is SharePoint Products Configuration Wizard
02/23/2015 14:50:07  1  INF                                                  Leaving function StringResourceManager.GetResourceString
02/23/2015 14:50:07  1  INF                                                  Not running in high contrast, so we will paint the background with our trademarked image

2015-02-23 14:24:34.28 Server      SQL Server detected 1 sockets with 3 cores per socket and 3 logical processors per socket, 3 total logical processors; using 3 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2015-02-23 14:24:34.28 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-02-23 14:24:34.28 Server      Detected 2047 MB of RAM. This is an informational message; no user action is required.
2015-02-23 14:24:34.28 Server      Using conventional memory in the memory manager.
2015-02-23 14:24:34.42 Server      This instance of SQL Server last reported using a process ID of 1460 at 2/23/2015 2:24:26 PM (local) 2/23/2015 1:24:26 PM (UTC). This is an informational message only; no user action is required.
2015-02-23 14:24:34.42 Server      Node configuration: node 0: CPU mask: 0x0000000000000007:0 Active CPU mask: 0x0000000000000007:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2015-02-23 14:24:34.42 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2015-02-23 14:24:34.45 Server      Software Usage Metrics is disabled.
2015-02-23 14:24:34.46 spid5s      Starting up database 'master'.
2015-02-23 14:24:34.52 Server      CLR version v4.0.30319 loaded.
2015-02-23 14:24:34.60 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2015-02-23 14:24:35.07 spid5s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-02-23 14:24:35.07 spid5s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2015-02-23 14:24:35.10 spid5s      SQL Trace ID 1 was started by login "sa".
2015-02-23 14:24:35.12 spid5s      Server name is 'SP-SQL'. This is an informational message only. No user action is required.
2015-02-23 14:24:35.13 spid5s      Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\ftimport.dll'.
2015-02-23 14:24:35.13 spid16s     Starting up database 'msdb'.
2015-02-23 14:24:35.14 spid17s     Starting up database 'SharePoint_Config'.
2015-02-23 14:24:35.14 spid9s      Starting up database 'mssqlsystemresource'.
2015-02-23 14:24:35.14 spid18s     Starting up database 'WSS_Logging'.
2015-02-23 14:24:35.14 spid19s     Starting up database 'WSS_Content_Archive'.
2015-02-23 14:24:35.14 spid20s     Starting up database 'WSS_Content_2222'.
2015-02-23 14:24:35.15 spid21s     Starting up database 'WSS_Content'.
2015-02-23 14:24:35.15 spid22s     Starting up database 'WordAutomationServices_08da96e66cbb4dfebdfc6fff78940019'.
2015-02-23 14:24:35.16 spid23s     Starting up database 'TranslationService_ae6c6173cf5e427ebac4420298f3608c'.
2015-02-23 14:24:35.16 spid25s     Starting up database 'SharePoint_AdminContent_92309263-16d3-4ebd-b7f4-bb3307ef4d74'.
2015-02-23 14:24:35.16 spid9s      The resource database build version is 11.00.2100. This is an informational message only. No user action is required.
2015-02-23 14:24:35.16 spid27s     Starting up database 'Search_Service_Application_LinksStoreDB_d82795625f054d268f5ecfbedfa78d1a'.
2015-02-23 14:24:35.16 spid26s     Starting up database 'Secure_Store_Service_DB_d54b4a70f0d84b86b0f0b3db53cecf90'.
2015-02-23 14:24:35.17 spid24s     Starting up database 'StateService_7e60c2df2c10403198435593d762351c'.
2015-02-23 14:24:35.64 spid13s     A self-generated certificate was successfully loaded for encryption.
2015-02-23 14:24:35.65 spid13s     Server is listening on [ 'any' <ipv6> 1433].
2015-02-23 14:24:35.65 spid13s     Server is listening on [ 'any' <ipv4> 1433].
2015-02-23 14:24:35.65 spid13s     Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2015-02-23 14:24:35.65 spid13s     Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2015-02-23 14:24:35.65 Server      Server is listening on [ ::1 <ipv6> 1434].
2015-02-23 14:24:35.65 Server      Server is listening on [ 127.0.0.1 <ipv4> 1434].
2015-02-23 14:24:35.65 Server      Dedicated admin connection support was established for listening locally on port 1434.
2015-02-23 14:24:35.65 spid13s     SQL Server is now ready for client connections. This is an informational message; no user action is required.
2015-02-23 14:24:35.65 Server      SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2015-02-23 14:24:35.69 Server      The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/SP-SQL.m.com ] for the SQL Server service.
2015-02-23 14:24:35.69 Server      The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/SP-SQL.m.com:1433 ] for the SQL Server service.
2015-02-23 14:24:35.72 spid9s      Starting up database 'model'.
2015-02-23 14:24:35.79 spid9s      Clearing tempdb database.
2015-02-23 14:24:36.02 spid9s      Starting up database 'tempdb'.
2015-02-23 14:24:36.18 spid28s     The Service Broker endpoint is in disabled or stopped state.
2015-02-23 14:24:36.19 spid28s     The Database Mirroring endpoint is in disabled or stopped state.
2015-02-23 14:24:36.21 spid28s     Service Broker manager has started.
2015-02-23 14:24:36.24 spid16s     Starting up database 'Search_Service_Application_DB_3cdf607717fa476a9017d0834d406368'.
2015-02-23 14:24:36.25 spid26s     Starting up database 'Search_Service_Application_CrawlStoreDB_6ce7ddd547e54461ac6d2cec07771adb'.
2015-02-23 14:24:36.29 spid23s     Starting up database 'Search_Service_Application_AnalyticsReportingStoreDB_53113fabad83492b8209cefe28ba4fd1'.
2015-02-23 14:24:36.29 spid22s     Starting up database 'AppMng_Service_DB_7b6e0de99b444d799a69b20c53344901'.
2015-02-23 14:24:36.30 spid24s     Starting up database 'Bdc_Service_DB_6c83ef126a9546cdac05df86a37bf1e7'.
2015-02-23 14:24:36.30 spid27s     Starting up database 'Managed Metadata Service_7000c9e1253140efa3579e4450257b29'.
2015-02-23 14:24:36.45 spid52      Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2015-02-23 14:24:36.46 spid52      Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
2015-02-23 14:24:36.46 spid52      Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2015-02-23 14:24:36.49 spid23s     Starting up database 'MID_Profile_DB'.
2015-02-23 14:24:36.73 spid18s     Starting up database 'MID_Social_DB'.
2015-02-23 14:24:36.91 spid18s     Starting up database 'MID_Sync_DB'.
2015-02-23 14:24:36.97 spid24s     Starting up database 'PerformancePoint Service Application_127949f4e90c482086f1319108a446d9'.
2015-02-23 14:24:37.05 spid52      Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
2015-02-23 14:24:37.05 spid52      Using 'xpsqlbot.dll' version '2011.110.2100' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
2015-02-23 14:24:37.05 spid22s     Starting up database 'ReportServer$MSSQLSERVER012TempDB'.
2015-02-23 14:24:37.34 spid52      Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2015-02-23 14:24:37.36 spid52      Using 'xpstar.dll' version '2011.110.2100' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2015-02-23 14:24:37.38 spid26s     Error: 909, Severity: 21, State: 1.
2015-02-23 14:24:37.38 spid26s     Database 'Search_Service_Application_CrawlStoreDB_6ce7ddd547e54461ac6d2cec07771adb' cannot be started in this edition of SQL Server because part or all of object 'MSSCrawlReportCrawlErrors' is enabled with data compression or vardecimal storage format. Data compression and vardecimal storage format are only supported on SQL Server Enterprise Edition.
2015-02-23 14:24:37.38 spid26s     Error: 933, Severity: 21, State: 1.
2015-02-23 14:24:37.38 spid26s     Database 'Search_Service_Application_CrawlStoreDB_6ce7ddd547e54461ac6d2cec07771adb' cannot be started because some of the database functionality is not available in the current edition of SQL Server.
2015-02-23 14:24:37.53 spid52      Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
2015-02-23 14:24:37.54 spid52      Using 'xplog70.dll' version '2011.110.2100' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
2015-02-23 14:24:41.96 spid5s      Recovery is complete. This is an informational message only. No user action is required.

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: 28 - Server doesn't support requested protocol)

HI,The issue could be of many reasons.please check the below to resolve the issue.

  Ensure SQL database and services are running.
        Ensure to reboot  the DB server after applied a Hot fix or Service Pack.
        Ensure the Firewall is not blocking the communication
        Ensure The SharePoint Installation Account does have the required permissions to the SQL Server database.
        Ensure Network connectivity is OK between the SharePoint Server and SQL Server

http://expertsharepoint.blogspot.de/2014/06/a-network-related-or-instance-specific.html

Hi Anil

I have done all of that.

When I try to add the server to the farm, I get to the part after you retrieve the database names.

That works no issue and find the right DB name.

After clicking next I get the following message

"Failed to connect to the existing server farm located at the specified database name. The database name is not a valid configuration database"

I see this in the Event Log

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: 28 - Server doesn't support requested protocol)

I have done everything said here but it still wouldnt work

Hi ,

Check if farm administration account is mapped to the configuration database as dbo and has dbo_owner permission on SQL Server.