Connection Error from Alteryx - Intermittent Connection Just Started

[Jason Davis]

Connections from Alteryx to Enterprise Insights from Alteryx vis OLEDB have been fine for over a year but suddenly receiving intermittent fails.  Appears to be some type of timeout issue but unsure as to how to resolve.  

Anyone else encountered this and resolved successfully?

Here's the error.

Error: Input Data (2): Error opening connect string: Microsoft OLE DB Driver for SQL Server: Login timeout expired\HYT00 = 0; Microsoft OLE DB Driver for SQL Server: A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.\08001 = 53; Microsoft OLE DB Driver for SQL Server: Named Pipes Provider: Could not open a connection to SQL Server [53]. \08001 = 53

Thanks

[Jason Davis]

Hi Sam.  Thanks for the quick response.  IP address for our Alteryx instance has not changed recently.  

[Sam Tsubota]

I suggest also checking with your network team to see if any firewall or network configurations were changed recently that may be blocking traffic to the port that is used to connect to Enterprise Insights. 

[Jason Davis]

I can check but again it's not a full block.  We connect but it's not consistent.  Might connect 5 times in a row but then fail once or 3 times straight.  

[Sam Tsubota]

The reason why I suggested checking these things because Enterprise Insights access is just IP whitelisting and either SQL login or Azure AD authentication. Since you are able to connect to Enterprise Insight, albeit not consistently, that rules out issues with IP whitelisting or SQL login authentication. The biggest variable with most connectivity issues is the customer's corporate network and firewall configurations. If you are unable connect to Enterprise Insights, the Atlassian team most likely won't see any error in the logs because no connection was established or know why the connection failed. You can open a support ticket to see if your Enterprise Insights instance is experiencing any intermittent downtime. 

[Sam Tsubota]

@Jason Davis You should to check to see if the network IP address for your Alteryx instance was changed recently. When your Enterprise Insights instance was set up a range of IP addresses for your corporate network was whitelisted by Atlassian to restrict access to users/application on your network. If the IP address has changed recently, you will need to submit a support ticket to Jira Align support to have the new IP address(es) whitelisted. Are you able to connect to Enterprise Insights from Azure Data Studio or SQL Server Management Studio when you are on your corporate network?