Sql server configuration manager как запустить

Name already in use

sql-docs / docs / relational-databases / sql-server-configuration-manager.md

• Go to file T
• Go to line L
• Copy path
• Copy permalink

• Open with Desktop
• View raw
• Copy raw contents Copy raw contents

Copy raw contents

Copy raw contents

SQL Server Configuration Manager

[!INCLUDEssNoVersion] Configuration Manager is a tool to manage the services associated with [!INCLUDEssNoVersion], to configure the network protocols used by [!INCLUDEssNoVersion], and to manage the network connectivity configuration from [!INCLUDEssNoVersion] client computers. Beginning with [!INCLUDE sssql22-md], can use Configuration Manager to manage the Azure extension for SQL Server.

[!INCLUDEssNoVersion] Configuration Manager is installed with your SQL Server installation. [!INCLUDEssNoVersion] Configuration Manager is a [!INCLUDEmsCoName] Management Console snap-in that is available from the Start menu, or can be added to any other [!INCLUDEmsCoName] Management Console display. [!INCLUDEmsCoName] Management Console (mmc.exe) uses the SQLServerManager<version>.msc file (such as SQLServerManager13.msc for [!INCLUDEsssql15-md]) to open Configuration Manager. You will need the corresponding [!INCLUDEssNoVersion] Configuration Manager version to manage that particular version of [!INCLUDEssNoVersion]. Here are the paths to the last five versions when Windows is installed on the C drive.

Version	Path
[!INCLUDEssNoVersion] 2022	C:\Windows\SysWOW64\SQLServerManager16.msc
[!INCLUDEssNoVersion] 2019	C:\Windows\SysWOW64\SQLServerManager15.msc
[!INCLUDEssNoVersion] 2017	C:\Windows\SysWOW64\SQLServerManager14.msc
[!INCLUDEssNoVersion] 2016	C:\Windows\SysWOW64\SQLServerManager13.msc
[!INCLUDEssSQL14]	C:\Windows\SysWOW64\SQLServerManager12.msc
[!INCLUDEssSQL11]	C:\Windows\SysWOW64\SQLServerManager11.msc

• Windows 10 or 11:
  To open [!INCLUDEssNoVersion] Configuration Manager, navigate to the file location listed above for your version. Click SQLServerManager16.msc to open the Configuration Manager. You can also right-click SQLServerManager16.msc to pin the Configuration Manager to the Start Page or Task Bar.

• Windows 8:
  To open [!INCLUDEssNoVersion] Configuration Manager, in the Search charm, under Apps, type SQLServerManager<version>.msc such as SQLServerManager13.msc, and then press Enter.

[!INCLUDEssNoVersion] Configuration Manager and SQL Server Management Studio use Window Management Instrumentation (WMI) to view and change some server settings. WMI provides a unified way for interfacing with the API calls that manage the registry operations requested by the [!INCLUDEssNoVersion] tools and to provide enhanced control and manipulation over the selected SQL services of the [!INCLUDEssNoVersion] Configuration Manager snap-in component. For information about configuring permissions related to WMI, see Configure WMI to Show Server Status in SQL Server Tools.

To start, stop, pause, resume, or configure services on another computer by using [!INCLUDEssNoVersion] Configuration Manager, see Connect to Another Computer (SQL Server Configuration Manager).

Use [!INCLUDEssNoVersion] Configuration Manager to start, pause, resume, or stop the services, to view service properties, or to change service properties.

Use [!INCLUDEssNoVersion] Configuration Manager to start the [!INCLUDEssDE] using startup parameters. For more information, see Configure Server Startup Options (SQL Server Configuration Manager).

Beginning with [!INCLUDE sssql22-md], you can use [!INCLUDEssNoVersion] Configuration Manager to start, pause, resume, or stop Azure extension for SQL Server.

Changing the Accounts Used by the Services

Manage the [!INCLUDEssNoVersion] services using [!INCLUDEssNoVersion] Configuration Manager.

[!IMPORTANT]
Always use [!INCLUDEssNoVersion] tools such as [!INCLUDEssNoVersion] Configuration Manager to change the account used by the [!INCLUDEssNoVersion] or [!INCLUDEssNoVersion] Agent services, or to change the password for the account. In addition to changing the account name, [!INCLUDEssNoVersion] Configuration Manager performs additional configuration such as setting permissions in the Windows Registry so that the new account can read the [!INCLUDEssNoVersion] settings. Other tools such as the Windows Services Control Manager can change the account name but do not change associated settings. If the service cannot access the [!INCLUDEssNoVersion] portion of the registry the service may not start properly.

