Udostępnij za pośrednictwem

Named Pipes and Azure App Services

  • Artykuł

According to this “Operating system functionality on Azure App Service” and my interpretation, it means if you attempt to use named pipes (*)(*) for anything other than inter-process communications (*) that it will not work.

I was coding some stuff and was getting these errors:

 
SqlException:
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: Named Pipes Provider,
error: 40 - Could not open a connection to SQL Server)

 
[Win32Exception (0x80004005): Access is denied]
[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: Named Pipes Provider, error: 40 - Could not open a connection 
to SQL Server)]

They both called out the provide: Named Pipes Provider and after some searching I found this was not going to work.  I decided to use TCP and all was good.

Comments

  • Anonymous
    July 25, 2018
    How did you implement that change? Did you change your connection string?