topic Re: Error receiving data: An existing connection was forcibly closed by the remote host. ( in Alteryx Server Discussions

Error receiving data: An existing connection was forcibly closed by the remote host. (1005

shravanvijayaprasad — Mon, 27 Apr 2020 12:38:35 GMT

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

Re: Error receiving data: An existing connection was forcibly closed by the remote host. (

ianwhite — Thu, 30 Apr 2020 16:29:04 GMT

Can you try to run this workflow from the designer that's installed locally on the server? This may be a permissions issue and that's the best way to be certain.

Re: Error receiving data: An existing connection was forcibly closed by the remote host. (

shravanvijayaprasad — Fri, 01 May 2020 15:51:55 GMT

@ianwhite yes, I am able to run it on my designer without any issues, and it does show the error log too.

Re: Error receiving data: An existing connection was forcibly closed by the remote host. (

ianwhite — Wed, 06 May 2020 21:02:29 GMT

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-Private-Gallery/ta-p/176171

Re: Error receiving data: An existing connection was forcibly closed by the remote host. (

raychase — Thu, 07 May 2020 00:19:51 GMT

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.

Full error:

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

Re: Error receiving data: An existing connection was forcibly closed by the remote host. (

tothd — Thu, 07 May 2020 04:09:52 GMT

looks like a process may be getting hung up and then client kicked out for not moving it along.

Please update this your ticket when this is resolved.

Cheers,

rdt

Re: Error receiving data: An existing connection was forcibly closed by the remote host. (

raychase — Wed, 13 May 2020 21:57:25 GMT

Anyone have any ideas on this? I'm seeing the error about 1-5 times per day. It seems to have started up during our last monthly VM patching window.

Re: Error receiving data: An existing connection was forcibly closed by the remote host. (

shravanvijayaprasad — Thu, 14 May 2020 04:44:48 GMT

@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.

Re: Error receiving data: An existing connection was forcibly closed by the remote host. (

shravanvijayaprasad — Thu, 14 May 2020 04:47:04 GMT

@raychase we have raised a support ticket too and provided our workflow. No response yet though

Re: Error receiving data: An existing connection was forcibly closed by the remote host. (

raychase — Thu, 14 May 2020 12:22:47 GMT

@shravanvijayaprasad - out of curiosity, what version of Alteryx Server are you using?

We have Alteryx Server 2019.4 on Windows Server 2012, using the SQL Server Native Client driver.

Re: Error receiving data: An existing connection was forcibly closed by the remote host. (

shravanvijayaprasad — Thu, 14 May 2020 16:32:26 GMT

I don't have server access myself but I can surely say that we are running 2019.3. I can check with the team and let you know. One thing I noticed is, this issue only happens when the workflow has an error (when it is completely successful, we see a log)

Re: Error receiving data: An existing connection was forcibly closed by the remote host. (

raychase — Sat, 23 May 2020 00:27:10 GMT

Any luck fixing this issue? I've been chatting with various different teams within my organization, as well as consulting with Alteryx Support, and we have not been able to identify the root cause.

Re: Error receiving data: An existing connection was forcibly closed by the remote host. (

raychase — Sun, 24 May 2020 12:54:01 GMT

@shravanvijayaprasad

Check this out, I believe it's the root cause of my problem. It may also be relevant to you:

https://support.microsoft.com/en-us/help/4557473/errors-when-applications-try-to-connect-to-sql-server-in-windows

Looks like I'll need to get the Windows Server version upgraded on the VM that hosts our Alteryx Server.

Re: Error receiving data: An existing connection was forcibly closed by the remote host. (

shravanvijayaprasad — Mon, 25 May 2020 18:11:09 GMT

@raychase no luck yet, I will look into the link you have provided. let me know if that resolved it for you

Re: Error receiving data: An existing connection was forcibly closed by the remote host. (

raychase — Fri, 29 May 2020 00:24:58 GMT

@shravanvijayaprasad I implemented the fix using a local group policy to remove any cipher suites prefixed with TLS_DHE_ and have not received any errors since. The fix has been in place for over 24 hours now, and typically we'd see the error at least once (sometimes as many as 15 times) per day.