Sql network configuration protocols not available

Question

After installing the 32-bit version of SQL Server 2008, I tried to configure it to allow remote access. So I opened SSCM (sql server configuration manager) to enable protocols. I did not find any protocol in the Sql server network configuration ...

I tried to repair, uninstall and reinstall, registers ... Has anyone encountered this before?

Answer 1

It seems that you installed a version that is not compatible with the target OS, for example, an enterprise at 7 !? but maybe this will help by enabling TCP protocol and remote connection using T-SQL

--step 1: creating a login (mandatory) create login login_to_system_after_injection with password=' Thank$SQL4Registry@ccess '; GO --step 2: enabling both windows/SQL Authentication mode /*some server specific configurations are not stored in system (SQL)*/ --set the value to 1 for disabling the SQL Authentication Mode after . . . exec xp_regwrite N'HKEY_LOCAL_MACHINE', N'Software\Microsoft\MSSQLServer\MSSQLServer', N'LoginMode', REG_DWORD, 2; --step 3:getting the server instance name declare @spath nvarchar(256); --SQL SERVER V100 path, use SQL9 for V90 exec master..xp_regread N'HKEY_LOCAL_MACHINE', N'Software\Microsoft\Microsoft SQL Server\Instance Names\SQL' ,N'SQL10',@spath output,no_output --step 4:preparing registry path declare @insRegPath nvarchar(1024)=N'Software\Microsoft\Microsoft SQL Server\' + @spath + '\MSSQLServer\SuperSocketNetLib\Tcp'; --step 5:enabling tcp protocol exec xp_regwrite N'HKEY_LOCAL_MACHINE', @insRegPath, N'Enabled', REG_DWORD, 1 --generally tries to enable all addresses. NOT Recommended --step 6:enabling remote access EXEC sys.sp_configure N'remote access', 1 GO RECONFIGURE WITH OVERRIDE --reconfigure is required! GO --step 7:a system restart is required in order to enabling remote access. --step 7.1:shutting down the server shutdown --After this command you need to start the server implicitly yourself. --or just configure the Agent in order to start the server at any shutdown or failure 

copied from http://www.codeproject.com/Articles/616114/SQL-Server-T-SQL-Tips-Tricks#xp_regeditwrite

Answer 2

I ran into a similar problem when I installed the (second) named instance of SQL Server (2016). The default instance also runs on SQL Server 2016.

2 things to check:

If you installed a 64-bit SQL server, the section "SQL Network Configuration (32-bit)" will be empty. You will have to check in the section "SQL Network Configuration" --- (without specifying 32-bit)

In my case, "SQL Network Configuration" --- (without specifying the 32-bit version) did not appear as an option. I could only see "SQL Network Configuration (32-bit)", which was empty, and "SQL Network Configuration" was missing. I did some research, and then realized that the SQL Server 2017 instance was previously hosted on this server, which was deleted, after which 2 X 2016 instances were installed. The server still had 2017 components, such as SSMS (sql server management studio ), sscm (sql server configuration manager), etc. I opened SQL Server 2017 Server Configuration Manager, where my instances run on SQL Server 2016. Later I manually opened SQL Server Configuration Manager (2016), which had SQL Network Configuration, as expected.

Hope this helps.

Best regards, Kishore