Unable to connect to SQL Server instance of an Azure VM from Azure Databricks - TCP/IP connection on port 1433 failed · Issue #42 · Azure/azure-sqldb-spark · GitHub
![Troubleshooting: SUnable to start SQL Server Service due to TCP Port is already being used - AutoCount Resource Center Troubleshooting: SUnable to start SQL Server Service due to TCP Port is already being used - AutoCount Resource Center](https://static.miraheze.org/autocountwiki/6/6e/Tcp_being_used1.png)
Troubleshooting: SUnable to start SQL Server Service due to TCP Port is already being used - AutoCount Resource Center
ERROR: "Verify the server and instance names and check that no firewall is blocking UDP traffic to port 1434. For SQL Server 2005 or later, verify that the SQL Server Browser Service
![How to assign a static port to a SQL Server named instance – and avoid a common pitfall | Arvind Shyamsundar's technical blog How to assign a static port to a SQL Server named instance – and avoid a common pitfall | Arvind Shyamsundar's technical blog](https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/64/64/metablogapi/5857.image_0F14BAA7.png)