Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
8,960 questions
Anyone else having trouble using Hybrid Connection Manager from a Linux App Service?
Bazul
1
Reputation point
.NET Core 3.1 App->Update .NET 6 LTS
Windows App Service -> HCM -> Host (Win 2016 Standard, HCM v0.7.7 agent)-> SQL server
This works. We're using DNS name of SQL Server not IP, standard port 1433, I can ping SQL server. All documented troubleshooting steps confirmed on the host.
443 is open
Test-NetConnection <SQL Server DNS name> -P 1433 returns successful result.
Application code functions properly, connects and returns data from on-prem SQL server.
Linux App Service (using same code base ->Update .NET 6 LTS, same host and SQL server)
Does not work
We're using DNS name of SQL Server not IP, standard port 1433, I can ping SQL server from the host. All documented troubleshooting steps confirmed on the host.
443 is open
Test-NetConnection <SQL Server DNS name> -P 1433 returns successful result.
But the .NET app deployed to a Linux App Service spins, times out and eventually returns a HTTP ERROR 504 or throws a exception. Tried both machine name of SQL server as well as fully qualified name (both tcpping just fine) but the when run in a Linux based App Service can't connect.
Microsoft.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 35 - An internal exception was caught)---> System.Net.Internals.SocketExceptionFactory+ExtendedSocketException (00000005, 0xFFFDFFFF): Name or service not known
Azure App Service
{count} votes
-
brtrach-MSFT 17,741 Reputation points Microsoft Employee Moderator2021-12-31T07:11:21.483+00:00 We have reached out to this customer in a private message. If the community has any input or similar experiences, please continue the discussion here.
-
![](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(131.20000000000002, 59%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
Anuruddha Singh 1 Reputation point Microsoft External Staff2022-12-02T22:16:47.287+00:00 I have similar problem while trying to connect to On-Prem SSAS cube from Azure Durable Function.
Setup-
Azure Function using microsoft ADOMDClient library and MSOLAP connection to connect to SSAS cube and pull data using DAX query.
Remote SSAS cube server is connecting using 2383 port.
Code works fine on dev environment
Now- Deployed Code to Azure Function
Created Hybrid connection in networking to SSAS cube with hostname and port
Installed HCM software on On-prem machine and able to add Hybrid connection created in azure portal.
Status of hybrid connection is Connected. On Azure portal also it is showing connected
Able to TCPPING SSAS server from azure function console for port 2383
Result Test-NetConnection on HCM host machine for SSAS cube is fine (true)
Result of Test-NetConnection on HCM machine for Azure IP and port 80 , 443
But when running Azure function app, not able to open connection with source server with error-- Exception - Check if server is running-Also troubleshooted Evet log for HCM client- No error but getting Information level error for every Azure Function Run as-
System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult) at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult) --- End of inner exception stack traceWhat I am missing here, if anyone can help.
Thanks
-
Mike 6 Reputation points2022-12-06T19:19:43.743+00:00 In our case we believe the issue to be the ancient version of Windows and\or SQL Server that we're trying to connect to (still have yet to upgrade it so we can't confirm but we were able to connect to a newer SQL Server on a new version of Windows from the Linux App Service, even the old DB and OS works fine from a Windows App Service).
In your case, I'm not a SSAS person or even close but... I'd first double check connection strings and rule out security access to the resource you're trying to connect to (I know, I'm sure you have but humor me there) and then second I'd make sure that this type of connection doesn't rely on dynamic ports. If everything else checks out ok and you're sure the connection string is good I'd think about this:
Things you cannot do with Hybrid Connections
Things you cannot do with Hybrid Connections include:- Mount a drive.
- Use UDP.
- Access TCP-based services that use dynamic ports, such as FTP Passive Mode or Extended Passive Mode.
- Support LDAP, because it can require UDP.
- Support Active Directory, because you cannot domain join an App Service worker.
Then given our issue...how old is the SQL Server you're using for SSAS and how old is the OS.
Sign in to comment
Sign in to answer