As an additional benefit, passwords changed using [!INCLUDEssNoVersion] Configuration Manager, SMO, or WMI take affect immediately without restarting the service.

Manage Server & Client Network Protocols

[!INCLUDEssNoVersion] Configuration Manager allows you to configure server and client network protocols, and connectivity options. After the correct protocols are enabled, you usually do not need to change the server network connections. However, you can use [!INCLUDEssNoVersion] Configuration Manager if you need to reconfigure the server connections so [!INCLUDEssNoVersion] listens on a particular network protocol, port, or pipe. For more information about enabling protocols, see Enable or Disable a Server Network Protocol. For information about enabling access to protocols through a firewall, see Configure the Windows Firewall to Allow SQL Server Access.

[!INCLUDEssNoVersion] Configuration Manager allows you to manage server and client network protocols, including the ability to force protocol encryption, view alias properties, or enable/disable a protocol.

[!INCLUDEssNoVersion] Configuration Manager allows you to create or remove an alias, change the order in which protocols are used, or view properties for a server alias, including:

Server Alias — The server alias used for the computer to which the client is connecting.

Protocol — The network protocol used for the configuration entry.

Connection Parameters — The parameters associated with the connection address for the network protocol configuration.

The [!INCLUDEssNoVersion] Configuration Manager also allows you to view information about failover cluster instances, though Cluster Administrator should be used for some actions such as starting and stopping the services.

Available Network Protocols

[!INCLUDEssNoVersion] supports Shared Memory, TCP/IP, and Named Pipes protocols. For information about choosing a network protocols, see Configure Client Protocols. [!INCLUDEssNoVersion] does not support VIA, Banyan VINES Sequenced Packet Protocol (SPP), Multiprotocol, AppleTalk, or NWLink IPX/SPX network protocols. Clients previously connecting with these protocols must select a different protocol to connect to [!INCLUDEssNoVersion]. You cannot use [!INCLUDEssNoVersion] Configuration Manager to configure the WinSock proxy. To configure the WinSock proxy, see your ISA Server documentation.

Отсутсвует диспетчер конфигурации Microsoft SQL Server или не открывается

Для настройки работы Microsoft SQL Server на специфическом порту нужно воспользоваться диспетчером конфигураций Microsoft SQL Server. Иногда ярлык “Диспетчер конфигурации SQL Server” (“SQL Server Configuration Manager”) отсутствует.

Запуск диспетчера конфигурации вручную

Вручную можно запустить командой:

C:\Windows\SysWOW64\mmc.exe /32 «c:\Windows\SysWOW64\SQLServerManager.msc»
(для 64-битной системы)

C:\Windows\System32\mmc.exe /32 C:\Windows\system32\SQLServerManager.msc
(для x86)

Вместо SQLServerManager.msc может быть другой файл, в зависимости от версии SQL Server, например, SQLServerManager12.msc.

Ошибка ручного запуска

В случае, если команда выдает ошибку 0x8004100e:

«Не удалось подключиться к поставщику WMI. Сервер недоступен или нет разрешения на доступ. Управлять службами SQL Server 2005 можно только с помощью диспетчера конфигурации SQL Server. Недопустимый класс [0x80041010] «

нужно восстановить файл конфигурации поставщика инструментария управления Windows (WMI) для управления службами SQL Server, выполнив:

C:\Program Files (x86)\Microsoft SQL Server\90\Shared\mofcomp sqlmgmproviderxpsp2up.mof
(для 64-битной системы)

C:\Program Files\Microsoft SQL Server\90\Shared\mofcomp sqlmgmproviderxpsp2up.mof
(для x86)

Вместо C:\. \90 может быть другая папка в зависимости от номера версии SQL Server (80, 90, 100, 110, 120 ….). Кроме того, на одном ПК могло быть установлено несколько версий, нужно выбрать актуальную.

Результат запуска

После этого диспетер конфигурации можно будет запустить вручную, как показано в начале.

SQL Server Configuration Manager cannot be found

After installing SQL Server 2008, I cannot find the SQL Server Configuration Manager in Start / SQL Server 2008 / Configuration Tools menu.

What should I do to install this tool?

13 Answers 13

If you happen to be using Windows 8 and up, here’s how to get to it:

The newer Microsoft SQL Server Configuration Manager is a snap-in for the Microsoft Management Console program.

It is not a stand-alone program as used in the previous versions of Microsoft Windows operating systems.

SQL Server Configuration Manager doesn’t appear as an application when running Windows 8.

To open SQL Server Configuration Manager, in the Search charm, under Apps, type:

How to use SQL Server Configuration Manager

SQL Server configuration manager is a tool provided by Microsoft SQL Server. When we install SQL Server, it is installed automatically. It is used for the following purposes.

