A connection attempt failed because the connected party did not properly respond after a period of time while testing Linked Service in Azure Synapse

Raghul Kannan 126

Hi,

I get the following error when I try to test connection to linked service from my Azure Synapse Analytics Studio.

A connection attempt failed because the connected party did not properly respond after a period of time.

ADLS Gen2 operation failed for: An error occurred while sending the request.. Account: 'xxxxx- devcurated'..

An error occurred while sending the request.

Unable to connect to the remote server

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond XX.XXX.XX.XXX:443

Vinodh247-1375 11,476 Reputation points

2023-07-20T08:45:32.12+00:00

Hi Raghul Kannan: the error is straight forward, the linked service is unable to reach out to the adls storage to make a connection. are you sure both your synapse adls are in the same subscription?
Raghul Kannan 126 Reputation points

2023-07-20T08:48:45.9333333+00:00

Hi @Vinodh247,

Yes, they are. Infact, I'm able to even look at data in storage account through "Data" hub. Plus, I have other storage accounts which are fine. Only issue is with this storage account.
KranthiPakala-MSFT 46,427 Reputation points Microsoft Employee

2023-07-20T15:35:20.3666667+00:00
@Raghul Kannan Thanks for using Microsoft Q&A forum and posting your query.

I'm able to even look at data in storage account through "Data" hub - Do you mean that you were able to see the data of the same storage account that is having linked service connection issue?

Also please confirm below:

Are there any firewall rules configured in your storage account firewall settings?

What credentials are being used to establish the connection from Synapse linked service the is resulting in error? Please ensure those details are correct. I would also recommend playing around with different auth types and see if it makes a difference.

If you are using Azure IR, can you try using SHIR and ensure that you whitelist the SHIR IP Address to access the storage account. This test is to check if it is related to firewall issue with your ADLS blocking your Azure IR IP range.

Is your Synapse workspace with Managed Vnet enabled?

Also recommend to go through this document and try to suggestion to see if that helps: Troubleshoot the Azure Data Lake Storage connectors in Azure Data Factory and Azure Synapse

Let us know how it goes.
Raghul Kannan 126 Reputation points

2023-07-20T17:43:05.2333333+00:00
Hi @KranthiPakala-MSFT ,

Do you mean that you were able to see the data of the same storage account that is having linked service connection issue? Yes

Are there any firewall rules configured in your storage account firewall settings? No, I have others storage accounts in same subscriptions which are working fine, which are in same VNET/subnets

I use System Assigned

Yes, Managed VNET is enabled. Like I said previously I have other storage accounts which are working perfectly
Raghul Kannan 126 Reputation points

2023-07-20T18:19:46.6733333+00:00

Hi @KranthiPakala-MSFT ,

I did a little more digging the looks like the issue is with adding managed private endpoint. It says it already exists though it's not. I get the error shown below

