0
Fixed

There was an error reading from the pipe: The pipe has been ended. (109, 0x6d)

Vitalus 3 years ago updated by Ben Burner 3 years ago 3

SC Version: 6.0.11622.6115


A few machines are showing this error when I select them. I'm still able to connect, but the right sidebar doesn't load any info and freezes up.


This only happens for about 3 machines out of 200.



ConnectWise Control Version:
19.2
Server Affected:
Host Client Affected:
Guest Client Affected:
+1
Fixed

Good morning,


The behavior you describe is likely caused by the existence of lengthy session connection event data on those sessions (this sort of data can be generated in a number of ways, but often is generated by copying a large number of files at once on the guest machine through a Control session).


We recently made a few improvements to how ConnectWise Control interacts with the database, and all of these improvements would be included in the latest stable release, 6.1.12292. While the improvements won't alter data that's already been written to the database, they should prevent this sort of behavior from cropping up going forward.


There are a couple ways to resolve the pipe errors you're encountering on the host page:

1) Completely uninstall the access client on the three affected machines and conduct a fresh install

2) Enable database maintenance on your Control server, namely the "Delete Access Session Activity: Remove messages, commands, notes, and connection information..." maintenance plan action; database maintenance will eventually clear out the session connection event data that trigger the pipe error


Cheers,

Ben

Thanks for the info Ben.


I did notice the computers that are giving me these errors are the one that have large file transfers done. Will the latest stable version you mentioned address this issue as well?


Also, is there way to run that database maitainence immediately without having to schedule it?

In versions 6.0 and 6.1, there is no way to run database maintenance immediately, and scheduling is limited to the top of the hour (1:00, 2:00, ... , ).


We've introduced an overhaul of the database tab in version 6.2 that permits more granular control over database maintenance plan action definitions. For instance, you will have the ability to delete host and/or guest access session connections older than a certain number of days. Furthermore, you will be able to schedule maintenance to run at a specific time, for example, 11:25 server local time.


While I don't recommend upgrading your production server to the current 6.2 pre-release, the 6.2 should be available shortly, pending QA.


Again, the quickest way to eliminate the pipe errors is to completely uninstall the access clients from the affected machines, and then conduct a fresh client install.