The machine config is Windows Server 2012, 64 Bit SQL Server 2016, and SQL Server Management Studio 2017. When I use SQL Server Configuration Manager to enable filestream, it gives me an error that I do not know how to get around. > There was an unknown error applying the FILESTREAM settings. check the > parameters are valid. (0x80041008)

I am trying to change the service account of an SQL Server 2014 instance to use an MSA. The MSA has already been created and installed to this server. I have changed it to a domain account previously and this worked fine. Configuration manager comes back with "Process terminated unexpectedly" when it restarts the SQL Engine. Checking the event log I see messages about not being able to access the error logs. When adding permissions to the error log there are then messages about not being able to access the master ldf and mdf. I've never seen this issue previously, so I'm wondering if anyone has seen anything similar? OS is 2012 R2 SQL is 204 EE

I have setup a SQL Server 2019 instance on my machine which has a computer name in a format like this: > AB-ABC1234ABAB My SQL instance is named 'SQL2019', therefore I connect to my local SQL instance by supplying the following name: > AB-ABC1234ABAB\SQL2019 I have scripts which rely on server aliases, e.g. - Alias1 - Alias2 To set these up, I navigated to the 'Sql Server Configuration Manager' and performed the following steps: 1) Navigate to 'Protocols for SQL2019' and enabled 'TCP/IP' 2) Navigated to the 'Aliases' for 'SQL Native Client 11.0 Configuration (32bit)' 3) Created the alias 'Alias1' pointing to my server name: AB-ABC1234ABAB\SQL2019 and protocol 'tcp' 4) Repeated above step for alias 2 5) Repeated above two steps for the 'SQL Native Client 11.0 Configuration' also. 6) Opened Windows Services and restarted the 'SQL Server (SQL2019)' service. In SQL Server Management Studio, I have connected to my instance using Windows authentication, then I have created a new login and selected 'SQL Server authentication'. I have then been tested that login by logging in by specifying the computer name as the server (AB-ABC1234ABAB\SQL2019). Then I have disconnected and typed the alias name (e.g. Alias1) in the login box, selected SQL Server authentication and supplied the same login I used earlier. When I do this, the connection attempt times out. It appears neither alias works for me. Error I get is the standard one, e.g. "provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)". What steps can I take to troubleshoot this issue? Could the hyphen in the server name be cause for concern? I noticed that if I delete the SQL alias I get a slightly different error: "error: 40 - Could not open a connection to SQL Server - the network path was not found."