Failed to save AzureDataLakeStorage3. Error: {"CorrelationId":"","StatusCode":409,"Message":"Resource already exists: Message=Private endpoint already exists in the vnet /subscriptions/c3b59e49-549f-49ff-9733-ac01e9f417a4/resourceGroups/vnet-c3b59e49-westeurope-102-rg/providers/Microsoft.Network/virtualNetworks/vnet-c3b59e49-westeurope-102 with PEReferenceName Drop and status Disconnected. Client id: d51a4cab-86b1-4328-b7b7-5b2e762edfca, Cluster: d51a4cab-86b1-4328-b7b7-5b2e762edfca. RequestedPEReferenceName: AzureDataLakeStorage3","ExceptionDetail":"Microsoft.Analytics.Clusters.Common.NetworkServiceException: Private endpoint already exists in the vnet /subscriptions/removed/resourceGroups/vnet-c3b59e49-westeurope-102-rg/providers/Microsoft.Network/virtualNetworks/vnet-c3b59e49-westeurope-102 with PEReferenceName Drop and status Disconnected. Client id: d51a4cab-86b1-4328-b7b7-5b2e762edfca, Cluster: d51a4cab-86b1-4328-b7b7-5b2e762edfca. RequestedPEReferenceName: AzureDataLakeStorage3\r\n at Microsoft.Analytics.Clusters.Services.NetworkService.NetworkServiceImpl.AddPrivateEndpointAsync(PrivateEndpointRequest request, AbstractMetadataContext dbContext) in C:\__w\1\s\Services\NetworkService\Service\NetworkServiceImpl.cs:line 3343\r\n at Microsoft.Analytics.Clusters.Services.NetworkService.StatefulBE.Controllers.NetworkController.AddPrivateEndpointAsync(String clientId, String privateEndpointReferenceName, PrivateEndpointRequest request) in C:\__w\1\s\Services\NetworkService\NetworkServiceBE\Controllers\NetworkController.cs:line 313\r\n at lambda_method66262(Closure , Object )\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.AwaitableObjectResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeActionMethodAsync>g__Awaited|12_0(ControllerActionInvoker invoker, ValueTask`1 actionResultValueTask)\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeNextActionFilterAsync>g__Awaited|10_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()\r\n--- End of stack trace from previous location ---\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResourceFilter>g__Awaited|25_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContextSealed context)\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeFilterPipelineAsync()\r\n--- End of stack trace from previous location ---\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope)\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope)\r\n at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)\r\n at Microsoft.Analytics.Clusters.Services.NetworkService.StatefulBE.ActivePartitionInstanceMiddleware.InvokeAsync(HttpContext context) in C:\__w\1\s\Services\NetworkService\NetworkServiceBE\ActivePartitionInstanceMiddleware.cs:line 90\r\n at Microsoft.Analytics.Clusters.Common.Web.Throttling.ThrottlingMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) in C:\__w\1\s\Shared\Web\Throttling\ThrottlingMiddleware.cs:line 60\r\n at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.<>c__DisplayClass6_1.<<UseMiddlewareInterface>b__1>d.MoveNext()\r\n--- End of stack trace from previous location ---\r\n at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.<>c__DisplayClass6_1.<<UseMiddlewareInterface>b__1>d.MoveNext()\r\n--- End of stack trace from previous location ---\r\n at Microsoft.Analytics.Clusters.Common.Web.ServiceFabricResourceNotFoundMiddleware.InvokeAsync(HttpContext httpContext) in C:\__w\1\s\Shared\Web\ServiceFabricResourceNotFoundMiddleware.cs:line 50\r\n at Microsoft.Analytics.Clusters.Common.Web.ExceptionMiddleware.InvokeAsync(HttpContext httpContext) in C:\__w\1\s\Shared\Web\ExceptionMiddleware.cs:line 59","ErrorType":"PrivateEndpointAlreadyExists","ErrorNumber":2141,"ErrorOn":"2023-07-20T18:13:47.5787213+00:00"}

Accepted answer

KranthiPakala-MSFT 46,427 Reputation points Microsoft Employee

2023-07-24T19:55:45.1066667+00:00
@Raghul Kannan

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 .

Error Message:

Unable to connect to the remote server

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond XX.XXX.XX.XXX:443

Issue:

When trying to test connection to ADLS Gen2 linked service from Azure Synapse Analytics Studio, it throws the above error.

Solution:

Issue seems to be with multiple deployments using bicep. One of the deployments may have corrupted the template and resulted that Azure Synapse analytics thinks managed private endpoint exists even though they don't. The User has deleted the Azure Synapse analytics and recreated which fixed the issue permanently. Hence the issue caused due to multiple deployments.

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.

I hope this helps!

If you have any other questions, please let me know. Thank you again for your time and patience throughout this issue.

Please don’t forget to Accept Answer and Yes for "was this answer helpful" wherever the information provided helps you, this can be beneficial to other community members.
Please sign in to rate this answer.
Nick Wong 170 Reputation points

2024-05-13T08:47:25.2633333+00:00

Hello @KranthiPakala-MSFT ,

I have the same issue, does it meant deleting the whole application on azure and restarted it again, I am a bit confused with this solution
Sign in to comment

1 additional answer

Raghul Kannan 126 Reputation points

2023-07-24T03:54:58.1766667+00:00

Hi,

The issue seems to be with multiple deployments using bicep and for some reason because of it Azure Synapse analytics thinks managed private endpoint exists even though they don't, I deleted the Azure Synapse analytics and recreated which fixed the issue.
Please sign in to rate this answer.
Vinodh247-1375 11,476 Reputation points

2023-07-24T05:40:53.87+00:00

Thanks for sharing the resolution, Raghul Kannan.
Sign in to comment

Share via

A connection attempt failed because the connected party did not properly respond after a period of time while testing Linked Service in Azure Synapse

1 additional answer