This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 70%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJP%3C/text%3E%3C/svg%3E)
REST API from Azure VM using ODBC cannot connect. From on premise can connect
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 79%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3END%3C/text%3E%3C/svg%3E)
Hi Jeffry Piell ,
Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.
Could you kindly share screenshots or any details of the issues to assist in further investigation?
Use answers to provide solutions to the user's question.
Hi Jeffry Piell ,
Thank you for providing information. We are working into it and will get back to you soon.
The port is open. I can access the Azure VM SQL from a local machine,.
From an Azure machine, it will not work.
I have attached all the screenshots to demonstrate the issue.
Hi Jeffry Piell, Please ensure that you have given TCP port 1433 and please refer to this document: https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/configure-a-server-to-listen-on-a-specific-tcp-port?view=sql-server-ver16
Can you please send us the screenshot of the error message that you are facing?
I am using a dsnless connection.
Apparently, the default port is not set to 1433 if the application making the dsnless connection is running in Azure.
Adding the port number (in my case, 1433) to the connection string remedied the issue.
The fix:
Change
"Driver={ODBC Driver 17 for SQL Server};Uid=XXXXXXX;Pwd=XXXXXXXX;Database=XXXXX=your-server-address;"
To this
"Driver={ODBC Driver 17 for SQL Server};Uid=XXXXXXX;Pwd=XXXXXXXX;Database=XXXXX=your-server-address,1433;"
Thank you, Microsoft Support!
We are glad to hear that we were able to resolve your issue.
Please Accept Answer and Upvote the answer that we have given, so that it will be useful to others in the community.
Thank you.
Barnabas,
Support enabled a one-time incident for this issue in response to a post in the forum, which no one could answer. They did this because I agreed to share the solution with the community. Once my product offering goes live, I will purchase the critical business package. I was already thinking about purchasing the business critical package.
Uppara’s excellent support convinced me that the support package is the best option. I will be purchasing support soon. Kudos to you to her, yourself, and your excellent staff! Thank you very much!
Kind regards,
Jeffry A Piell
Genoch, LLC
President