Getting a SQL connection error when adding Skillsets on an indexer

Eugene Zhuravel 0

I have an indexer that gets data from an Azure database and stores it in an index successfully. Once I add any skillset to the indexer, 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: TCP Provider, error: 0 - 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.)

I tried to get a debugging session going, but it also gives me the same error and doesn't run

brtrach-MSFT 15,366 Reputation points Microsoft Employee

2024-05-25T03:38:22.5266667+00:00
@Eugene Zhuravel It seems like there is an issue with the connectivity to the SQL server when you add a skillset to the indexer. This could be due to a number of reasons, such as incorrect connection string, firewall settings, or authentication issues.

To troubleshoot this issue, you can try the following steps:

See if the connection string you are using is correct and complete. Make sure that it includes the server name, database name, and authentication details.

Check the firewall settings on the SQL server to ensure that the IP address of the machine running the indexer is allowed to connect to the server.

Verify that the authentication details you are using are correct and have sufficient permissions to access the database.

Check the SQL server logs for any errors or warnings that might indicate the cause of the issue.

Try to run the skillset on a smaller dataset to see if the issue is related to the size of the data being processed.

Share via

Getting a SQL connection error when adding Skillsets on an indexer