Forum Discussion
Data Sources suddenly starting to fail
We have a number of connections defined in our on premise gateway.
Suddenly scheduled refreshes started failing.
There were yellow triangles against the connections when viewing under 'Manage Gateway'.
Error was 'SQL Connection Failed'.
Re-Entering the *same* credentialls immediately responded with connection succeeded.
A few minutes later, the yellow triangle comes back with 'SQL Connection Failed'.
We can re-enter the credentials again, and it succeeds. But always after a few minutes the Yellow Triangle comes back.
The Gateway was upgraded to the latest, as it was old, Nov 2020. It's now at October 2021.
The server has been rebooted as has the gateway service.
The connection still return failure after a few minutes of re-applying the credentials and initially succeeding.
Hi Nick_D ,
You can first reconfigure the SQL Server data source in Manage Gateway as suggested by GilbertQ and check if similar problems still exist after restarting the gateway.
I can see here that the information you provided is a SQL Server connection issue, it would be nice to have more detailed information on the error message.
To effectively use this troubleshooter, you may want to gather the following information.
1.The complete text of the error message along with the error codes and whether the error is intermittent (happens only sometimes) or consistent (happens all the time).
2.Errorlogs from SQL Server from which you can note the following:
A. Fully qualified domain name (FQDN) of the SQL Server machine or in case of clustered installations, the FQDN virtual name. If you are using a named instance, note down the instance name.
B.Network libraries and ports the SQL instance is listening on.
3.Application and System event logs from SQL Server and Client systems.
4.If the connections are failing from an application, the connection string from the app. These are typically found in Web.config files for ASP.NET applications.
For more information，you can refer to：Resolving connectivity errors to SQL Server
If I have not understood your needs correctly, please do not hesitate to inform me.
Hope it helps,
Community Support Team _ CaitlynIf this post helps then please consider Accept it as the solution to help the other members find it more quickly.
3 Replies
Hi Nick_D ,
You can first reconfigure the SQL Server data source in Manage Gateway as suggested by GilbertQ and check if similar problems still exist after restarting the gateway.
I can see here that the information you provided is a SQL Server connection issue, it would be nice to have more detailed information on the error message.
To effectively use this troubleshooter, you may want to gather the following information.
1.The complete text of the error message along with the error codes and whether the error is intermittent (happens only sometimes) or consistent (happens all the time).
2.Errorlogs from SQL Server from which you can note the following:
A. Fully qualified domain name (FQDN) of the SQL Server machine or in case of clustered installations, the FQDN virtual name. If you are using a named instance, note down the instance name.
B.Network libraries and ports the SQL instance is listening on.
3.Application and System event logs from SQL Server and Client systems.
4.If the connections are failing from an application, the connection string from the app. These are typically found in Web.config files for ASP.NET applications.
For more information，you can refer to：Resolving connectivity errors to SQL Server
If I have not understood your needs correctly, please do not hesitate to inform me.
Hope it helps,
Community Support Team _ CaitlynIf this post helps then please consider Accept it as the solution to help the other members find it more quickly.
Hi Nick_D ,
Does the replies above solve your problem? If it has been solved, please mark the correct reply as the standard answer to help the other members find it more quickly.Thanks in advance for your kind cooperation!
Hope it helps,
Community Support Team _ CaitlynIf this post helps then please consider Accept it as the solution to help the other members find it more quickly.
