Dynamic Input Tool Error
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
All,
I have a dynamic input tool set up to run some preSQL processing. I have the correct server and everything in the "Edit" box for the input data source template configuration. When I run, I get the following error:
[Microsoft][SQL Server Native Client 11.0][SQL Server]Named Pipes Provider: Could not open a connection to SQL Server [53]. [Microsoft][SQL Server Native Client 11.0][SQL Server]OLE DB provider "SQLNCLI11" for linked server "dummy server" returned message "Login timeout expired".
I'm calling that dummy server just to keep it undisclosed.
The issue is, "dummy server" is not referenced anywhere in the tool or workflow and is not the same server I established in the input data source template so I have no clue how or why Alteryx is even referencing that server. Does anyone have any thoughts?
- Labels:
- Dynamic Processing
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
hard to tell without looking at your dynamic input config. are you using a named database source? is the server specified in your odbc driver set up?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
@avoncuster23 please add some screen shots of configuration and error message.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
The server "A" <> "B". I don't know why the process is trying to connect to server "B".
  
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
This server says your named server is linked to the other server via a SQL Server linked server (https://learn.microsoft.com/en-us/sql/relational-databases/linked-servers/create-linked-servers-sql-...) if that's not the case - talk to your DB Admin. My hunch is this may not be an Alteryx thing.
