+4
Under review

Exception 0x80004005 error in event logs on recent release.

Joshua Fredrickson 3 months ago updated by Rob Day 1 month ago 14

I am seeing the following error on multiple computers with the latest version of Screenconnect (19.2.24707.7131).  After reviewing the Windows event logs it appears I started getting this error on June 11th on my computer.

I can still connect to these clients, and there is no error popping up on the screen for these clients. I noticed this when troubleshooting another issue in the event viewer.

System.Net.Sockets.SocketException (0x80004005): A blocking operation was interrupted by a call to WSACancelBlockingCall

at ScreenConnect.SocketNetworkConnection.Receive(Byte[] buffer)

at ScreenConnect.NetworkConnection.OnReadStreamNeedsBufferCycled(Object sender, EventArgs e)

at ScreenConnect.Extensions.RaiseEvent[T](Object sender, EventHandler`1 eventHandler, T eventArgs)

at ScreenConnect.BlockBufferReadStream.Read(Byte[] buffer, Int32 offset, Int32 count)

at ScreenConnect.Extensions.ReadByteDefault(Stream stream)

ConnectWise Control Version:
19.1
Server Affected:
Host Client Affected:
Guest Client Affected:

I'm also getting 0x80004005 on a win7 box. Connectwise Automate installs, and screenconnect components are present in program files (x86). Event viewer when attempting to start the screenconnect service via services.msc:

System.Net.Sockets.SocketException (0x80004005): A blocking operation was interrupted by a call to WSACancelBlockingCall
at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)

On affected machines, I am UNABLE to connect with screenconnect.

I am also getting the same error in event viewer as above when trying to install the client on a new machine, i have also tried to manually start the service and it fails. 



System.Net.Sockets.SocketException (0x80004005): A blocking operation was interrupted by a call to WSACancelBlockingCall at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) at ScreenConnect.SocketNetworkConnection.Receive(Byte[] buffer) at ScreenConnect.NetworkConnection.OnReadStreamNeedsBufferCycled(Object sender, EventArgs e) at ScreenConnect.Extensions.RaiseEvent[T](Object sender, EventHandler`1 eventHandler, T eventArgs) at ScreenConnect.BufferStream.OnNeedsBufferCycled() at ScreenConnect.BlockBufferReadStream.Read(Byte[] buffer, Int32 offset, Int32 count) at ScreenConnect.Extensions.ReadByteDefault(Stream stream) at ScreenConnect.BlockBufferReadStream.ReadByte() at System.IO.BinaryReader.ReadByte() at ScreenConnect.MessageSerializer.Deserialize(BinaryReader reader, Type requireBaseClass) at ScreenConnect.EndPointManager.ReceiveMessage(BinaryReader reader, Type requiredBaseMessageType) at ScreenConnect.SocketEndPointManager.RunIncomingThread(ThreadSharedState threadSharedState)

I'm having the same problem and cannot connect;

System.Net.Sockets.SocketException (0x80004005): A blocking operation was interrupted by a call to WSACancelBlockingCall
at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at ScreenConnect.SocketNetworkConnection.Receive(Byte[] buffer)
at ScreenConnect.NetworkConnection.OnReadStreamNeedsBufferCycled(Object sender, EventArgs e)
at ScreenConnect.Extensions.RaiseEvent[T](Object sender, EventHandler`1 eventHandler, T eventArgs)
at ScreenConnect.BufferStream.OnNeedsBufferCycled()
at ScreenConnect.BlockBufferReadStream.Read(Byte[] buffer, Int32 offset, Int32 count)
at ScreenConnect.Extensions.ReadByteDefault(Stream stream)
at ScreenConnect.BlockBufferReadStream.ReadByte()
at System.IO.BinaryReader.ReadByte()
at ScreenConnect.MessageSerializer.Deserialize(BinaryReader reader, Type requireBaseClass)
at ScreenConnect.EndPointManager.ReceiveMessage(BinaryReader reader, Type requiredBaseMessageType)
at ScreenConnect.SocketEndPointManager.RunIncomingThread(ThreadSharedState threadSharedState)

We are getting a similar error randomly at one client:

System.Net.Sockets.SocketException (0x80004005): An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at ScreenConnect.SocketNetworkConnection.Receive(Byte[] buffer)
at ScreenConnect.NetworkConnection.OnReadStreamNeedsBufferCycled(Object sender, EventArgs e)
at ScreenConnect.Extensions.RaiseEvent[T](Object sender, EventHandler`1 eventHandler, T eventArgs)
at ScreenConnect.BufferStream.OnNeedsBufferCycled()
at ScreenConnect.BlockBufferReadStream.Read(Byte[] buffer, Int32 offset, Int32 count)
at ScreenConnect.Extensions.ReadByteDefault(Stream stream)
at ScreenConnect.BlockBufferReadStream.ReadByte()
at System.IO.BinaryReader.ReadByte()
at ScreenConnect.MessageSerializer.Deserialize(BinaryReader reader, Type requireBaseClass)
at ScreenConnect.EndPointManager.ReceiveMessage(BinaryReader reader, Type requiredBaseMessageType)
at ScreenConnect.SocketEndPointManager.RunIncomingThread(ThreadSharedState threadSharedState)

Do you guys use Palo Alto for your firewall?  We think we might of identified that as the problem on our end but are still researching.

No we don't, let us know what you have found :)

Ok it ended up being with the Captive Portal settings on our Palo Alto.

Not sure if the SonicWall has the same options but start there.  ScreenConnect support told me that after the 19 upgrade of their client some firewalls were like Palo were having issue so I suspect it could affect other types of firewalls.

I'm having the same issue, Sophos XG. I mean if its never been an issue before, wouldn't that be a Control issue, that maybe they should fix? =)

After making the changes on our Palo Alto the exceptions went away in the event viewer.


From what I understand they changed the way the traffic is being routed in the new version of Screen Connect which is why some firewalls are requiring some configuration changes.

It would be nice to have the configuration requirements on the Screen Connect site for each of these firewalls.  I know our administrator who called Palo Alto they had no idea what he was talking about at first.

Interesting, but shouldn't that affect all clients? I only have 1 of 40 at the site with that problem.

I am getting the same thing on random Win 10 workstations and we use Sophos.  I just pushed it out to 150 of the exact same computers with the same GPOs applied and maybe 10 of them came up with this error.

We are on 19.1.24050.7079

For those seeing the same issue, I did find that if I uninstall the client completely and reinstall it that they seem to work fine.  I just added it to my script that I push out with and those 10 computers all came online.

I am having the same issue on one new Server 2019 server.  it is a Hyper-V VM on a server 2019 host.  when  I try to connect, screen freezes on locked screen and I get the error above on my workstation and on the server I am trying to connect to.  I have 4 servers at this client, 2 physical, 2 VM's but only have the issue with one VM.  I can connect when the Hyper-V host is connected to the VM [has vm open in Hyper-V], but as soon as the host closes the vm, I cannot connect anymore.