+41
Started

The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

aodinfo 6 months ago updated by Miko 1 week ago 60 2 duplicates
The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.
ConnectWise Control Version:
20.5
Server Affected:
Host Client Affected:
Guest Client Affected:

Duplicates 2

on host server on naviguate on guest 

Could you send me your instance URL? I suspect this might be extension-related.

is on navigate on main menu host (guest cient) example ( groupe lalonde) i click i have this error i reclick i work after or i have error again no all the time on 100 click 10 time error! on next error i print screen for you excuse me my language is french
 

+2

I am also getting this error, after upgrade to 20.5

+2

Same here. 

After upgrade to 20.5 (self host)

The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

Appears randomly, no perceived loss of functionality.

Just, FYI

When this error pops up - console show this error:


Same here. Pop ups sometime, even on the code-joining page.

+1

no

The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

only

I use Opera Browser

Same here along with other errors after the latest and greatest update. Following

+4

I appreciate that ConnectWise is working on the problem.  I am a little bit frustrated since 20.5 is all about fixing bugs.  So far i have had two major problems since upgrading to 20.5 this being one of them.  The other being "There was an error writing to the Pipe..."  Either this error or the Pipe error pops up maybe 1 out of every 10 times i go to click somewhere on the Web Server Console Page

Using Brave with Shields Down and I am getting this as well. Seemed to start showing up this week. I know there was a recent update but I did not check versions. We have a Connectwise hosted edition. 

Having the same issue as well with Google Chrome 83.0.4103.97

I've been getting this progressively more and more lately. With the 20.6 version I'm getting it A LOT

I just saw that .7465 has been reclassified from Stable to Preview, presumably so that the Auto-Upgrade won't be applied. Maybe they noticed this bug and decided it was too soon to deem it stable?

We're having this issue too (self hosted).

+2

We are having this same issue.  Upgraded to 25.6 and we are still getting it. Self-hosted on Windows 2019.

Just upgraded to the 25.6 stable and I am still getting this error once in a while.

+2

Same here with self-hosted.  Started with 20.5 and continues with 20.6.  Seems to run fine for a while and then the error pops up randomly.  Once it's starts, I also have some trouble reconnecting to the console.

+1

Same situation here with v20.5 & 20.6

Self hosted.

Same here - self hosted v20.6.28797.7465 running on Windows 2016

Chrome 83.0.4103.106 - Windows 10

Having the same problem with cloud-hosted v20.5.28493.7445 with Chrome as well

Same here, using the new Chromium Edge version 83.0.478.54, self-hosted version 20.6.28954.7473

Also having the issue - 20.6 self hosted in a Server 2012R2 VM.  Firefox 77.0.1, my other tech who gets it is running Chrome.  No loss of functionality, once I click the message away I can use normally.

@connectwise Any update on this. There was a software update to 20.6.28954.7473 but we are still having the same issue. 

+1

I would like to add myself to the list.

Control version: 20.6.28797.7465 (Self hosted)

Browser: Edge Chromium 83.0.478.56

Errors I'm seeing: 

1. There was an error writing to the pipe: The pipe is being closed. (232, 0xe8).

2. The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

Like others the errors are totally random and don't seem to effect functionality, but are annoying.  Also, I feel like I'm seeing more delay (waiting for the interface to respond) in the more recent versions of ConnectWise Control.

Same problems w/self hosted version, an assortment of browsers, version 20.5.28493.7445.

Cloud v20.6.28954.7473, error showed up when I tried to delete a trigger.

Having the same problem CWC v20.6.28954 (self-hosted), Windows Server 2012 r2. After no support for Linux since version 19.4, I migrated to Windows and it still not working properly. What's going on?

Cloud hosted. Using Latest version of Chrome browser, randomly appears.

Same here.  Self-hosted
Version: 20.6.28954.7473
Host: Server 2019 Standard
Clients: Win 10 Pro - 2004 - Occurs in Chrome on all my technician's computers

Same here. Self hosted 20.7.29305.7496, Appears in Firefox 78.0.2/64-bit. Seen on clicking 'update guest info' or just clicking any machine in the access list. Apparently random.

+1