I have run into an issue whilst configuring a multi-instance SQL Server when assigning a specific IP address to the fist instance. ### Dedicated IP Setup The steps I perform to configure a single instance to a dedicated IP address are: 1. Open SQL Server Configuration Manager (SSCM) 2. Navigate down the tree to: SQL Server Configuration Manager (local) +-- SQL Server Network Configuration +-- Protocols for 3. In the right pane I then doubl-click on **TCP/IP** which open the **Properties of TCP/IP** in the tab **Protocol** 4. I then ensure that **Enabled** is set to **yes** and the option for **Listen All** is set to **No**. 5. I switch tabs into the **IP Addresses** and ensure that - **Enabled** is set to **No** for all IPv4 and IPv6 addreses, except for the IP address that I want to assign to this instance. For this IP address I set the setting to **Yes**. - The **TCP Dynamic Ports** is empty for all IP addresses. - For the IP address that I want to assign to this instance I assign the **TCP port 1433**. 6. I then close all windows and SSCM displays the standard message: --------------------------- Warning --------------------------- Any changes made will be saved; however, they will not take effect until the service is stopped and restarted. --------------------------- OK --------------------------- 7. I restart the specific instance and it will generally allow connections to my instance via the dedicated IP address. 8. I test the instance is listening on the given IP address and port with: c:\> netstat -abon > TCP 10.58.212.112:1433 0.0.0.0:0 LISTENING 2172 > [sqlservr.exe] Above results are from a working server So far so good. I have done this for the umpteenth time and never had any issues. ### Case Two days ago the SQL Server service for a freshly configured instance on a **test** server wouldn't start after configuring the 10.58.194.5 address for the instance. I tried the following steps to fix the "broken" **test** instance: 1. Repair Shared Tools 2. Repair Instance 3. Deinstall and Reinstall SQL Server 4. Run a ProcMon to figure out where things were broken. But nothing has helped so far. The relevent output from the ERRORLOG file is as follows: > 2021-12-17 08:00:03.76 spid17s Error: 26024, Severity: 16, State: 1. > 2021-12-17 08:00:03.76 spid17s Server failed to listen on 10.58.194.5 1433. Error: 0x2741. > To proceed, notify your system administrator. > 2021-12-17 08:00:03.76 spid17s Error: 17182, Severity: 16, State: 1. > 2021-12-17 08:00:03.76 spid17s TDSSNIClient initialization failed with error 0x2741, status code 0xa. > Reason: Unable to initialize the TCP/IP listener. > 2021-12-17 08:00:03.76 spid17s Error: 17182, Severity: 16, State: 1. > 2021-12-17 08:00:03.76 spid17s TDSSNIClient initialization failed with error 0x2741, status code 0x1. > Reason: Initialization failed with an infrastructure error. Check for previous errors. > 2021-12-17 08:00:03.76 spid17s Error: 17826, Severity: 18, State: 3. > 2021-12-17 08:00:03.76 spid17s Could not start the network library because of an internal error in the network library. > To determine the cause, review the errors immediately preceding this one in the error log. > 2021-12-17 08:00:03.76 spid17s Error: 17120, Severity: 16, State: 1. > 2021-12-17 08:00:03.76 spid17s SQL Server could not spawn FRunCommunicationsManager thread. > Check the SQL Server error log and the operating system error log for information about possible related problems. This is the first time that I am unable to configure/set a SQL Server instance to a specific IP address. ### Event Log Entries The following errors are logged in the Application Event Log of Windows when trying to start the service (newest first): > Level | Date / Time | Source | Event ID > Error | 17.12.2021 11:00:45 | MSSQL$ | 17120 > Error | 17.12.2021 11:00:45 | MSSQL$ | 17826 > Error | 17.12.2021 11:00:45 | MSSQL$ | 17182 > Error | 17.12.2021 11:00:45 | MSSQL$ | 17182 > Error | 17.12.2021 11:00:45 | MSSQL$ | 26024 These Event IDs resemble the information from the ERRORLOG. Additional entry in the System Event Log is: > Level | Date / Time | Source | Event ID > Error | 17.12.2021 11:00:45 | Service Control Manager | 7024 The details being: > The service "SQL Server ()" has been stopped with the following error: > The requested address is invalid in this context. The XML details being: > - > - > > 7024 > 0 > 2 > 0 > 0 > 0x8080000000000000 > > 15418 > > > System > SERVER.DOMAIN.TLD > > > - > SQL Server () > %%10049 > 4D005300530051004C00240041004C004C00470045004D00450049004E000000 > > ### Network Interface Card Configuration There is only one NIC configured on the **test** server. And it is a virtual one at that. The name is **Ethernet0** and the type is **Ethernet Adapter for vmxnet3**. The network is configured as follows: > IP address: 10.58.194.4 > Subnet mask: 255.255.255.192 > Standard gateway: 10.58.194.2 The additional IP addresses that we are using for the SQL Server instances are: > 10.58.194.5 / 255.255.255.192 > 10.58.194.6 / 255.255.255.192 > 10.58.194.7 / 255.255.255.192 > 10.58.194.28 / 255.255.255.192 > 10.58.194.29 / 255.255.255.192 The single NIC is configured to accept connections for the six IP addresses. ### Question Does anybody have an idea how I can fix this problem? ----- ### Additional Information via Comments If I set the **Listen All** option to **Yes** in the TCP/IP configuration, then the instance will start. But this is not what I am seeking. I am unable to connect to the instance using the alias or the IP address. The sqlserver.exe process is then no longer listening on port 1433. After contemplating my observation that _the sqlserver.exe process is then no longer listening on port 1433_ it seems like the server is unable to bind the IP address to port 1433 for my first instance. After configuring **Listen All** to **yes** and the IP address to have port 1433 , then sqlserver.exe doesn't listen on any IP address (0.0.0.0) for port 1433. It's like the configuration setting for the input box for the port number is corrupt. SQL Server ERRORLOG displays: > 2021-12-17 16:27:36.35 spid17s Error: 26058, Severity: 16, State: 1. > 2021-12-17 16:27:36.35 spid17s A TCP provider is enabled, but there are no TCP listening ports configured. > The server cannot accept TCP connections.` ---- ### Side Notes I was able to set up and configure a **productive** server, that I received the same day, to use a specific IP without any issues. The only difference was maybe that the six IP addresses I received for the **productive server**, were in **sequential order** like this: > 10.xx.xxx.111 / 255.255.255.0 -- server > 10.xx.xxx.112 / 255.255.255.0 -- instance_1 > 10.xx.xxx.113 / 255.255.255.0 -- instance_2 > 10.xx.xxx.114 / 255.255.255.0 --... > 10.xx.xxx.115 / 255.255.255.0 > 10.xx.xxx.116 / 255.255.255.0

