Creating a new package, updating an existing package, or running a query fails connecting to SQL

  • 29Views
  • Last Post 15 December 2021
0
votes
Ken Banks posted this 13 December 2021

When I attempt to update an existing package, create a new package, or create a new SQL query that connects to our SQL database I get the following error:

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)

I have verified that named pipes are still setup, allowing remote connections, and I have added the new IP address to allow connections to the server. 

The strange part is existing packages still run sucecssfully as do the scheduled pakages using the same connection, which tells me the connection settings are correct. It is a problem with the process or updating connections that is failing.

0
votes
Nataliia Nikulina posted this 15 December 2021

Hello Ken,

 

Thank you for contacting Skyvia Support team.

This error indicates that your SQL server is not configured properly for external connections.

Please check this tutorial for configuration steps:

https://docs.skyvia.com/connectors/databases/sqlserver_connections.html

If the issue continues to happen please specify the exact packages where the issue persists. 

We look forward to hearing from you.

 

Best regards,

Nataliia,

Customer Support Engineer 

Close