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.
6/17/21: We have completed maintenance for the Search functionality on the Community. If you are seeing any issues, please try to clear your cache first. If the issue persists please email Community@alteryx.com
When I schedule run a workflow on server, we are getting the following error - Error receiving data: An existing connection was forcibly closed by the remote host. (10054) and it doesn't show the error log in Workflow results. has anyone had this error and can you guide me through why we might be having this error?
This error doesn't show up when I run it on my local machine Alteryx Designer but it happens only on the server
is your designer the one that's on the system running the server software? Whenever Alteryx Server is installed, deisgner is also installed. So whatever machine is designated as the Server system will also have Designer on it. Running it there, as the user that will be running the Server, will allow you to determine if there are permissions issues.
The error that you're seeing is typically indicative of a permissions issue, which is why I suggest that Designer on the Server system to confirm. If you can run it on your own system fine but both the Designer on the Server and the Server itself through Gallery can't run the workflow, then we know it's permissions based. In this case, I usually direct customers to this post that explains permissions on workflows pretty well. https://community.alteryx.com/t5/Alteryx-Server-Knowledge-Base/How-Workflow-Credentials-Work-on-a-Pr...
We've been experiencing the same error, although very intermittently. The same workflow could run 50 times on Server in a day and fail once or twice with this error.
I submitted a ticket with Support earlier today to have it looked into. Permissions are certainly not the cause, as it works with the same credentials 95% of the time.
Error opening connect string: Microsoft SQL Server Native Client 11.0: Client unable to establish connection\08001 = 10054; Microsoft SQL Server Native Client 11.0: TCP Provider: An existing connection was forcibly closed by the remote host. \08001 = 10054
@ianwhite yes, I asked my server team to run it on the server designer and it ran (with errors) but it also had the log. The problem is I'm still not able to see the log in the server gallery. I've tried using another gallery and same error there too.