I'm having trouble finding any documentations regarding supported key lengths for RSA certs to encrypt SQL connections. Our internal CA is issuing certs with a 4096 key length and that seems to work with our 2019 SQL servers, but I cannot seem to get anything lower than 2019 to see the certs in Configuration Manager. My hunch is that 2017 and below do not support a 4096 key length but I'm not able to find any documentation saying what is actually supported so it's only a guess right now. Does anybody have any documentation showing what is supported by each version? Thanks.

I have installed sql server 64 bit. Why does sql configuration manager show 32 and 64 bit options when only 64 bit version is installed?

I have to update 50+ servers to use encrypted connection strings. Is there a way to script setting Force Encryption and TrustServerCertificate (e.g Powershell, or ???) so that I don't have to open Configuration Manager and set on each box?

I have a SQL Server 2017 instance that I have configured to listen on multiple ports 1433 and 1234. I would like to know if its possible to have one port (1234) accept **only** secure connections while the default port accept both? I have already set up the instance, verified both ports are working, and installed the certificate but it seems my only option is to force SSL for the entire instance in config manager. Am I missing something? All help is appreciated.

I am trying to add a traceflag as a startup parameter to a distant SQL Server 2016, installed on a Windows 2016 core server and I am following these instructions At this point in the document: > In the console tree, expand Services and Applications, and then expand > SQL Server Configuration Manager to manage the remote computer's > services. There is no SQL Server Configuration Manager here. - Is this a permissions issue? - Does anyone know what permission needs to be added and where so I can see SQL Server Configuration manager under Services and Applications? - Does core have anything to do with this? Thanks, Craig

In SQL Server Configuration Manager on the Advanced tab in TCP/IP Protocol properties box there is an option Accepted NTLM SPNs. What is the use of that option and how it can be used?

I have a server running Windows 2012 R2 Datacenter 64-bit. I was using SQL 2016 RC3 with no issues and I want to replace it with the RTM build we have from MSDN. After uninstalling RC3 and then installing RTM, I was unable to connect remotely to the server. Upon inspection, I see within Configuration Manager that there is no node for "SQL Server Network Configuration". The 32-bit versions are listed, and TCP/IP is enabled. How do I get this missing node installed? I have started the SQL Browser service and attempted to repair the 2016 installation. Nothing seems to revive this missing component. I find interesting that there are pieces of the RC3 and RTM installs left behind that I can't uninstall. I'm not sure if this is relevant. I followed Microsoft instructions on uninstalling SQL Server so I feel like I've done everything right.