After removing this extension "Advanced SMTP Settings" I haven't seen this error anymore. I also updated one of five other outdated extensions that I don't remember the name. I was on version v20.6 and now on v20.7.29305.7496 and so far so good. Windows Server 2012 r2, self-hosted.

I just removed the Advanced SMTP Settings as suggested and verified that all extensions are up-to-date,  but I still get the error message.  I also upgraded to version 20.7.29305.7496.

Upgraded to version 20.7.29305.7496, still getting the error.

same. They obviously don't care...at this point that's clear. I've just learned to deal with it.

I went out on a limb and disabled all extensions, and the error still appears.

After removing this extension "Advanced SMTP Settings" I haven't seen this error anymore. I also updated one of five other outdated extensions that I don't remember the name. I was on version v20.6 and now on v20.7.29305.7496 and so far so good. Windows Server 2012 r2, self-hosted, 110 Unattended devices.

I kept these extensions and so far no problem:

- Additional General Information - Version: 1.5.8

- Advanced Configurator Editor - Version: 1.2.18

- Guest Full Installer Builder in Active Panel - Version: 1.5.2

- Guest Session Starter - Version: 1.0.105

It doesn't work for me.  Did you restart the server after doing the changes?  

Upgraded to version 20.7.29386.7502

Problem persists with or without extensions turned off.

Running on Chrome v84.0.4147.105 and ScreenConnect Client v20.7.29443.7508 and am getting the error quite often. What's the status on a fix? 

The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

I've also been having this issue for a while now. Looking for a fix before I upgrade again and end up with a new bug as well as this one. Any updates at all? I had opened a ticket on this, but it auto closed due to no response. Not sure what I am expected to reply with if it's a bug.

After upgrading to 20.7.29293.7496, the number of errors I'm receiving has greatly reduced -- but they still occur.  Still in need of a fix.

Without knowing there is a known issue (ouch),  Updated to 20.7.29443.7508 getting "Error Object reference not set to an instance of an object." Support tells me it's the same issue. And they are working on it.

+1

error to write to the pipe 222 this error now on 20.8.29574.7520 

it's really frustrating i click to change guest and this error appears on Self hosted and technician computer connect to hosted  is not the same error before and same error on multi computer connecting on technician on host

+1

Today, I launched my browser, entered my cloud instance’s URL and I was shown the error message: “There was an error writing to the pipe: Unrecognized error 232 (0xe8).” I closed the error popup, but I saw that the guest page underneath was in an unusual state: the leftmost column showed only the Admin cog icon, the other icons (Support, Meeting, Access) were nowhere to be seen. I reloaded the page and it was displayed correctly. My instance is on v20.9.581.7519 and I was already logged in to the instance as an Administrator.

-1

Hi All, 

Looks like the bug fix for this issue is in version 20.9, which is currently in preview. We expect this release to be stable in a few weeks. 

+2

Caitlin, that’s great news for the “communication object” error, but I’d like to ask what the status is on the “error writing to the pipe” that I (and a couple of others) commented on above? Granted, that should probably be in a separate bug report, but it’s an issue I’m having even on v20.9.

+2

I am also having the "error writing to the pipe" issue on self hosted and version 20.9.680.7530

Same issue (Error writing to the pipe) as well on self hosted 20.9.680.7530. It has persisted across 3 upgrades now. 

Can also confirm that it's been around since the last 3 versions.  Just upgraded and it's still a problem.

I am also getting this more and more frequently, i am proxied through NGNIX but it doesnt seem to make a difference. its an issue at its core web server.
20.8.29574.7520

CTC are also receiving this error. Keen to see it resolved.

Multiple browsers and are self hosted.

Clicking the x on the error allows you to continue working but its more of an annoyance.

This has been going on 4 months now with no movement towards a resolution.  Any update?

I upgraded to 20.10.957.7556 and, while it seems less infrequent, I still get these random messages. Quite perplexing that there hasn't been any forward progress or notification on this.

Same version here. It's annoying enough that I'm evaluating replacement services. I'm not entrenched in their ecosystem (only a ScreenConnect customer) so it's easy enough for me to move. I opened a ticket with support, but they just pointed me to this bug report and closed my ticket.

I agree, it would be very nice to get some sort of update here.  I think we're 5 version upgrades in now and still been an issue for many of us.  

Getting it with 20.11.  Self-hosted on Win10Pro.