Join our community!

Get everything you need to start developing EPiServer solutions.
February 24 2011, 15:22

Terminating client connection: Error reading from pipe 3720: error 109

In the log files I am constantly seeing 

2011-02-24 15:15:50,978 INFO PipeServerChannel.ServerMain Microsoft.Samples.Runtime.Remoting.Channels.Pipe.DBG - 18.3.1 Scheduler info:  Terminating client connection: Error reading from pipe 3720: error 109
2011-02-24 15:15:50,978 INFO PipeServerChannel.ServerMain Microsoft.Samples.Runtime.Remoting.Channels.Pipe.DBG - 18.3.1 Scheduler info:  Terminating client connection: Error reading from pipe 3720: error 109. Once a minute. The site is running on multiple servers with arround 40 instances per server so in total this message appears allot. Should I be worried about this or is this expected?


  • January 3 2012, 17:50

    I get the same error... did you find a solution to this? I have log level set to WARN and this message appears... 

  • January 9 2012, 22:11

    I think this error is caused when the scheduler tries to run the job publishing versions (don´t know the exact translation atm), that is by default run every minute. If this job not could start due to some reason, the error occurs. Try to check your database for jobs that is set to true, but started a long time ago. Set them to false. This will only make them reevaluate themselves when triggered again. Then, check that you don´t have any scheduled job that takes too much time to complete. Best practice in scheduled job is to run them in a separate thread to avoid those kinds of errors.

    Hope you got some help of my post. :)

  • March 8 2012, 9:13

    How do you run a job in a seperate thread? Are you talking about custom jobs or all the standard jobs as well?

    I have this error too. The job was running once an hour and takes seconds to complete, yet the job is still running it says.

  • March 8 2012, 10:06

    John, check if there is another job preventing your current job to complete. "Running" doesn´t always mean running :)

    Check the table in your Episerver database for more information.

  • March 14 2012, 21:05

    This problem did not go away after applying the hotfix for CMS 6R2. The issue of the jobs "still running" does. Due to it being a bug fixed in the hotfix: http://world.episerver.com/Blogs/Shahid-Nawaz/Dates/2012/1/General-Hotfix-CMS-6-R2/

    So it seems that the error in the log may be unrelated to my problem - the question is, what does the error mean then?

  • March 14 2012, 21:05
    Content removed by user
  • February 27 2014, 10:59

    I am getting this error in EPiServer 7.1 now. Does anybody know what it is? Can it be safely ignored? It shows as a warning in the log so maybe it's not a huge deal?

  • March 7 2014, 10:52

    Hi!

    I´m also experiencing this problem in EPiServer 7.1.2 with Patch4 installed. Does anybody know what´s wrong?

  • May 16 2014, 15:15

    Im also having this problem with CMS 6 r2.. 

    I think this problem is related to another error i have, timeout error from TMG "Error Code: 408"

    it fits well with the itmestamps in "Terminating client connection: Error reading from pipe"

  • June 28 2014, 16:47

    We are experienceing this too and it is consistently accompanied by a significant performance hit within a particular page load process, so we need to determine the cause.  Did anyone make any progress on figuring this out?