We do not appear to be able to change the startup parameters for a new SQL Server instance, using SQL Server Configuration Manager (see screenshot below). We are members of the sysadmin fixed server role, and are running SSCM version 2015.0130.16111.04 for Microsoft SQL Server 2016 (SP2-CU6) (KB4488536) - 13.0.5292.0 (X64) Enterprise Edition.

I have newly installed following things on my system

     - Microsoft SQL Server Management Studio 2014 
     - SQL Server 2017
     - Visual Studio 2015

When I tried to open SSMS for the first time, it asked me for the "Server Name" when I surfed I came to know that I have to check the instance name in Configuration manager-->Sql Services, but I couldn't find any services running in Configuration Manager, it is showing "There are no items to show" Secondly, I also tried giving the permissions to my SQL Server services as mentioned in article here, but couldn't solve my issue. Also I tried to check find the SQL Server instance name using the sqlcmd -L command, but it didn't show any servers, even though SQL Server is already installed. What am I doing wrong?

I am having trouble with a Linked Server. I would typically not use a linked server, but legacy issues are forcing my hand. I am attempting to set up a linked server between two new production SQL servers. I have configured SQL on both machines with domain service accounts running MSSQLSvc on each respective SQL instance. The domain service accounts have SPNs registered; I have verified this through AD attribute editor(sp?). I can perform single hop queries on the actual servers, but no luck with the double hop from my laptop (domain admin). I have used the Kerberos Config tool on each server and configured what I can. This is where google falls short on this issue. When I use the Kerberos Config Tool on one of the servers I get this for my service account running MSSQLsvc: TCP must be enabled to use Kerberos authentication. In the SQL server config manager, I have TCP/IP enabled. I have restarted services and the server on several occasions. Any thoughts? I can provide more information.

Does SQL Server Express 2016 come with SQL Server Configuration Manager? If not, is there any licenced way to add SQL Server Configuration Manager to an existing installation of SQL Server Express 2016?

I am having a problem with connectivity in one of my transactional replications and when checking the situation with the SQL Server configuration manager I see there are aliases. I was wonder why they have been created... What aliases are used for in the SQL Server Configuration Manager? Does it have anything to do that in this particular case the machines (publisher and subscriber) are on different domains?

For security reasons, we want to change the password that starts the SQL Server service everyday. Is it possible to do this without restarting the service? If it is possible will the changes be immediately applied, or will I eventually need to restart the service to get the new password? We were thinking of doing this change in the services option of the windows OS and not in SQL Server configuration manager.

We have changed the login/startup account of our SQL Server service, to use a domain service account. However, we are experiencing issues with this account, and need to revert back to using the local NT Service\MSSQL$[namedinstance] account for now. Is there a way of doing this? When prompted for the password in SQL Server Configuration Manager, what does one enter? We never set a password for this previously, but it appears to require one. > The account name is invalid or does not exist, or the password is invalid for the account name specified. [0x80070421]

While I know why are ports used in SQL Server, I wonder what is the difference between an endpoint and a port. Ports can be managed using Configuration Manager, is it also possible to manage endpoints with CM? Thanks for your time.

Even after installing SSMS on a SQL Server Client machine, I found that SQL Server Configuration Manager would not run. Manually loading the mof file via [Microsoft's Instructions](https://support.microsoft.com/en-us/help/956013/error-message-when-you-open-sql-server-configuration-manager-in-sql-se) was sufficient to repair the "Cannot connect to WMI provider" error, but this only caused the 32 bit configuration manager to show up. I also want to configure 64-bit aliases. Historically, I've avoided this problem by using the SQL Server Install Media to install SSMS, but I was hoping this was no longer necessary now that SSMS was released separately. Absent a documented recommendation from Microsoft, I'd rather avoid the commonly suggested hack of copying sqlmgmprovider.dll from other machines.