Assume that you install SQL Server 2019 Developer Edition with the standard networking configuration in which TCP/IP protocol is not enabled by default. In this situation, you notice that the PolyBase services are unable to start successfully. Additionally, PolyBase services may create full memory dumps, and you may receive an error message that resembles the following:
DateTime [Thread:3876] [DiagnosticsConnectionWrapper:ErrorEvent] (Error, High): Error while opening connection (Data Source=SBK-VNEXT-WIN1,0;Initial Catalog=master;Integrated Security=True;Pooling=True;Min Pool Size=1;Max Pool Size=100;MultipleActiveResultSets=True;Application Name=DWDiagnostics).
System.Data.SqlClient.SqlException[87:0]: 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: 25 - Connection string is not valid) ---> System.ComponentModel.Win32Exception: The parameter is incorrect
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This issue is fixed in the following cumulative update for SQL Server:
About cumulative updates for SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
To work around this issue, TCP/IP protocol must be enabled by default during installation of SQL Server 2019 Developer Edition (or enabled post installation).
Learn about the terminology that Microsoft uses to describe software updates.