Connectivity from Azure extension for SQL Server to DPS is not OK

Question

Connectivity from Azure extension for SQL Server to DPS is not OK

Jonathan Hobdell 20

Hi

I'm trying to register my machine / on-prem SQL Server instance with my Azure subscription. I've done it two different ways because the first one failed. In both cases the machine seemed to register successfully (it's visible within Azure Arc), but both times, I get the subject message:

Connectivity from Azure extension for SQL Server to DPS is not OK (Status: null, Message: null)

As a result, neither the SQL Server instance nor any of its databases are visible. I've got lost trying to find stuff in the docs. Does anyone have any idea what's going wrong here?

Thanks so much!

Jonathan Hobdell 20 Reputation points

2024-10-30T11:56:59.1166667+00:00

Found a tag that I didn't apply:

ArcSQLServerExtensionDeployment: Disabled

But that wasn't the solution.
Sai Raghunadh M 4,640 Reputation points Microsoft External Staff Moderator

2024-10-30T18:45:52.9466667+00:00

Hi @Jonathan Hobdell,

Thanks for the question and using MS Q&A platform.

Make sure your SQL Server instance can access Azure services through the necessary ports. Generally, you need to have ports 443 (HTTPS) and 5671 (AMQP) open for the Azure extension to communicate with Azure.

please go through this documentation that might help you Troubleshoot connectivity to the data processing service and telemetry endpoints.

I hope this information helps, please do let us know if you have any Queries.
Jonathan Hobdell 20 Reputation points

2024-10-31T10:06:40.8333333+00:00
Hi @Sai Raghunadh M

Thank you for your reply. I have rules for 443 on my firewall, and I've now added 5671 as per your message.

I had previously tried to work through that troubleshooting article with no useful result: the connectivity to both UK South and UK West is fine. Checking the Azure Resource Graph telemetry stats query returns a single result where the upload status is blank. This doesn't match any of the error codes so I assume it's being blocked still, or something similar.

I've also just run the unhealthy extensions check query from here: https://learn.microsoft.com/en-us/sql/sql-server/azure-arc/troubleshoot-extension?view=sql-server-ver16&source=recommendations

And it shows that the extension status is indeed unhealthy, but the Message doesn't contain any useful information to my eyes (see below). And I get the exact same result running it through PowerShell locally.

Any further thoughts on this would be very much appreciated!

Extension Message: {"FailureCount":0,"LastUpdatedTimestamp":"2024\/10\/30, 11:08:41.249","Message":"Completed asyncEnable","SeqNum":0}, SQL Server Extension Agent Deployer: {"FailureCount":0,"LastUpdatedTimestamp":"2024\/10\/30, 11:08:41.249","Message":"Completed asyncEnable","SeqNum":0}
Jonathan Hobdell 20 Reputation points

2024-10-31T10:19:35.97+00:00
Hi @Sai Raghunadh M

Thank you for your reply. I have rules for 443 on my firewall, and I've now added 5671 as per your message.

I had previously tried to work through that troubleshooting article with no useful result: the connectivity to both UK South and UK West is fine. Checking the Azure Resource Graph telemetry stats query returns a single result where the upload status is blank. This doesn't match any of the error codes so I assume it's being blocked still, or something similar.

I've also just run the unhealthy extensions check query from here: https://learn.microsoft.com/en-us/sql/sql-server/azure-arc/troubleshoot-extension?view=sql-server-ver16&source=recommendations

And it shows that the extension status is indeed unhealthy, but the Message doesn't contain any useful information to my eyes (see below). And I get the exact same result running it through PowerShell locally. Any further thoughts on this would be very much appreciated!

Extension Message: {"FailureCount":0,"LastUpdatedTimestamp":"2024\/10\/30, 11:08:41.249","Message":"Completed asyncEnable","SeqNum":0}, SQL Server Extension Agent Deployer: {"FailureCount":0,"LastUpdatedTimestamp":"2024\/10\/30, 11:08:41.249","Message":"Completed asyncEnable","SeqNum":0}
Jonathan Hobdell 20 Reputation points

2024-10-31T15:38:03.0166667+00:00

I have just spotted something that seems to imply that it must be a Windows Server machine, is that right?
Sai Raghunadh M 4,640 Reputation points Microsoft External Staff Moderator

2024-11-01T10:35:52.0666667+00:00

Hi @Jonathan Hobdell,

Yes, Azure Arc for SQL Server requires a Windows Server machine

Review your network settings to make sure that any proxy servers or network appliances aren't interfering with the connection.

Accepted answer

1 additional answer

Your answer

Jonathan Hobdell 20 Reputation points

2024-10-30T11:56:59.1166667+00:00

Found a tag that I didn't apply:

ArcSQLServerExtensionDeployment: Disabled

But that wasn't the solution.
Sai Raghunadh M 4,640 Reputation points Microsoft External Staff Moderator

2024-10-30T18:45:52.9466667+00:00

Hi @Jonathan Hobdell,

Thanks for the question and using MS Q&A platform.

Make sure your SQL Server instance can access Azure services through the necessary ports. Generally, you need to have ports 443 (HTTPS) and 5671 (AMQP) open for the Azure extension to communicate with Azure.

please go through this documentation that might help you Troubleshoot connectivity to the data processing service and telemetry endpoints.

I hope this information helps, please do let us know if you have any Queries.
Jonathan Hobdell 20 Reputation points

2024-10-31T10:06:40.8333333+00:00

Hi @Sai Raghunadh M

Thank you for your reply. I have rules for 443 on my firewall, and I've now added 5671 as per your message.

I had previously tried to work through that troubleshooting article with no useful result: the connectivity to both UK South and UK West is fine. Checking the Azure Resource Graph telemetry stats query returns a single result where the upload status is blank. This doesn't match any of the error codes so I assume it's being blocked still, or something similar.

I've also just run the unhealthy extensions check query from here: https://learn.microsoft.com/en-us/sql/sql-server/azure-arc/troubleshoot-extension?view=sql-server-ver16&source=recommendations

And it shows that the extension status is indeed unhealthy, but the Message doesn't contain any useful information to my eyes (see below). And I get the exact same result running it through PowerShell locally.

Any further thoughts on this would be very much appreciated!

Extension Message: {"FailureCount":0,"LastUpdatedTimestamp":"2024\/10\/30, 11:08:41.249","Message":"Completed asyncEnable","SeqNum":0}, SQL Server Extension Agent Deployer: {"FailureCount":0,"LastUpdatedTimestamp":"2024\/10\/30, 11:08:41.249","Message":"Completed asyncEnable","SeqNum":0}
Jonathan Hobdell 20 Reputation points

2024-10-31T10:19:35.97+00:00

Hi @Sai Raghunadh M

Thank you for your reply. I have rules for 443 on my firewall, and I've now added 5671 as per your message.

I had previously tried to work through that troubleshooting article with no useful result: the connectivity to both UK South and UK West is fine. Checking the Azure Resource Graph telemetry stats query returns a single result where the upload status is blank. This doesn't match any of the error codes so I assume it's being blocked still, or something similar.

I've also just run the unhealthy extensions check query from here: https://learn.microsoft.com/en-us/sql/sql-server/azure-arc/troubleshoot-extension?view=sql-server-ver16&source=recommendations

And it shows that the extension status is indeed unhealthy, but the Message doesn't contain any useful information to my eyes (see below). And I get the exact same result running it through PowerShell locally. Any further thoughts on this would be very much appreciated!

Extension Message: {"FailureCount":0,"LastUpdatedTimestamp":"2024\/10\/30, 11:08:41.249","Message":"Completed asyncEnable","SeqNum":0}, SQL Server Extension Agent Deployer: {"FailureCount":0,"LastUpdatedTimestamp":"2024\/10\/30, 11:08:41.249","Message":"Completed asyncEnable","SeqNum":0}
Jonathan Hobdell 20 Reputation points

2024-10-31T15:38:03.0166667+00:00

I have just spotted something that seems to imply that it must be a Windows Server machine, is that right?
Sai Raghunadh M 4,640 Reputation points Microsoft External Staff Moderator

2024-11-01T10:35:52.0666667+00:00

Hi @Jonathan Hobdell,

Yes, Azure Arc for SQL Server requires a Windows Server machine

Review your network settings to make sure that any proxy servers or network appliances aren't interfering with the connection.

Answer 1

Hi @Jonathan Hobdell,

I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to accept the answer.

Issue:

I'm trying to register my machine / on-prem SQL Server instance with my Azure subscription. I've done it two different ways because the first one failed. In both cases the machine seemed to register successfully (it's visible within Azure Arc), but both times, I get the subject message:

Connectivity from Azure extension for SQL Server to DPS is not OK (Status: null, Message: null)

As a result, neither the SQL Server instance nor any of its databases are visible. I've got lost trying to find stuff in the docs. Does anyone have any idea what's going wrong here?

Solution:

I eventually managed to get this working. The documentation is very thorough, but extremely confusing sometimes, and I suspect out of date in places.

Here's what I established, in case it's helpful to anyone else some time:

Install Azure Extension via installation centre - steps should be fairly straightforward if you know Azure Portal even a little bit
Install Azure Arc Agent following steps here: https://learn.microsoft.com/en-us/azure/network-watcher/connection-monitor-connected-machine-agent?tabs=WindowsScript
- Basically, register single server after searching "Servers - Azure Arc" in Azure Portal
- In Azure Portal, under Azure Arc, click Data Services > SQL Server Instances
Click Add and follow the steps to create the script and run it locally via PowerShell (you may need to install the Azure PowerShell module and / or change the execution policy for your local machine account) If I missed anything please let me know and I'd be happy to add it to my answer, or feel free to comment below with any additional information. Hope this helps. Do let us know if you have any further queries. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Jonathan Hobdell 20 Reputation points

2024-11-01T11:58:02.82+00:00

Thank you, @Sai Raghunadh M ! Have a great day!
Sai Raghunadh M 4,640 Reputation points Microsoft External Staff Moderator

2024-11-01T12:00:33.6+00:00

Thanks @Jonathan Hobdell Have a great day.

Answer 2

I eventually managed to get this working. The documentation is very thorough, but extremely confusing sometimes, and I suspect out of date in places.

Here's what I established, in case it's helpful to anyone else some time:

Install Azure Extension via installation centre - steps should be fairly straightforward if you know Azure Portal even a little bit
Install Azure Arc Agent following steps here: https://learn.microsoft.com/en-us/azure/network-watcher/connection-monitor-connected-machine-agent?tabs=WindowsScript
- Basically, register single server after searching "Servers - Azure Arc" in Azure Portal
In Azure Portal, under Azure Arc, click Data Services > SQL Server Instances
Click Add and follow the steps to create the script and run it locally via PowerShell (you may need to install the Azure PowerShell module and / or change the execution policy for your local machine account)

Sai Raghunadh M 4,640 Reputation points Microsoft External Staff Moderator

2024-11-01T11:47:28.37+00:00

Hi @Jonathan Hobdell,

Glad to know that your issue has been resolved. And thanks for sharing the solution, which might be beneficial to other community members reading this thread.

Share via

Connectivity from Azure extension for SQL Server to DPS is not OK

1 additional answer

Your answer