1. Manage SQL Server services
2. To manage SQL Server network configuration (32 bit and 64 bit)
3. To manage the SQL Server native client configuration
4. Create alias and manage client protocols

The SQL Server configuration manager is a Microsoft console management snap-in and is in the start menu. You can find it once the installation of the SQL Server is completed. To open the configuration manager, Microsoft management console uses the “SQLServerManager<version>.msc” file. For example, if you have installed SQL Server 2019 on the server, then you can open it by running “SQLServerManager15.msc” command.

How to open the SQL Server Configuration Manager in SQL Server 2017

To open configuration manager in SQL Server 2017, press the Windows and R key together. In Run, type “SQLServerManager14.msc” command. The SQL Server configuration manager will open. Following is the list of commands that can be used to open the SQL Server configuration manager using “Run” or command prompt for different versions of SQL Server.

SQL Server version	Command
SQL Server 2019	SQLServerManager15.msc
SQL Server 2017	SQLServerManager14.msc
SQL Server 2016	SQLServerManager13.msc
SQL Server 2014	SQLServerManager12.msc
SQL Server 2012	SQLServerManager11.msc

Manage SQL Server services

We can start, stop, and restart the SQL Server services using the configuration manager. In the Left pan, select the “SQL Server services.” You can view the list of SQL Server services. In my workstation, I have installed multiple instances of SQL Server. Hence, I can manage them from one place. See the following image:

Now, we can start, stop, and restart the SQL Server services. To do that, right-click on any SQL Server service and in the context menu, you can see the options to start, stop, and restart the services. See the following image:

You can also change the startup parameters, enable AlwaysOn availability features, and other advanced options from the properties. To open it, right-click on SQL Server service and click on “Properties.” See the following image:

To change SQL Server startup parameters, click on the “Startup Parameter” tab. See the following image:

To change the SQL Server service account, click on the “Log On” tab. Moreover, you can also start/stop/restart the SQL Server service and view the status of the service. See the following image:

To enable the AlwaysOn availability group, click on the “AlwaysOn High Availability” tab. See the following image:

Manage SQL Server native client configuration

SQL Server native client is a network library that the client uses to connect to the SQL Server. Using the SQL Server configuration manager, we can perform the following tasks:

1. Change Client protocols
2. Create and configure an alias

To change the client protocols, click on “Client Protocols” under the “SQL Native client 11.0 configuration.” See the following image:

Clients can connect to the SQL Server using any of the following protocols.

1. Shared Memory
2. TCP/IP
3. Named Pipes

In the right pane, you can see the list of all the above client protocols. You can enable/disable any of the protocols. To do that, right-click on any of the protocols and select Enable/Disable. See the following image:

We can also define an alias. Alias is an alternate name that can be used to connect to SQL Server. To create a new alias, right-click on Aliases and select “New Alias.” See the following image:

In Alias – New dialog box, provide Alias Name, Port number, a protocol used to connect SQL Server and hostname of the SQL Server. See the following image:

You can read Overview of SQL Server Aliases article to learn more about SQL Server aliases.

Manage SQL Server network configuration

From manage SQL Server network configuration node, you can enable or disable the network protocols supported by SQL Server.

1. Shared Memory
2. TCP/IP
3. Named Pipe

The Shared Memory Protocol

The Shared memory protocol is used by the clients to connect the SQL Server instance on the same server. It is the simplest protocol and does not have any configuration options. You can only disable or enable the protocols that can be done from the properties window. To do that, See the following image:

The TCP/IP Protocol

Using TCP/IP protocols, computers can connect to the SQL Server instance. To configure the TCP/IP settings, right-click on the TCP/IP protocol and choose properties. See the following image:

From the “protocol” tab in the properties dialog box, you can disable or enable the protocol, define the time for how long the connection will remain active and define that whether it can listen to all IP Addresses. See the following image:

In the IP Addresses tab, you can specify the IP Address and the port number on which the SQL Server service will accept the incoming connections. See the following image:

The Named Pipe Protocol

The named pipe protocol is configured for local are network and it is used for inter-process communication. To configure a valid named pipe connection string, right-click on “Named Pipe” and choose properties. Under the protocol tab of the “Named Pipe properties” dialog box, you can specify the valid named pipe connection string in the Pipe Name text box. See the following image:

Summary

In this article, I have explained the SQL Server Configuration Manager and how to use it to configure SQL Server services and its configuration parameters.

Nisarg Upadhyay is a SQL Server Database Administrator and Microsoft certified professional who has more than 8 years of experience with SQL Server administration and 2 years with Oracle 10g database administration.