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

Jonathan Hobdell 0

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 0 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 820 Reputation points Microsoft Vendor

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 0 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 0 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}

Share via

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

Your answer