SOLVED
SQL Error
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
SKC
5 - Atom
‎01-28-2022
02:45 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi, I am trying to run a workflow and I have started getting a new SQL error from a data source I normally don't have any problems with. Can someone help me? Here is the error. Error: Input Data (18): Error SQLExtendedFetch: [Microsoft][ODBC Driver 17 for SQL Server]Error in row[Microsoft][ODBC Driver 17 for SQL Server]TCP Provider: An existing connection was forcibly closed by the remote host. [Microsoft][ODBC Driver 17 for SQL Server]Communication link failure[Microsoft][ODBC Driver 17 for SQL Server]Session Provider: Physical connection is not usable [xFFFFFFFF]. [Microsoft][ODBC Driver 17 for SQL Server]Communication link failure[Microsoft][ODBC Driver 17 for SQL Server]Session Provider: Physical connection is not usable [xFFFFFFFF]. [Microsoft][ODBC Driver 17 for SQL Server]Communication link failure[Microsoft][ODBC Driver 17 for SQL Server]Session Provider: Physical connection is not usable [xFFFFFFFF]. [Microsoft][ODBC Driver 17 for SQL Server]Communication link failure
Solved! Go to Solution.
Labels:
- Labels:
- Error Message
2 REPLIES 2
gabrielvilella
14 - Magnetar
‎01-28-2022
03:07 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
jrsheppard
7 - Meteor
‎01-28-2022
05:41 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
I would check if your SQL Server instance was switched to a different Server, or if any permissions were changed. You can check if you still have access by going to Start > ODBC Data Sources (64 bit) > Add > ODBC Driver 17 for SQL Server > Enter the correct credentials > Test. If the ODBC DSN doesn't work, it will spit out a clearer error code. If there's an error on the ODBC DSN, then it's not an Alteryx issue.
