-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SQL Server Network Configuration Registry Entries Missing #4
Comments
I also have the same problem, all protocols are missing, any ideas? |
I was able to get it to work by enabling what I could through the configuration manager, then going into the registry and manually enabling the protocols for the sqlserver entry (2019 developer). I wouldn't call it fixed as there seems to be missing settings to do it correctly through the config mgr, but the system does now work. |
@shennerf Are you able to share the exact steps and registry keys you had to add/modify to get TCP/IP to work? I have the same issue but have so far been unable to figure out what in the registry needs to be modified. |
@shennerf - that would be amazing as i'm in the same boat. |
So, my install is SQLServer 2019 Developer, though I would expect this will work for all of them. Also - I am connecting to it via IP from another app on the same VM - I did not test connecting to it from a different machine. The entries are not fully correct - but it does work for me when I followed these steps:
Hope this helps |
Thank you @shennerf – for me, with SQL Server 2022 Express, it was sufficient to set Enabled under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL16.SQLEXPRESS\MSSQLServer\SuperSocketNetLib\Tcp to 1 and TcpPort to 1433 under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL16.SQLEXPRESS\MSSQLServer\SuperSocketNetLib\Tcp\IPAll. (With some reservation for the fact that I did change settings back and forth, but I believe that in the end, these are the only ones that differ from the defaults.) I did not find anything relevant at all in the SQL Server Configuration Manager to change (the mentioned configuration item was completely empty), but the registry changes turned out to be sufficient. Obviously, for connections from outside of the virtual machine, the firewall also needs to be set to allow incoming connections to port 1433. And as remote connections with Windows Authentications may or may not work well, it might be necessary to allow SQL Server Authentication, too (under Security in Server Properties in SQL Server Management Studio). |
Thanks, OttoG and shennerf! This was simple and did the trick for me running SQLServerExpress 2022 on Windows 11 Pro version 22H2 Arm.
|
@aleks-f |
@joshuadavidmcgee thanks for replying. The one registry setting seems to have been enough. The problem turned to be elsewhere, in two places:
|
jimm98y - I have used your scripts to try to install all versions except 2022 Express, and I have been unable to get TCPIP on 1433 to work. When researching - it looks like the registry entries for the instance are missing (I do see them on my Windows 10 Intel VM) - Have you seen this issue (Everything else seems to install correctly)?
The text was updated successfully, but these errors were encountered: