In-DB Connection on Server Returning "Number of records read: 0"

[BarryJT]

I am banging my head against the desk (again) as having an issue with the In-DB connectors on the Alteryx Server, and hoping someone can help me before I decide to re-do workflow to use Input Data. What's weird is not that I'm having issues but that the same connector works on first table but not the rest and the workflow works fine when running from Designer.

I have a workflow with a Connect In-DB tool with a file connection type. Actually, there are 5 instances of the Connect In-DB tool using the same file connection. The file connection points to a SQL Server Native Client 11 ODBC driver that uses Trusted Connection. As I mentioned above, when I run from my computer, the workflow runs great. However, when upload to the gallery, the first instance works but the other instances while showing no error message (job results show ran successfully), logs the following: "Number of Records Read: 0". I can't run from the Designer on the Server as the Connect In-DB tools are using Trusted Connection and I log onto the Server with my admin account while Gallery is using a service account.  I tried to make a new connection file to point to same odbc driver and same issue.

I'm stumped.... I keep wondering if it's a user issue but I have no idea where to go from here (besides trying to change to Input Data connection).

Any suggestions?

Thanks,

Barry

[fmvizcaino]

Hi @BarryJT ,

If possible, try adding your credential when publishing the workflow onto the server. If not possible, ask your Gallery admin to enable the option just for the testing's sake. 

https://help.alteryx.com/20221/server/alteryx-server-configuration#workflow-settings

That way, you will know if it is indeed a user issue.

Best,

Fernando Vizcano

[BarryJT]

Hi @fmvizcaino, 

Thanks for the response. Luckily (or unluckily) I am the Gallery admin.  After making the security changes, I was able to run workflow on gallery with my personal credentials. The good news is that it ran fine. However, if it was a security issue with the other id, I'm surprised I didn't receive any error messages. I put in ticket for IT to check my access rights to the tables and if that's fine, I'll see if they can see anything in the database logs. 

Thanks again for the suggestion and I'll follow back up once I've worked with IT and hopefully resolve the issue.

Best Regards,

Barry