This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
hello. I have what I hope is a simple question. I have built a very simple app that uses some In-DB tools that work great on my desktop computer.
however when I try to publish the app to our analytic gallery, i get the error "Unable to find connection 'MYCONNECT'.
MYCONNECT is the name of the connect that I set up using the drop down option "manage connections" from the Connect in-DB tool, and then I set up the connections in the tool that pops up.... I used a sql server connection and simply followed the prompts...
Do i need to somehow set up the same connection on the server in order for this functionality to work?
To create the connection on your Alteryx Server as a system connection you'll want to make sure Alteryx Designer is running with elevated permissions. To do this find the icon to launch Designer. Rather than double clicking it right click on it and choose Run as Admin. When Designer launches you should now see the option to create the System connection type in the Manage In-DB Connections window.
This post has a trick to always run Alteryx Designer with elevated permissions.
Hope this helps!
Peter Stoddard Premium Support Advisor Alteryx, Inc.
So I`m following all the steps as you did. Connections to server and user were set with the same name and same configurations. However, when I`m trying to add the workflow to server I get the following message:
"[TEST.yxmd] Tool 1 - Error SQLDriver Connect: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified". any ideas what should I do?
I still wasn`t able to solve the issue. I`ve rewritten most of the workflows to sql queries, so that I could use it on the server. However, I can`t do that on the workflows that are creating temporary tables, as temporary tables just seem not to work in the usual input...:(
Please share if alteryx support comes up with the solution.
It sounds like everybody in here has already verified their drivers, but when I had this issue the problem was that our server had an updated version of the ODBC driver we were using. So the server was not recognizing the older version. once we updated on our local machines it and set up the ODBC with the new version worked fine.